Service interruption via concurrent raid1d teardown
Published Jun 18, 2025 · Updated May 11, 2026
Race condition in Linux kernel MD 4.12 through 6.0-rc2 allows local users to interrupt service during device-mapper RAID teardown. In md_stop in drivers/md/md.c, the destructor calls __md_stop without first invoking __md_stop_writes, so raid1d can continue after teardown frees resources. Triggering the race requires local access and an active MD RAID configuration; the public record does not specify whether the KASAN-detected fault crashes or hangs the kernel.
Summary
What happened
Race condition in Linux kernel MD 4.12 through 6.0-rc2 allows local users to interrupt service during device-mapper RAID teardown. In md_stop in drivers/md/md.c, the destructor calls __md_stop without first invoking __md_stop_writes, so raid1d can continue after teardown frees resources. Triggering the race requires local access and an active MD RAID configuration; the public record does not specify whether the KASAN-detected fault crashes or hangs the kernel.
The record
- CVE
- CVE-2022-49987
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 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=4.12
- Affected versionversion=48df498daf62e1292868005675331929305067f0 <0dd84b319352bb8ba64752d4e45396d8b13e6018
- Affected versionversion=48df498daf62e1292868005675331929305067f0 <1678ca35b80a94d474fdc31e2497ce5d7ed52512
- Affected versionversion=48df498daf62e1292868005675331929305067f0 <661c01b2181d9413c799127f13143583b69f20fd
- Affected versionversion=48df498daf62e1292868005675331929305067f0 <690b5c90fd2d81fd1d2b6110fa36783232f6dce2
- Affected versionversion=48df498daf62e1292868005675331929305067f0 <8e7fb19f1a744fd34e982633ced756fee0498ef7
- Affected versionversion=48df498daf62e1292868005675331929305067f0 <a5a58fab556bfe618b4c9719eb85712d78c6cb10
- Affected versionversion=48df498daf62e1292868005675331929305067f0 <f42a9819ba84bed2e609a4dff56af37063dcabdc
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
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