CVE-2025-68375: perf/x86: Fix NULL event access and potential PEBS record loss
In the Linux kernel, the following vulnerability has been resolved:
perf/x86: Fix NULL event access and potential PEBS record loss
When intelpmudrainpebsicl() is called to drain PEBS records, the perfeventoverflow() could be called to process the last PEBS record.
While perfeventoverflow() could trigger the interrupt throttle and stop all events of the group, like what the below call-chain shows.
perfeventoverflow() -> perfeventoverflow() ->perfeventaccountinterrupt() -> perfeventthrottlegroup() -> perfeventthrottle() -> event->pmu->stop() -> x86pmustop()
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 intelpmudrainpebsicl() calls perfeventoverflow() 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 intelpmudrainpebsicl() tries to process the last PEBS record of event b and encounters NULL pointer access.
To avoid this issue, move cpuc->events[] clearing from x86pmustop() to x86pmudel(). It's safe since cpuc->activemask or cpuc->pebsenabled is always checked before access the event pointer from cpuc->events[].
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68375?
CVE-2025-68375 has a medium severity level due to its potential impact on system performance and stability.
What software is affected by CVE-2025-68375?
CVE-2025-68375 affects certain versions of the Linux kernel.
How do I fix CVE-2025-68375?
To fix CVE-2025-68375, you need to update to the patched version of the Linux kernel that resolves this issue.
What is the exploit impact of CVE-2025-68375?
The exploit impact of CVE-2025-68375 could result in system instability due to improper handling of PEBS records.
Is CVE-2025-68375 being actively exploited?
As of the latest updates, there are no indications that CVE-2025-68375 is actively being exploited in the wild.