Audit suppression via non-atomic dm-verity error counter
Published Aug 15, 2026 · Updated Aug 15, 2026
Race condition in the Linux kernel dm-verity target allows local users to suppress a maximum-corrupted-errors audit event. The dm-verity verification path increments v->corrupted_errs non-atomically, so concurrent corrupted-block errors can lose updates and skip dm_audit_log_target("max-corrupted-errors"). Exploitation requires local low-privileged access and concurrent error generation against a dm-verity mapping; the documented consequence is loss of that audit signal rather than direct data disclosure or code execution.
Summary
What happened
Race condition in the Linux kernel dm-verity target allows local users to suppress a maximum-corrupted-errors audit event. The dm-verity verification path increments v->corrupted_errs non-atomically, so concurrent corrupted-block errors can lose updates and skip dm_audit_log_target("max-corrupted-errors"). Exploitation requires local low-privileged access and concurrent error generation against a dm-verity mapping; the documented consequence is loss of that audit signal rather than direct data disclosure or code execution.
The record
- CVE
- CVE-2026-72096
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-663, T1685.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=4.1
- Affected versionversion=65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8 <089e05b644d5aa786c21af467c80b24d691becb1
- Affected versionversion=65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8 <3303e5c6501e3638ded8e9402d703805b00ce64e
- Affected versionversion=65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8 <752e214b2c6f15b40b0d873a2ce27733ce0884c6
- Affected versionversion=65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8 <8ec4d9c5a5cf4b61fc087f871465b1f79b393325
- Affected versionversion=65ff5b7ddf0541f2b6e5cc59c47bfbf6cbcd91b8 <ac99781115d37d10894653b47941d9d8fc26fa64
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