CVE-2026-68255: Linux kernel · Out-of-bounds Read
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.7 High · fixed in 2757e6e803092cf0aeaf4b735e16b5d3bdc705c5 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in 2757e6e803092cf0aeaf4b735e16b5d3bdc705c5, 375c1934ef0196d3b6d3a1eae3232bef8dae7bf7, 65ce911f341ad8ff0c08922eff5bb6db75666eb0 +5
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/65ce911f341ad8ff0c08922eff5bb6db75666eb0 (opens in a new tab)
- git.kernel.org/stable/c/64bedd2758eccbc74d39f7006a7ec16fa39dc901 (opens in a new tab)
- git.kernel.org/stable/c/3f506a85a905b080cadc029a1651a310479090a6 (opens in a new tab)
- git.kernel.org/stable/c/9fc2a017c5d597937e0c28b9a9669844aa796c42 (opens in a new tab)
- git.kernel.org/stable/c/2757e6e803092cf0aeaf4b735e16b5d3bdc705c5 (opens in a new tab)
- git.kernel.org/stable/c/35be0e2c6862abcd5e5f5445261f1fd910d4a9b4 (opens in a new tab)
- git.kernel.org/stable/c/375c1934ef0196d3b6d3a1eae3232bef8dae7bf7 (opens in a new tab)
- git.kernel.org/stable/c/4e1a53892ba7f8a3e1da6bfc53c83ae7c812dccd (opens in a new tab)