CVE-2026-68255drm/virtio: bound EDID block reads to the response buffer
- 7.7HighCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.7 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| NVDNVD · Received | 3.1 | High7.7 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.7.
Affected products
- affected b4b01b4995fb15b55a2d067eb405917f5ab32709 – < 65ce911f341ad8ff0c08922eff5bb6db75666eb0
- affected b4b01b4995fb15b55a2d067eb405917f5ab32709 – < 64bedd2758eccbc74d39f7006a7ec16fa39dc901
- affected b4b01b4995fb15b55a2d067eb405917f5ab32709 – < 3f506a85a905b080cadc029a1651a310479090a6
- affected b4b01b4995fb15b55a2d067eb405917f5ab32709 – < 9fc2a017c5d597937e0c28b9a9669844aa796c42
- affected b4b01b4995fb15b55a2d067eb405917f5ab32709 – < 2757e6e803092cf0aeaf4b735e16b5d3bdc705c5
- affected b4b01b4995fb15b55a2d067eb405917f5ab32709 – < 35be0e2c6862abcd5e5f5445261f1fd910d4a9b4
- affected b4b01b4995fb15b55a2d067eb405917f5ab32709 – < 375c1934ef0196d3b6d3a1eae3232bef8dae7bf7
- affected b4b01b4995fb15b55a2d067eb405917f5ab32709 – < 4e1a53892ba7f8a3e1da6bfc53c83ae7c812dccd
- affected 5.0
- unaffected < 5.0
- unaffected 5.10.266 – ≤ 5.10.*
- unaffected 5.15.217 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/65ce911f341ad8ff0c08922eff5bb6db75666eb0 (opens in a new tab)
- https://git.kernel.org/stable/c/64bedd2758eccbc74d39f7006a7ec16fa39dc901 (opens in a new tab)
- https://git.kernel.org/stable/c/3f506a85a905b080cadc029a1651a310479090a6 (opens in a new tab)
- https://git.kernel.org/stable/c/9fc2a017c5d597937e0c28b9a9669844aa796c42 (opens in a new tab)
- https://git.kernel.org/stable/c/2757e6e803092cf0aeaf4b735e16b5d3bdc705c5 (opens in a new tab)
- https://git.kernel.org/stable/c/35be0e2c6862abcd5e5f5445261f1fd910d4a9b4 (opens in a new tab)
- https://git.kernel.org/stable/c/375c1934ef0196d3b6d3a1eae3232bef8dae7bf7 (opens in a new tab)
- https://git.kernel.org/stable/c/4e1a53892ba7f8a3e1da6bfc53c83ae7c812dccd (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55356 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68255)Record last updated .