drm/virtio: bound EDID block reads to the response buffer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b4b01b4995fb15b55a2d067eb405917f5ab32709 · < 35be0e2c6862abcd5e5f5445261f1fd910d4a9b4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/virtio: bound EDID block reads to the response buffer
virtio_get_edid_block() validates the read offset only against the device-supplied resp->size field, never against the fixed-size resp->edid array. The EDID block index is driven by the device-supplied extension count, so a malicious virtio-gpu backend can advertise a large size together with a high block count and read far past the array into adjacent kernel memory, which is then surfaced in the parsed EDID (an out-of-bounds read / info leak).
Also reject any read whose end exceeds the size of the edid array. Conforming EDID responses stay within the array and are unaffected.
From the CVE record · Linux
The Linux kernel's virtio-gpu EDID reader checks offsets against a device-supplied size but not the fixed-size EDID response array. A malicious virtio-gpu backend can supply a large size and extension count, causing an out-of-bounds read that exposes adjacent kernel memory through the parsed EDID.
Engineers running Linux kernels with the drm/virtio virtio-gpu driver should check their kernel builds; affected versions were not provided.