drm/gud: fix out-of-bounds write in gud_plane_atomic_check()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 · < ea57100955c1c2a525ba1a98c18d9a05b25aeedb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/gud: fix out-of-bounds write in gud_plane_atomic_check()
The plane property loop uses req->properties[num_properties + i] as write index while simultaneously incrementing `num_properties` inside the loop. At iteration i, num_properties has also incremented by i, so the write is done at `initial_num_properties + 2*i`, skipping every other index and advancing by 2 per iteration.
With just 2 connector and 32 plane properties the last write happens at index 64, one slot past the end of the 64-slot (indices 0–63) allocation. A USB device can trigger OOB by advertising the maximum number of properties.
Fix by dropping the redundant `+ i`; num_properties is already the correct running index, as gud_connector_fill_properties() fills the preceding slots.
From the CVE record · Linux
The Linux kernel’s drm/gud property loop can write past the end of an allocated array. A USB device advertising the maximum number of properties can trigger the out-of-bounds write; the input does not specify authentication requirements.
Engineers running Linux kernels with drm/gud should check their versions; affected versions are not specified.