CVE-2025-68798: Linux kernel · perf/x86/amd: Check event before enable to avoid GPF
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e1028fb38b328084bc683a4efb001c95d3108573 : update Linux kernel when convenient.
Data as of 10 Nov 2026, 13:18 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in e1028fb38b328084bc683a4efb001c95d3108573, 49324a0c40f7e9bae1bd0362d23fc42232e14621, 866cf36bfee4fba6a492d2dcc5133f857e3446b0 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This vulnerability has been fixed in the Linux kernel. Users should update to a Linux kernel version that includes the fix commits referenced (e.g., post-5.19 with the specified fixes). No additional mitigation is required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's AMD performance monitoring unit (PMU) code can cause a general protection fault (GPF) due to a null pointer dereference in amd_pmu_enable_all(). This issue arises from a race condition where cpuc->events[idx] can become NULL during certain NMI throttle operations. The flaw affects AMD machines and has been fixed by adding a check for NULL events before enabling them.
References
- git.kernel.org/stable/c/49324a0c40f7e9bae1bd0362d23fc42232e14621 (opens in a new tab)
- git.kernel.org/stable/c/6e41d9ec8d7cc3f01b9ba785e05f0ebef8b3b37f (opens in a new tab)
- git.kernel.org/stable/c/e1028fb38b328084bc683a4efb001c95d3108573 (opens in a new tab)
- git.kernel.org/stable/c/43c2e5c2acaae50e99d1c20a5a46e367c442fb3b (opens in a new tab)
- git.kernel.org/stable/c/866cf36bfee4fba6a492d2dcc5133f857e3446b0 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)