Answer in brief
CVE-2026-68255 records a Unknown severity vulnerability in drm/virtio: bound EDID block reads to the response buffer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <9fc2a017c5d597937e0c28b9a9669844aa796c42 || >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <2757e6e803092cf0aeaf4b735e16b5d3bdc705c5 || >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <35be0e2c6862abcd5e5f5445261f1fd910d4a9b4 || >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <375c1934ef0196d3b6d3a1eae3232bef8dae7bf7 || >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <4e1a53892ba7f8a3e1da6bfc53c83ae7c812dccd | 9fc2a017c5d597937e0c28b9a9669844aa796c42, 2757e6e803092cf0aeaf4b735e16b5d3bdc705c5, 35be0e2c6862abcd5e5f5445261f1fd910d4a9b4, 375c1934ef0196d3b6d3a1eae3232bef8dae7bf7, 4e1a53892ba7f8a3e1da6bfc53c83ae7c812dccd |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68255 records a Unknown severity vulnerability in drm/virtio: bound EDID block reads to the response buffer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <9fc2a017c5d597937e0c28b9a9669844aa796c42 || >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <2757e6e803092cf0aeaf4b735e16b5d3bdc705c5 || >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <35be0e2c6862abcd5e5f5445261f1fd910d4a9b4 || >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <375c1934ef0196d3b6d3a1eae3232bef8dae7bf7 || >=b4b01b4995fb15b55a2d067eb405917f5ab32709 <4e1a53892ba7f8a3e1da6bfc53c83ae7c812dccd | 9fc2a017c5d597937e0c28b9a9669844aa796c42, 2757e6e803092cf0aeaf4b735e16b5d3bdc705c5, 35be0e2c6862abcd5e5f5445261f1fd910d4a9b4, 375c1934ef0196d3b6d3a1eae3232bef8dae7bf7, 4e1a53892ba7f8a3e1da6bfc53c83ae7c812dccd |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.