Local kernel crash via unchecked bitmap counter
Published Sep 18, 2025 · Updated Sep 18, 2025
NULL pointer dereference in Linux kernel md bitmap code allows local users to crash the system during bitmap-backed array I/O. md_bitmap_startwrite() and md_bitmap_endwrite() dereference a counter pointer returned by md_bitmap_get_counter() without checking for NULL after bitmap-page lookup failure. Low-privileged local access and an md array using a write-intent bitmap are required; the documented consequence is a kernel crash only.
Summary
What happened
NULL pointer dereference in Linux kernel md bitmap code allows local users to crash the system during bitmap-backed array I/O. md_bitmap_startwrite() and md_bitmap_endwrite() dereference a counter pointer returned by md_bitmap_get_counter() without checking for NULL after bitmap-page lookup failure. Low-privileged local access and an md array using a write-intent bitmap are required; the documented consequence is a kernel crash only.
The record
- CVE
- CVE-2022-50402
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <100caacfa0ed26e061954c90cdc835d42f709536
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <21e9aac9a74d30907d44bae0d24c036cb3819406
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3bd548e5b819b8c0f2c9085de775c5c7bff9052f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5d8d046f3dba939e74e2414f009df426700430ed
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <99bef41f8e8d1d52b5cb34f2f193f1346192752b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b621d17fe8b079574c773800148fb86907f3445d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ff3b7e12bc9f50de05c9d82b5b79e23e5be888f1
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.
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