Kernel crash via offset-miscalculated writeset lookup
Published Aug 15, 2026 · Updated Aug 15, 2026
Out-of-bounds read in Linux dm-era since 3.15 allows local users to crash the kernel through a table with a non-zero start sector. era_map() calculates the writeset block before subtracting the target offset, so metadata_current_marked() can pass an absolute block beyond the in-core bitset to writeset_marked(). Reaching the faulty mapping path requires local access and device-mapper configuration privileges; the documented consequence is a kernel crash.
Summary
What happened
Out-of-bounds read in Linux dm-era since 3.15 allows local users to crash the kernel through a table with a non-zero start sector. era_map() calculates the writeset block before subtracting the target offset, so metadata_current_marked() can pass an absolute block beyond the in-core bitset to writeset_marked(). Reaching the faulty mapping path requires local access and device-mapper configuration privileges; the documented consequence is a kernel crash.
The record
- CVE
- CVE-2026-72107
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.15
- Affected versionversion=eec40579d84873dfb7021eb24c50360f073237c5 <1fcb5e29dd7a5b85adb9d8b539911741d878e829
- Affected versionversion=eec40579d84873dfb7021eb24c50360f073237c5 <7e1822f83c5a1ee7b4a19e98edde8770a10b4c71
- Affected versionversion=eec40579d84873dfb7021eb24c50360f073237c5 <9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f
- Affected versionversion=eec40579d84873dfb7021eb24c50360f073237c5 <a868196f03c2b19418ae3d2b69e195d668a271e5
- Affected versionversion=eec40579d84873dfb7021eb24c50360f073237c5 <bafe3e720cdac38cd7ea4eb7852a8f2dbe1bbfe6
- Affected versionversion=eec40579d84873dfb7021eb24c50360f073237c5 <db5f9b4601f0012038e5a2628aedec2f47933380
- Affected versionversion=eec40579d84873dfb7021eb24c50360f073237c5 <e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5
- Affected versionversion=eec40579d84873dfb7021eb24c50360f073237c5 <fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo