{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98894 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98894 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98894 and fix it if it is affected.\n\nWhat it is: CVE-2026-98894 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98894 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98894/ (Markdown: https://insights.sbomify.com/CVE-2026-98894/index.md)","id":"CVE-2026-98894","markdown":"https://insights.sbomify.com/CVE-2026-98894/index.md","name":"CVE-2026-98894","record":{"aliases":["AZL-110567","BELL-CVE-2026-98894","DEBIAN-CVE-2026-98894","GHSA-7fwj-mp6x-9r6f","UBUNTU-CVE-2026-98894"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/ras: reset CPER ring on corrupt entry size\n\nWhen CPER ring overflow handling advances the read pointer, it trusts the\nparsed entry size from the current ring contents. Corrupt CPER data can\nproduce an entry size that does not advance rptr after dword conversion\nand pointer masking.\n\nIn that case the recovery loop keeps testing the same location while\nholding the CPER ring mutex. This can hang the worker that is writing the\nnext CPER record.\n\nDetect a no-progress rptr update and reset the CPER ring to an empty\nstate instead. This drops the corrupt contents and lets the writer leave\nthe recovery path without spinning.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/amd/ras: reset CPER ring on corrupt entry size","id":"CVE-2026-98894","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"net/mlx5: HWS, Handle destroying table that has a miss table","id":"CVE-2026-98895"},"packages":[],"prev":{"headline":"firmware: arm_scmi: Validate SENSOR_UPDATE payload size","id":"CVE-2026-98893"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-26","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98894/"}