Kernel crash via invalid clustered bitmap metadata
Published Feb 26, 2025 · Updated May 11, 2026
Improper bitmap validation in Linux 3.5 through 5.18.2 allows local users to crash a clustered-md host via malformed metadata. md_bitmap_read_sb assigns a zero chunk size despite rejecting bad bitmap magic, causing md_bitmap_create to divide by zero while loading another cluster slot. The failure requires a clustered RAID array and the ability to corrupt its on-disk bitmap metadata; non-clustered arrays handle invalid metadata in userspace.
Summary
What happened
Improper bitmap validation in Linux 3.5 through 5.18.2 allows local users to crash a clustered-md host via malformed metadata. md_bitmap_read_sb assigns a zero chunk size despite rejecting bad bitmap magic, causing md_bitmap_create to divide by zero while loading another cluster slot. The failure requires a clustered RAID array and the ability to corrupt its on-disk bitmap metadata; non-clustered arrays handle invalid metadata in userspace.
The record
- CVE
- CVE-2022-49526
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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.5
- Affected versionversion=ef99bf480de9bde9d3b2afdf05324670fab4e571 <0959aa00f9765bd8c654b1365012e41b51c733cc
- Affected versionversion=ef99bf480de9bde9d3b2afdf05324670fab4e571 <27f672af28a8e9b783ff7f0eaf7ef2fbd5a2f4ba
- Affected versionversion=ef99bf480de9bde9d3b2afdf05324670fab4e571 <422e8f7ba1e08c8e0e88d375bcb550bc2bbfe96d
- Affected versionversion=ef99bf480de9bde9d3b2afdf05324670fab4e571 <cf9392282a2cf5a8d83dd1c5aa1a097e12f172bc
- Affected versionversion=ef99bf480de9bde9d3b2afdf05324670fab4e571 <d8f1558e1daf54f53a90b4c5700ae3e3a4b13412
- Affected versionversion=ef99bf480de9bde9d3b2afdf05324670fab4e571 <e68cb83a57a458b01c9739e2ad9cb70b04d1e6d2
- Affected versionversion=ef99bf480de9bde9d3b2afdf05324670fab4e571 <e69e93120f6219b9cc4fba3b515b6ababd8548aa
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.
Public exploit references
- Clustered-md faulty-injection 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