Kernel memory disclosure via zero-length metadata clearing
Published Aug 15, 2026 · Updated Aug 15, 2026
Uninitialized memory disclosure in dm-integrity in the Linux kernel allows local users to read kernel memory through integrity metadata. In drivers/md/dm-integrity.c, the write path gives memset a zero length by subtracting tuple size from itself rather than subtracting tag size, leaving each integrity payload tail uncleared. Reachability requires low local privileges and a hash size smaller than the device tuple size; the reported consequence is disclosure of residual kernel memory.
Summary
What happened
Uninitialized memory disclosure in dm-integrity in the Linux kernel allows local users to read kernel memory through integrity metadata. In drivers/md/dm-integrity.c, the write path gives memset a zero length by subtracting tuple size from itself rather than subtracting tag size, leaving each integrity payload tail uncleared. Reachability requires low local privileges and a hash size smaller than the device tuple size; the reported consequence is disclosure of residual kernel memory.
The record
- CVE
- CVE-2026-72101
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1005
- 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=6.11
- Affected versionversion=fb0987682c629c1d2c476f35f6fde405a5e304a4 <0c4e9bb1d4101030f55c869f18bd3ece39a77bbb
- Affected versionversion=fb0987682c629c1d2c476f35f6fde405a5e304a4 <50af3e51dc709384701dbc721b4bd865285c5f2c
- Affected versionversion=fb0987682c629c1d2c476f35f6fde405a5e304a4 <7bb03b2b01b814a9fc14afbfc2cbb2cca5b34750
- Affected versionversion=fb0987682c629c1d2c476f35f6fde405a5e304a4 <8f0af8493009a61b4313e0a8c6e03fbc36fd43f9
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.
Weakness, pattern, technique
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