{"api_version":"1","generated_at":"2026-10-26T08:56:58+00:00","cve":"CVE-2026-98894","urls":{"html":"https://cve.report/CVE-2026-98894","api":"https://cve.report/api/cve/CVE-2026-98894.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98894","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98894"},"summary":{"title":"drm/amd/ras: reset CPER ring on corrupt entry size","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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-23 12:18:23","updated_at":"2026-10-26 07:17:14"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a98d0d49757a113ce17960262b9cd4ccc1420108","name":"https://git.kernel.org/stable/c/a98d0d49757a113ce17960262b9cd4ccc1420108","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4d695e66d7027a0c78302e47ac76293675fbbb4d","name":"https://git.kernel.org/stable/c/4d695e66d7027a0c78302e47ac76293675fbbb4d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98894","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98894","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4058e7cbfd0fb0cae7cbb8035bb43c593cc7c964 a98d0d49757a113ce17960262b9cd4ccc1420108 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4058e7cbfd0fb0cae7cbb8035bb43c593cc7c964 4d695e66d7027a0c78302e47ac76293675fbbb4d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/amd/amdgpu/amdgpu_cper.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"a98d0d49757a113ce17960262b9cd4ccc1420108","status":"affected","version":"4058e7cbfd0fb0cae7cbb8035bb43c593cc7c964","versionType":"git"},{"lessThan":"4d695e66d7027a0c78302e47ac76293675fbbb4d","status":"affected","version":"4058e7cbfd0fb0cae7cbb8035bb43c593cc7c964","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/amd/amdgpu/amdgpu_cper.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.15"},{"lessThan":"6.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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."}],"providerMetadata":{"dateUpdated":"2026-10-26T06:56:20.527Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/a98d0d49757a113ce17960262b9cd4ccc1420108"},{"url":"https://git.kernel.org/stable/c/4d695e66d7027a0c78302e47ac76293675fbbb4d"}],"title":"drm/amd/ras: reset CPER ring on corrupt entry size","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98894","datePublished":"2026-10-23T11:37:55.539Z","dateReserved":"2026-09-25T10:25:14.378Z","dateUpdated":"2026-10-26T06:56:20.527Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-23 12:18:23","lastModifiedDate":"2026-10-26 07:17:14","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98894","Ordinal":"1","Title":"drm/amd/ras: reset CPER ring on corrupt entry size","CVE":"CVE-2026-98894","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98894","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"drm/amd/ras: reset CPER ring on corrupt entry size"}]}}}