Skip to main content
VulnerabilityPublished Updated

CVE-2026-68255: Linux kernel · Out-of-bounds Read

Affects Linux kernelSource CVE Database V5

0

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

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b4b01b4995fb15b55a2d067eb405917f5ab32709, < 2757e6e803092cf0aeaf4b735e16b5d3bdc705c5
Fixed in
  • 2757e6e803092cf0aeaf4b735e16b5d3bdc705c5
LinuxLinuxAffected
  • ≥ b4b01b4995fb15b55a2d067eb405917f5ab32709, < 375c1934ef0196d3b6d3a1eae3232bef8dae7bf7
Fixed in
  • 375c1934ef0196d3b6d3a1eae3232bef8dae7bf7
LinuxLinuxAffected
  • ≥ b4b01b4995fb15b55a2d067eb405917f5ab32709, < 65ce911f341ad8ff0c08922eff5bb6db75666eb0
Fixed in
  • 65ce911f341ad8ff0c08922eff5bb6db75666eb0
LinuxLinuxAffected
  • ≥ b4b01b4995fb15b55a2d067eb405917f5ab32709, < 64bedd2758eccbc74d39f7006a7ec16fa39dc901
Fixed in
  • 64bedd2758eccbc74d39f7006a7ec16fa39dc901
LinuxLinuxAffected
  • ≥ b4b01b4995fb15b55a2d067eb405917f5ab32709, < 35be0e2c6862abcd5e5f5445261f1fd910d4a9b4
Fixed in
  • 35be0e2c6862abcd5e5f5445261f1fd910d4a9b4
LinuxLinuxAffected
  • ≥ b4b01b4995fb15b55a2d067eb405917f5ab32709, < 9fc2a017c5d597937e0c28b9a9669844aa796c42
Fixed in
  • 9fc2a017c5d597937e0c28b9a9669844aa796c42

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

Community reviews

Loading reviews…