Storage I/O hang via stale B-tree root
Published Oct 7, 2025 · Updated Oct 7, 2025
Denial of service in Linux kernel dm-thin before 6.2 allows local users to hang storage I/O after a metadata commit failure. When a commit writes some copied B-tree nodes but fails on another, pmd->root retains the new root and later lookup can cycle through stale metadata indefinitely. Low-privileged local access must trigger the failed commit and subsequent thin-pool read path; the resulting soft lockup can stall kernel workers and panic the host.
Summary
What happened
Denial of service in Linux kernel dm-thin before 6.2 allows local users to hang storage I/O after a metadata commit failure. When a commit writes some copied B-tree nodes but fails on another, pmd->root retains the new root and later lookup can cycle through stale metadata indefinitely. Low-privileged local access must trigger the failed commit and subsequent thin-pool read path; the resulting soft lockup can stall kernel workers and panic the host.
The record
- CVE
- CVE-2022-50534
- Published
- Oct 7, 2025
- Updated
- Oct 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2025CVE publishedPublication date reported by the CVE source.
- Oct 7, 2025Record 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 <3db757ffdd87ed8d7118b2250236a496502a660f
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <4b710e8481ade7c9200e94d3018e99dc42a0a0e8
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <7991dbff6849f67e823b7cc0c15e5a90b0549b9f
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <87d69b8824ca9b090f5a8ed47f758e8f6eecb871
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <94f01ecc2aa0be992865acc80ebb6701f731f955
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <a63ce4eca86fd207e3db07c00fb7ccf4adf1b230
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <b35a22760aa5008d82533e59b0f0b5eb1b02d4e5
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <b91f481300e3a10eaf66b94fc39b740928762aaf
- Affected versionversion=991d9fa02da0dd1f843dc011376965e0c8c6c9b5 <f758987ff0af3a4b5ee69e95cab6a5294e4367b0
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
- dm-thin metadata corruption reproducerproof of concept · demonstrated
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