Linux kernel denial of service in AMD CPER ring overflow handling
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's AMD RAS CPER ring overflow handling can fail to advance its read pointer when it encounters corrupt entry-size data. This can leave the recovery loop spinning while holding a mutex, hanging the worker writing the next CPER record. The input does not specify an attacker path, access requirements, or user interaction.
Engineers running Linux kernels with the affected drm/amd/ras CPER ring handling should check their deployments; affected versions are not specified.