# CVE-2026-98894: drm/amd/ras: reset CPER ring on corrupt entry size


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110567, BELL-CVE-2026-98894, DEBIAN-CVE-2026-98894, GHSA-7fwj-mp6x-9r6f, UBUNTU-CVE-2026-98894

## What is CVE-2026-98894?

CVE-2026-98894 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/ras: reset CPER ring on corrupt entry size

When CPER ring overflow handling advances the read pointer, it trusts the
parsed entry size from the current ring contents. Corrupt CPER data can
produce an entry size that does not advance rptr after dword conversion
and pointer masking.

In that case the recovery loop keeps testing the same location while
holding the CPER ring mutex. This can hang the worker that is writing the
next CPER record.

Detect a no-progress rptr update and reset the CPER ring to an empty
state instead. This drops the corrupt contents and lets the writer leave
the recovery path without spinning.

## Which versions are affected by CVE-2026-98894?


## How do I fix CVE-2026-98894?

Upgrade to a fixed version.

## Is CVE-2026-98894 being exploited?

There is no known exploitation of CVE-2026-98894 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98894 and fix it if it is affected.

What it is: CVE-2026-98894 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98894 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98894/ (Markdown: https://insights.sbomify.com/CVE-2026-98894/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98894
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98894
- OSV: https://osv.dev/vulnerability/CVE-2026-98894

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98894/
Summaries are generated and may contain mistakes; the official description above is the record.