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.
Fix
Microsoft's update · Low
- Release Notes — azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 · build 6.6.159.1-2
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-29.
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 5
- StatusReceived → PublishedNVD modified 2026-10-26 06:56
- StatusPublished → ReceivedNVD modified 2026-10-26 07:17
- StatusReceived → PublishedNVD modified 2026-10-23 11:37
- StatusPublished → ReceivedNVD modified 2026-10-23 12:18
- First seenunscored · linuxNVD modified 2026-10-23 11:37
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.