CVE-2022-49987
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
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 48df498daf62e1292868005675331929305067f0; < 1678ca35b80a94d474fdc31e2497ce5d7ed52512 (affected, git) ≥ 48df498daf62e1292868005675331929305067f0; < 690b5c90fd2d81fd1d2b6110fa36783232f6dce2 (affected, git) ≥ 48df498daf62e1292868005675331929305067f0; < 8e7fb19f1a744fd34e982633ced756fee0498ef7 (affected, git) ≥ 48df498daf62e1292868005675331929305067f0; < a5a58fab556bfe618b4c9719eb85712d78c6cb10 (affected, git) ≥ 48df498daf62e1292868005675331929305067f0; < 661c01b2181d9413c799127f13143583b69f20fd (affected, git) ≥ 48df498daf62e1292868005675331929305067f0; < f42a9819ba84bed2e609a4dff56af37063dcabdc (affected, git) ≥ 48df498daf62e1292868005675331929305067f0; < 0dd84b319352bb8ba64752d4e45396d8b13e6018 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
4.12 (affected) ≥ 0; < 4.12 (unaffected, semver) ≥ 4.14.292; ≤ 4.14.* (unaffected, semver) ≥ 4.19.257; ≤ 4.19.* (unaffected, semver) ≥ 5.4.212; ≤ 5.4.* (unaffected, semver) ≥ 5.10.140; ≤ 5.10.* (unaffected, semver) ≥ 5.15.64; ≤ 5.15.* (unaffected, semver) ≥ 5.19.6; ≤ 5.19.* (unaffected, semver) ≥ 6.0; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/1678ca35b80a94d474fdc31e2497ce5d7ed52512CNA: Linux
- https://git.kernel.org/stable/c/690b5c90fd2d81fd1d2b6110fa36783232f6dce2CNA: Linux
- https://git.kernel.org/stable/c/8e7fb19f1a744fd34e982633ced756fee0498ef7CNA: Linux
- https://git.kernel.org/stable/c/a5a58fab556bfe618b4c9719eb85712d78c6cb10CNA: Linux
- https://git.kernel.org/stable/c/661c01b2181d9413c799127f13143583b69f20fdCNA: Linux
- https://git.kernel.org/stable/c/f42a9819ba84bed2e609a4dff56af37063dcabdcCNA: Linux
- https://git.kernel.org/stable/c/0dd84b319352bb8ba64752d4e45396d8b13e6018CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.