Integrity-check errors via double hash-offset increment
Published Aug 15, 2026 · Updated Aug 15, 2026
Incorrect tag comparison in Linux dm-integrity 5.7 and later allows local users to cause faulty integrity decisions with non-power-of-two tags. The dm_integrity_rw_tag function increments hash_offset while comparing each tag byte and then adds to_copy after the loop, advancing the offset twice across metadata buffers. The path requires a dm-integrity volume with a non-power-of-two tag size; published assessments bound the consequence to low integrity and availability impact.
Summary
What happened
Incorrect tag comparison in Linux dm-integrity 5.7 and later allows local users to cause faulty integrity decisions with non-power-of-two tags. The dm_integrity_rw_tag function increments hash_offset while comparing each tag byte and then adds to_copy after the loop, advancing the offset twice across metadata buffers. The path requires a dm-integrity volume with a non-power-of-two tag size; published assessments bound the consequence to low integrity and availability impact.
The record
- CVE
- CVE-2026-72099
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- 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=5.7
- Affected versionversion=84597a44a9d86ac949900441cea7da0af0f2f473 <4f4e43337e9ef322595201cfc24def50fd624219
- Affected versionversion=84597a44a9d86ac949900441cea7da0af0f2f473 <5dfd8042635278613da3b88553e25ade2103cd58
- Affected versionversion=84597a44a9d86ac949900441cea7da0af0f2f473 <829476c06496aab018f14127c055adb164d1a750
- Affected versionversion=84597a44a9d86ac949900441cea7da0af0f2f473 <cf9feed8c131e303ecf2afebe6f791be018818ad
- Affected versionversion=84597a44a9d86ac949900441cea7da0af0f2f473 <edf025f083854f80032b73a1aad69a3c90db236f
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
No sourced classifications are available.
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