drm/amdkfd: Add bounds check for CRAT subtype length
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5b5c4e40a37e858e2bff8cd91be8e972256392c4 · < 6e7566ba4739dd573c331adde1c96690f7a567bd| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: Add bounds check for CRAT subtype length
The CRAT parser validates that the subtype header fits within the image, but does not verify that the advertised subtype length fits. A malformed CRAT table with an oversized length field causes out-of-bounds reads when kfd_parse_subtype() casts the header to specific subtype structures.
Add validation that sub_type_hdr + length does not exceed the image boundary before parsing the subtype contents.
(cherry picked from commit 48e1d1e6e8798aef0312e68d8e586021b5b3cf4d)
From the CVE record · Linux
The Linux kernel’s drm/amdkfd CRAT parser does not check whether an advertised subtype length fits within the table image. A malformed CRAT table with an oversized length can cause out-of-bounds reads; the input does not specify how an attacker could supply the table or whether authentication or user interaction is required.
Engineers running Linux kernels with the affected drm/amdkfd CRAT parser should check their kernel builds; affected versions are not specified.