CVE-2025-68375
perf/x86: Fix NULL event access and potential PEBS record loss
Reported by linux · Published December 24, 2025
In the Linux kernel, the following vulnerability has been resolved: perf/x86: Fix NULL event access and potential PEBS record loss When intel_pmu_drain_pebs_icl() is called to drain PEBS records, the perf_event_overflow() could be called to process the last PEBS record. While perf_event_overflow() could trigger the interrupt throttle and stop all events of the group, like what the below call-chain shows. perf_event_overflow() -> __perf_event_overflow() ->__perf_event_account_interrupt() -> perf_event_throttle_group() -> perf_event_throttle() -> event->pmu->stop() -> x86_pmu_stop() The side effect of stopping the events is that all corresponding event pointers in cpuc->events[] array are cleared to NULL. Assume there are two PEBS events (event a and event b) in a group. When intel_pmu_drain_pebs_icl() calls perf_event_overflow() to process the last PEBS record of PEBS event a, interrupt throttle is triggered and all pointers of event a and event b are cleared to NULL. Then intel_pmu_drain_pebs_icl() tries to process the last PEBS record of event b and encounters NULL pointer access. To avoid this issue, move cpuc->events[] clearing from x86_pmu_stop() to x86_pmu_del(). It's safe since cpuc->active_mask or cpuc->pebs_enabled is always checked before access the event pointer from cpuc->events[].
EPSS 0.19% · 8.9th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.19, 6.18.2, 6.17.13 |
| Linux | Linux | cf69b99805c263117305ac6dffbc85aaf9259d32, 7e772a93eb61cb6265bdd1c5bde17d0f2718b452, 6b089028bff1f2ff9e0c62b8f1faca1a620e5d6e, 6.16 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9734e25fbf5ae68eb04234b2cd14a4b36ab89141, 9734e25fbf5ae68eb04234b2cd14a4b36ab89141, 9734e25fbf5ae68eb04234b2cd14a4b36ab89141 |
| Linux | Linux | 6.16, 0, 6.17.13 |
| linux | linux_kernel | 6.16, 6.16, 6.16 |
| Linux | Linux | 9734e25fbf5ae68eb04234b2cd14a4b36ab89141, 9734e25fbf5ae68eb04234b2cd14a4b36ab89141, 6.16 |
Timeline
- Dec 23, 2025 CVE Published
- Dec 24, 2025 EPSS Score (30 in total, the first dated here)
- Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (130 in total, the first dated here)
- Mar 29, 2026 Security Advisory (135 in total, the first dated here)
- Sep 29, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-68375
vulnetix vdb fixes CVE-2025-68375
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-68375/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart