Virtio_get_edid_block validates the read offset only against the device-supplied response size, not against the fixed-size response edid array. A malicious virtio-gpu backend can advertise a large size together with a high block count, causing reads far past the array into adjacent kernel memory. The data read is surfaced in the parsed EDID, resulting in an out-of-bounds read that leaks sensitive kernel memory.

Linux kernel implementations that include the virtio-gpu driver are potentially affected. No specific vendor or version list is provided in the source data. All current Linux kernel releases prior to the commit that fixed the issue may be vulnerable. Users should verify whether their kernel contains the virtio-gpu driver and whether the patch has been applied.

The vulnerability is an information disclosure flaw with no known exploitation of further privileges. EPSS is not available and the issue is not listed in the CISA KEV catalog, indicating limited active exploitation at this time. The likely attack vector involves a malicious virtio-gpu backend, which may be controlled by an attacker with access to the host virtualization infrastructure. Because the flaw is confined to kernel memory read boundaries, multiple privilege levels would be required to achieve a successful read, and the vulnerability is not remotely exploitable over the network without additional components. The absence of a CVSS score and exploit reports suggests the risk is moderate, but it remains advisable to apply a patch or upgrade the kernel promptly to eliminate the data-leak potential.