Metadata corruption via premature held_root updates
Published Aug 15, 2026 · Updated Aug 15, 2026
Metadata corruption in the Linux kernel allows local users to damage thin-pool metadata through snapshot operations after a commit failure. __reserve_metadata_snap() and __release_metadata_snap() update held_root in the block-manager buffer before commit success, so abort_transaction flushes an invalid root. Reaching the flaw requires CAP_SYS_ADMIN in the initial user namespace and a failing metadata commit; the resulting reference-count errors can force repair and cause data loss.
Summary
What happened
Metadata corruption in the Linux kernel allows local users to damage thin-pool metadata through snapshot operations after a commit failure. __reserve_metadata_snap() and __release_metadata_snap() update held_root in the block-manager buffer before commit success, so abort_transaction flushes an invalid root. Reaching the flaw requires CAP_SYS_ADMIN in the initial user namespace and a failing metadata commit; the resulting reference-count errors can force repair and cause data loss.
The record
- CVE
- CVE-2026-72108
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-367, T1565
- Attack vector
- local
- Privileges
- admin
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.2
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <3dc9ae1029320d77472c44965e572f176949cd63
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <4af993468193cf4cd32ba5748786e7801945f7d2
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <5bcd4d3058ebaf46ad2e163829d87dd4870c7a45
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <5efb1a7734ed4035fa4fdc3716bdb84621f27cf6
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <7f76245960a332f39b08cc556e675d1765dc5bbb
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <9f1a0d27586ceab055e6b050e3731ce3c6b2c4f0
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <abf2fae92cbe68945028987d498cc72f8f0e23a8
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <b5f9a31c51cbb374a1713c3494f8660ab070f035
What conditions does exploitation require?
What is affected?
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