CVE-2022-49987
published 2025-06-18CVE-2022-49987: In the Linux kernel, the following vulnerability has been resolved: md: call __md_stop_writes in md_stop From the link [1], we can see raid1d was running even…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.3th percentile
In the Linux kernel, the following vulnerability has been resolved:
md: call __md_stop_writes in md_stop
From the link [1], we can see raid1d was running even after the path
raid_dtr -> md_stop -> __md_stop.
Let's stop write first in destructor to align with normal md-raid to
fix the KASAN issue.
[1]. https://lore.kernel.org/linux-raid/CAPhsuW5gc4AakdGNdF8ubpezAuDLFOYUO_sfMZcec6hQFm8nhg@mail.gmail.com/T/#m7f12bf90481c02c6d2da68c64aeed4779b7df74a
Affected
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.2-1 (bookworm) | linux 6.0.2-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 48df498daf62e1292868005675331929305067f0 < 1678ca35b80a94d474fdc31e2497ce5d7ed52512 | 1678ca35b80a94d474fdc31e2497ce5d7ed52512 |
| linux | linux | >= 48df498daf62e1292868005675331929305067f0 < 690b5c90fd2d81fd1d2b6110fa36783232f6dce2 | 690b5c90fd2d81fd1d2b6110fa36783232f6dce2 |
| linux | linux | >= 48df498daf62e1292868005675331929305067f0 < 8e7fb19f1a744fd34e982633ced756fee0498ef7 | 8e7fb19f1a744fd34e982633ced756fee0498ef7 |
| linux | linux | >= 48df498daf62e1292868005675331929305067f0 < a5a58fab556bfe618b4c9719eb85712d78c6cb10 | a5a58fab556bfe618b4c9719eb85712d78c6cb10 |
| linux | linux | >= 48df498daf62e1292868005675331929305067f0 < 661c01b2181d9413c799127f13143583b69f20fd | 661c01b2181d9413c799127f13143583b69f20fd |
| linux | linux | >= 48df498daf62e1292868005675331929305067f0 < f42a9819ba84bed2e609a4dff56af37063dcabdc | f42a9819ba84bed2e609a4dff56af37063dcabdc |
| linux | linux | >= 48df498daf62e1292868005675331929305067f0 < 0dd84b319352bb8ba64752d4e45396d8b13e6018 | 0dd84b319352bb8ba64752d4e45396d8b13e6018 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.140-1 | 5.10.140-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 4.12 < 4.14.292 | 4.14.292 |
| linux | linux_kernel | >= 4.15 < 4.19.257 | 4.19.257 |
| linux | linux_kernel | >= 4.20 < 5.4.212 | 5.4.212 |
| linux | linux_kernel | >= 5.11 < 5.15.64 | 5.15.64 |
| linux | linux_kernel | >= 5.16 < 5.19.6 | 5.19.6 |
| linux | linux_kernel | >= 5.5 < 5.10.140 | 5.10.140 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: md: call __md_stop_writes in md_stop
vendor_redhat·2025-06-18·CVSS 5.5
CVE-2022-49987 [MEDIUM] kernel: md: call __md_stop_writes in md_stop
kernel: md: call __md_stop_writes in md_stop
In the Linux kernel, the following vulnerability has been resolved:
md: call __md_stop_writes in md_stop
From the link [1], we can see raid1d was running even after the path
raid_dtr -> md_stop -> __md_stop.
Let's stop write first in destructor to align with normal md-raid to
fix the KASAN issue.
[1]. https://lore.kernel.org/linux-raid/CAPhsuW5gc4AakdGNdF8ubpezAuDLFOYUO_sfMZcec6hQFm8nhg@mail.gmail.com/T/#m7f12bf90481c02c6d2da68c64aeed4779b7df74a
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Out of support scope
Package: kernel (Red Hat Enterprise Linux 7) - Not affected
Package: kernel-rt (Red Hat Enterprise Linux 7) - Not affected
Package: kernel (Red Hat Enterprise Linux 8) -
Debian
CVE-2022-49987: linux - In the Linux kernel, the following vulnerability has been resolved: md: call __...
vendor_debian·2022·CVSS 5.5
CVE-2022-49987 [MEDIUM] CVE-2022-49987: linux - In the Linux kernel, the following vulnerability has been resolved: md: call __...
In the Linux kernel, the following vulnerability has been resolved: md: call __md_stop_writes in md_stop From the link [1], we can see raid1d was running even after the path raid_dtr -> md_stop -> __md_stop. Let's stop write first in destructor to align with normal md-raid to fix the KASAN issue. [1]. https://lore.kernel.org/linux-raid/CAPhsuW5gc4AakdGNdF8ubpezAuDLFOYUO_sfMZcec6hQFm8nhg@mail.gmail.com/T/#m7f12bf90481c02c6d2da68c64aeed4779b7df74a
Scope: local
bookworm: resolved (fixed in 6.0.2-1)
bullseye: resolved (fixed in 5.10.140-1)
forky: resolved (fixed in 6.0.2-1)
sid: resolved (fixed in 6.0.2-1)
trixie: resolved (fixed in 6.0.2-1)
GHSA
GHSA-x238-pmq6-pv77: In the Linux kernel, the following vulnerability has been resolved:
md: call __md_stop_writes in md_stop
From the link [1], we can see raid1d was ru
ghsa_unreviewed·2025-06-18
CVE-2022-49987 [MEDIUM] GHSA-x238-pmq6-pv77: In the Linux kernel, the following vulnerability has been resolved:
md: call __md_stop_writes in md_stop
From the link [1], we can see raid1d was ru
In the Linux kernel, the following vulnerability has been resolved:
md: call __md_stop_writes in md_stop
From the link [1], we can see raid1d was running even after the path
raid_dtr -> md_stop -> __md_stop.
Let's stop write first in destructor to align with normal md-raid to
fix the KASAN issue.
[1]. https://lore.kernel.org/linux-raid/CAPhsuW5gc4AakdGNdF8ubpezAuDLFOYUO_sfMZcec6hQFm8nhg@mail.gmail.com/T/#m7f12bf90481c02c6d2da68c64aeed4779b7df74a
OSV
CVE-2022-49987: In the Linux kernel, the following vulnerability has been resolved: md: call __md_stop_writes in md_stop From the link [1], we can see raid1d was runn
osv·2025-06-18·CVSS 5.5
CVE-2022-49987 [MEDIUM] CVE-2022-49987: In the Linux kernel, the following vulnerability has been resolved: md: call __md_stop_writes in md_stop From the link [1], we can see raid1d was runn
In the Linux kernel, the following vulnerability has been resolved: md: call __md_stop_writes in md_stop From the link [1], we can see raid1d was running even after the path raid_dtr -> md_stop -> __md_stop. Let's stop write first in destructor to align with normal md-raid to fix the KASAN issue. [1]. https://lore.kernel.org/linux-raid/CAPhsuW5gc4AakdGNdF8ubpezAuDLFOYUO_sfMZcec6hQFm8nhg@mail.gmail.com/T/#m7f12bf90481c02c6d2da68c64aeed4779b7df74a
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0dd84b319352bb8ba64752d4e45396d8b13e6018https://git.kernel.org/stable/c/1678ca35b80a94d474fdc31e2497ce5d7ed52512https://git.kernel.org/stable/c/661c01b2181d9413c799127f13143583b69f20fdhttps://git.kernel.org/stable/c/690b5c90fd2d81fd1d2b6110fa36783232f6dce2https://git.kernel.org/stable/c/8e7fb19f1a744fd34e982633ced756fee0498ef7https://git.kernel.org/stable/c/a5a58fab556bfe618b4c9719eb85712d78c6cb10https://git.kernel.org/stable/c/f42a9819ba84bed2e609a4dff56af37063dcabdc
2025-06-18
Published