Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf : patch Linux kernel soon.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% 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
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf, e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5, db5f9b4601f0012038e5a2628aedec2f47933380 +5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 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
  • ≥ eec40579d84873dfb7021eb24c50360f073237c5, < fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf
Fixed in
  • fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf
LinuxLinuxAffected
  • ≥ eec40579d84873dfb7021eb24c50360f073237c5, < e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5
Fixed in
  • e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5
LinuxLinuxAffected
  • ≥ eec40579d84873dfb7021eb24c50360f073237c5, < db5f9b4601f0012038e5a2628aedec2f47933380
Fixed in
  • db5f9b4601f0012038e5a2628aedec2f47933380
LinuxLinuxAffected
  • ≥ eec40579d84873dfb7021eb24c50360f073237c5, < bafe3e720cdac38cd7ea4eb7852a8f2dbe1bbfe6
Fixed in
  • bafe3e720cdac38cd7ea4eb7852a8f2dbe1bbfe6
LinuxLinuxAffected
  • ≥ eec40579d84873dfb7021eb24c50360f073237c5, < a868196f03c2b19418ae3d2b69e195d668a271e5
Fixed in
  • a868196f03c2b19418ae3d2b69e195d668a271e5
LinuxLinuxAffected
  • ≥ eec40579d84873dfb7021eb24c50360f073237c5, < 9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f
Fixed in
  • 9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f

Description

In the Linux kernel, the following vulnerability has been resolved: dm era: fix out-of-bounds memory access for non-zero start sector dm-era tracks writes in target-relative blocks, but era_map() calculates the writeset block before applying the target offset. Tables with a non-zero start sector can therefore pass an absolute mapped-device block to metadata_current_marked(). If the absolute block is beyond the current writeset size, writeset_marked() tests past the end of the in-core bitset. KASAN reports this as a vmalloc-out-of-bounds access. Apply the target offset before calculating the era block so writeset lookups use the target-relative block number.

References

Community reviews

Loading reviews…