{"api_version":"1","generated_at":"2026-10-29T13:57:41+00:00","cve":"CVE-2025-68375","urls":{"html":"https://cve.report/CVE-2025-68375","api":"https://cve.report/api/cve/CVE-2025-68375.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2025-68375","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2025-68375"},"summary":{"title":"perf/x86: Fix NULL event access and potential PEBS record loss","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[].","state":"PUBLISHED","assigner":"Linux","published_at":"2025-12-24 11:16:01","updated_at":"2026-10-13 11:10:00"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/6b089028bff1f2ff9e0c62b8f1faca1a620e5d6e","name":"https://git.kernel.org/stable/c/6b089028bff1f2ff9e0c62b8f1faca1a620e5d6e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7e772a93eb61cb6265bdd1c5bde17d0f2718b452","name":"https://git.kernel.org/stable/c/7e772a93eb61cb6265bdd1c5bde17d0f2718b452","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cf69b99805c263117305ac6dffbc85aaf9259d32","name":"https://git.kernel.org/stable/c/cf69b99805c263117305ac6dffbc85aaf9259d32","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-68375","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68375","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9734e25fbf5ae68eb04234b2cd14a4b36ab89141 cf69b99805c263117305ac6dffbc85aaf9259d32 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9734e25fbf5ae68eb04234b2cd14a4b36ab89141 6b089028bff1f2ff9e0c62b8f1faca1a620e5d6e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9734e25fbf5ae68eb04234b2cd14a4b36ab89141 7e772a93eb61cb6265bdd1c5bde17d0f2718b452 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.16 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.17.13 6.17.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.2 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["arch/x86/events/core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"cf69b99805c263117305ac6dffbc85aaf9259d32","status":"affected","version":"9734e25fbf5ae68eb04234b2cd14a4b36ab89141","versionType":"git"},{"lessThan":"6b089028bff1f2ff9e0c62b8f1faca1a620e5d6e","status":"affected","version":"9734e25fbf5ae68eb04234b2cd14a4b36ab89141","versionType":"git"},{"lessThan":"7e772a93eb61cb6265bdd1c5bde17d0f2718b452","status":"affected","version":"9734e25fbf5ae68eb04234b2cd14a4b36ab89141","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/x86/events/core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.16"},{"lessThan":"6.16","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.17.*","status":"unaffected","version":"6.17.13","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.2","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"6.19","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.17.13","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.2","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.19","versionStartIncluding":"6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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[]."}],"providerMetadata":{"dateUpdated":"2026-05-11T21:51:59.533Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/cf69b99805c263117305ac6dffbc85aaf9259d32"},{"url":"https://git.kernel.org/stable/c/6b089028bff1f2ff9e0c62b8f1faca1a620e5d6e"},{"url":"https://git.kernel.org/stable/c/7e772a93eb61cb6265bdd1c5bde17d0f2718b452"}],"title":"perf/x86: Fix NULL event access and potential PEBS record loss","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2025-68375","datePublished":"2025-12-24T10:33:04.819Z","dateReserved":"2025-12-16T14:48:05.310Z","dateUpdated":"2026-05-11T21:51:59.533Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2025-12-24 11:16:01","lastModifiedDate":"2026-10-13 11:10:00","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2025","CveId":"68375","Ordinal":"1","Title":"perf/x86: Fix NULL event access and potential PEBS record loss","CVE":"CVE-2025-68375","Year":"2025"},"notes":[{"CveYear":"2025","CveId":"68375","Ordinal":"1","NoteData":"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[].","Type":"Description","Title":"perf/x86: Fix NULL event access and potential PEBS record loss"}]}}}