CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 43c2e5c2acaae50e99d1c20a5a46e367c442fb3b, 49324a0c40f7e9bae1bd0362d23fc42232e14621, 6e41d9ec8d7cc3f01b9ba785e05f0ebef8b3b37f; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.
Low priority for now. Upgrade to Linux Linux 43c2e5c2acaae50e99d1c20a5a46e367c442fb3b, 49324a0c40f7e9bae1bd0362d23fc42232e14621, 6e41d9ec8d7cc3f01b9ba785e05f0ebef8b3b37f; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd: Check event before enable to avoid GPF On AMD machines cpuc->events[idx] can become NULL in a subtle race condition with NMI->throttle->x86_pmu_stop(). Check event for NULL in amd_pmu_enable_all() before enable to avoid a GPF. This appears to be an AMD only issue. Syzkaller reported a GPF in amd_pmu_enable_all. INFO: NMI handler (perf_event_nmi_handler) took too long to run: 13.143 msecs Oops: general protection fault, probably for non-canonical address 0xdffffc0000000034: 0000 PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x00000000000001a0-0x00000000000001a7] CPU: 0 UID: 0 PID: 328415 Comm: repro_36674776 Not tainted 6.12.0-rc1-syzk RIP: 0010:x86_pmu_enable_event (arch/x86/events/perf_event.h:1195 arch/x86/events/core.c:1430) RSP: 0018:ffff888118009d60 EFLAGS: 00010012 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000034 RSI: 0000000000000000 RDI: 00000000000001a0 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002 R13: ffff88811802a440 R14: ffff88811802a240 R15: ffff8881132d8601 FS: 00007f097dfaa700(0000) GS:ffff888118000000(0000) GS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200001c0 CR3: 0000000103d56000 CR4: 00000000000006f0 Call Trace: <IRQ> amd_pmu_enable_all (arch/x86/events/amd/core.c:760 (discriminator 2)) x86_pmu_enable (arch/x86/events/core.c:1360) event_sched_out (kernel/events/core.c:1191 kernel/events/core.c:1186 kernel/events/core.c:2346) __perf_remove_from_context (kernel/events/core.c:2435) event_function (kernel/events/core.c:259) remote_function (kernel/events/core.c:92 (discriminator 1) kernel/events/core.c:72 (discriminator 1)) __flush_smp_call_function_queue (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/csd.h:64 kernel/smp.c:135 kernel/smp.c:540) __sysvec_call_function_single (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./arch/x86/include/asm/trace/irq_vectors.h:99 arch/x86/kernel/smp.c:272) sysvec_call_function_single (arch/x86/kernel/smp.c:266 (discriminator 47) arch/x86/kernel/smp.c:266 (discriminator 47)) </IRQ>
- Published
- Jan 13, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.19affected
- ada543459cab7f653dcacdaba4011a8bb19c627c and later · before 49324a0c40f7e9bae1bd0362d23fc42232e14621affected · git
- ada543459cab7f653dcacdaba4011a8bb19c627c and later · before 6e41d9ec8d7cc3f01b9ba785e05f0ebef8b3b37faffected · git
- ada543459cab7f653dcacdaba4011a8bb19c627c and later · before e1028fb38b328084bc683a4efb001c95d3108573affected · git
- ada543459cab7f653dcacdaba4011a8bb19c627c and later · before 43c2e5c2acaae50e99d1c20a5a46e367c442fb3baffected · git
- ada543459cab7f653dcacdaba4011a8bb19c627c and later · before 866cf36bfee4fba6a492d2dcc5133f857e3446b0affected · git
- before 5.19not affected · semver
- 6.1.160 and later · up to and including 6.1.*not affected · semver
- 6.6.120 and later · up to and including 6.6.*not affected · semver
- 6.12.64 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.3-1 | 6.18.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68794Jan 13, 2026 · iomap: adjust read range correctly for non-block-aligned positions39Monitor
- ← EarlierCVE-2025-68795Jan 13, 2026 · ethtool: Avoid overflowing userspace buffer on stats query31Monitor
- Later →CVE-2025-68800Jan 13, 2026 · mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 43c2e5c2acaae50e99d1c20a5a46e367c442fb3b | Vendor (CNA) |
| Linux Linux | 49324a0c40f7e9bae1bd0362d23fc42232e14621 | Vendor (CNA) |
| Linux Linux | 6e41d9ec8d7cc3f01b9ba785e05f0ebef8b3b37f | Vendor (CNA) |
| Linux Linux | 866cf36bfee4fba6a492d2dcc5133f857e3446b0 | Vendor (CNA) |
| Linux Linux | e1028fb38b328084bc683a4efb001c95d3108573 | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/49324a0c40f7e9bae1bd0362d23fc42232e14621
- git.kernel.org/stable/c/6e41d9ec8d7cc3f01b9ba785e05f0ebef8b3b37f
- git.kernel.org/stable/c/866cf36bfee4fba6a492d2dcc5133f857e3446b0
- git.kernel.org/stable/c/e1028fb38b328084bc683a4efb001c95d3108573
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.