CVE-2026-72107: Linux kernel · Out-of-bounds Read
Affects Linux kernelSource CVE Database V5
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
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 15 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: 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
- git.kernel.org/stable/c/fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf (opens in a new tab)
- git.kernel.org/stable/c/e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5 (opens in a new tab)
- git.kernel.org/stable/c/9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f (opens in a new tab)
- git.kernel.org/stable/c/7e1822f83c5a1ee7b4a19e98edde8770a10b4c71 (opens in a new tab)
- git.kernel.org/stable/c/db5f9b4601f0012038e5a2628aedec2f47933380 (opens in a new tab)
- git.kernel.org/stable/c/1fcb5e29dd7a5b85adb9d8b539911741d878e829 (opens in a new tab)
- git.kernel.org/stable/c/bafe3e720cdac38cd7ea4eb7852a8f2dbe1bbfe6 (opens in a new tab)
- git.kernel.org/stable/c/a868196f03c2b19418ae3d2b69e195d668a271e5 (opens in a new tab)