CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.65% (FIRST EPSS); higher than 50.8% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1fcb5e29dd7a5b85adb9d8b539911741d878e829, 7e1822f83c5a1ee7b4a19e98edde8770a10b4c71, 9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f.
Low priority for now. Upgrade to Linux Linux 1fcb5e29dd7a5b85adb9d8b539911741d878e829, 7e1822f83c5a1ee7b4a19e98edde8770a10b4c71, 9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.6% · 50th percentile
- CWE
- CWE-125
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.15affected
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before fe94a0b14010a3c267ff9a2508afb4f27ff1c5bfaffected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5affected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before 9946a7176bd8c25ddd6e5f1799c54e572ee6bf0faffected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before 7e1822f83c5a1ee7b4a19e98edde8770a10b4c71affected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before db5f9b4601f0012038e5a2628aedec2f47933380affected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before 1fcb5e29dd7a5b85adb9d8b539911741d878e829affected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before bafe3e720cdac38cd7ea4eb7852a8f2dbe1bbfe6affected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before a868196f03c2b19418ae3d2b69e195d668a271e5affected · git
- before 3.15not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72103Aug 15, 2026 · dm: avoid leaking the caller's thread keyring via the table device file29Monitor
- ← EarlierCVE-2026-72105Aug 15, 2026 · dm-log: fix a bitset_size overflow on 32bit machines31Monitor
- Later →CVE-2026-72108Aug 15, 2026 · dm thin metadata: fix metadata snapshot consistency on commit failure31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1fcb5e29dd7a5b85adb9d8b539911741d878e829 | Vendor (CNA) |
| Linux Linux | 7e1822f83c5a1ee7b4a19e98edde8770a10b4c71 | Vendor (CNA) |
| Linux Linux | 9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f | Vendor (CNA) |
| Linux Linux | a868196f03c2b19418ae3d2b69e195d668a271e5 | Vendor (CNA) |
| Linux Linux | bafe3e720cdac38cd7ea4eb7852a8f2dbe1bbfe6 | Vendor (CNA) |
| Linux Linux | db5f9b4601f0012038e5a2628aedec2f47933380 | Vendor (CNA) |
| Linux Linux | e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5 | Vendor (CNA) |
| Linux Linux | fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-720840 days apartscsi: target: Bound PR-OUT TransportID parsing to the received buffer39Monitor
- CVE-2026-681605 days apartceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()39Monitor
- CVE-2026-683885 days apartsmb/client: handle overlapping allocated ranges in fallocate39Monitor
- CVE-2026-680827 days apartlibceph: fix two unsafe bare decodes in decode_lockers()39Monitor
- CVE-2026-6391227 days apartxfrm: esp: restore combined single-frag length gate39Monitor
- CVE-2026-6393827 days apartKVM: SEV: Check PSC request indices against the actual size of the buffer37Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/7e1822f83c5a1ee7b4a19e98edde8770a10b4c71
- git.kernel.org/stable/c/9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f
- git.kernel.org/stable/c/a868196f03c2b19418ae3d2b69e195d668a271e5
- git.kernel.org/stable/c/bafe3e720cdac38cd7ea4eb7852a8f2dbe1bbfe6
- git.kernel.org/stable/c/db5f9b4601f0012038e5a2628aedec2f47933380
- git.kernel.org/stable/c/e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5
- git.kernel.org/stable/c/fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.