Kernel crash via lingering failed-RAID1 worker thread
Published Dec 24, 2025 · Updated Dec 24, 2025
NULL-pointer dereference in Linux kernel md/raid1 allows attackers to crash the kernel during shutdown after a RAID1 setup failure. The failed startup path frees RAID1 resources without unregistering the mdx_raid1 worker thread, which later dereferences released state in md_check_recovery. The condition requires a RAID1 array assembled only from an inactive disk to fail during startup and remain present until shutdown.
Summary
What happened
NULL-pointer dereference in Linux kernel md/raid1 allows attackers to crash the kernel during shutdown after a RAID1 setup failure. The failed startup path frees RAID1 resources without unregistering the mdx_raid1 worker thread, which later dereferences released state in md_check_recovery. The condition requires a RAID1 array assembled only from an inactive disk to fail during startup and remain present until shutdown.
The record
- CVE
- CVE-2022-50715
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 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 <0c7c7468c3ae222e297b7dc74d6ccb69c4d0183c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <10d713532ffc67b13df61ed9c138a8ce0a186236
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <110f14a7b2eb5b8aa9df5af2d629524f2a07d543
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <19d5a0e17aba92b10d895e40ec782768cf00da23
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <22be44212cad8be96860346882d8e694b0b437b6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a3cc41e05e8af340a2a759b168c29fffdb9194eb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b611ad14006e5be2170d9e8e611bf49dff288911
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d26364596db8f8b55277b2afb3952e05a4057a21
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d684ceb77311410aeaf5189d321f9f564838c49a
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
No sourced classifications are available.
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