{"cve":"CVE-2025-68375","nvd":{"published":"2025-12-24T11:16:01.097","modified":"2026-10-13T11:10:00.203","status":"Deferred","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86: Fix NULL event access and potential PEBS record loss\n\nWhen intel_pmu_drain_pebs_icl() is called to drain PEBS records, the\nperf_event_overflow() could be called to process the last PEBS record.\n\nWhile perf_event_overflow() could trigger the interrupt throttle and\nstop all events of the group, like what the below call-chain shows.\n\nperf_event_overflow()\n  -> __perf_event_overflow()\n    ->__perf_event_account_interrupt()\n      -> perf_event_throttle_group()\n        -> perf_event_throttle()\n          -> event->pmu->stop()\n            -> x86_pmu_stop()\n\nThe side effect of stopping the events is that all corresponding event\npointers in cpuc->events[] array are cleared to NULL.\n\nAssume there are two PEBS events (event a and event b) in a group. When\nintel_pmu_drain_pebs_icl() calls perf_event_overflow() to process the\nlast PEBS record of PEBS event a, interrupt throttle is triggered and\nall pointers of event a and event b are cleared to NULL. Then\nintel_pmu_drain_pebs_icl() tries to process the last PEBS record of\nevent b and encounters NULL pointer access.\n\nTo avoid this issue, move cpuc->events[] clearing from x86_pmu_stop()\nto x86_pmu_del(). It's safe since cpuc->active_mask or\ncpuc->pebs_enabled is always checked before access the event pointer\nfrom cpuc->events[].","cvss_v4":null,"cvss_v3":null,"cwes":[],"references":["https://git.kernel.org/stable/c/6b089028bff1f2ff9e0c62b8f1faca1a620e5d6e","https://git.kernel.org/stable/c/7e772a93eb61cb6265bdd1c5bde17d0f2718b452","https://git.kernel.org/stable/c/cf69b99805c263117305ac6dffbc85aaf9259d32"],"products":[],"source":"nvd","synced_at":"2026-10-19T22:17:07.138532058+00:00"},"epss":{"cve":"CVE-2025-68375","score":0.00193,"percentile":0.08828,"date":"2026-10-25"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}