CVE-2026-98894: Linux kernel · drm/amd/ras: reset CPER ring on corrupt entry size
Source GCVE Database
Not known to be exploited : upgrade to a98d0d49757a113ce17960262b9cd4ccc1420108 or 4d695e66d7027a0c78302e47ac76293675fbbb4d when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · 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 has been implemented in the Linux kernel to detect no-progress updates of the read pointer and reset the CPER ring to an empty state, effectively dropping corrupt data and preventing hangs. Users should apply the official Linux kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or Linux kernel advisory for the current remediation guidance.
Description
A vulnerability in the Linux kernel's drm/amd/ras component related to CPER ring overflow handling has been resolved. The issue occurs when corrupt CPER data causes the read pointer not to advance, resulting in a recovery loop that hangs the worker writing the next CPER record. The fix resets the CPER ring to an empty state upon detecting no progress in the read pointer update, preventing the system from spinning indefinitely.