CVE-2026-98894: Linux kernel · drm/amd/ras: reset CPER ring on corrupt entry size
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to a98d0d49757a113ce17960262b9cd4ccc1420108 or 4d695e66d7027a0c78302e47ac76293675fbbb4d when convenient.
Data as of 26 Oct 2026, 13:07 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in a98d0d49757a113ce17960262b9cd4ccc1420108, 4d695e66d7027a0c78302e47ac76293675fbbb4d
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade Linux kernel to a98d0d49757a113ce17960262b9cd4ccc1420108 or 4d695e66d7027a0c78302e47ac76293675fbbb4d.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel. The patch resets the CPER ring to an empty state upon detecting corrupt entry sizes that prevent read pointer advancement, preventing the hang. Users should update to the fixed kernel versions identified by the commits a98d0d49757a113ce17960262b9cd4ccc1420108 and 4d695e66d7027a0c78302e47ac76293675fbbb4d to remediate this issue.
Description
A vulnerability in the Linux kernel's AMD RAS driver (drm/amd/ras) involves improper handling of corrupt CPER ring entry sizes. When corrupt CPER data causes the read pointer to not advance, the recovery loop spins indefinitely while holding a mutex, potentially hanging the worker thread responsible for writing CPER records. The issue is resolved by detecting no-progress in the read pointer update and resetting the CPER ring to an empty state, dropping corrupt contents and allowing recovery to proceed.