md: call __md_stop_writes in md_stop
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0dd84b319352bb8ba64752d4e45396d8b13e6018, 1678ca35b80a94d474fdc31e2497ce5d7ed52512, 661c01b2181d9413c799127f13143583b69f20fd.
Low priority for now. Upgrade to Linux Linux 0dd84b319352bb8ba64752d4e45396d8b13e6018, 1678ca35b80a94d474fdc31e2497ce5d7ed52512, 661c01b2181d9413c799127f13143583b69f20fd or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.12 and later · before 4.14.292
- linux linux kernel4.15 and later · before 4.19.257
- linux linux kernel4.20 and later · before 5.4.212
- linux linux kernel5.5 and later · before 5.10.140
- linux linux kernel5.11 and later · before 5.15.64
- linux linux kernel5.16 and later · before 5.19.6
- linux linux kernel6.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- 48df498daf62e1292868005675331929305067f0 and later · before 1678ca35b80a94d474fdc31e2497ce5d7ed52512affected · git
- 48df498daf62e1292868005675331929305067f0 and later · before 690b5c90fd2d81fd1d2b6110fa36783232f6dce2affected · git
- 48df498daf62e1292868005675331929305067f0 and later · before 8e7fb19f1a744fd34e982633ced756fee0498ef7affected · git
- 48df498daf62e1292868005675331929305067f0 and later · before a5a58fab556bfe618b4c9719eb85712d78c6cb10affected · git
- 48df498daf62e1292868005675331929305067f0 and later · before 661c01b2181d9413c799127f13143583b69f20fdaffected · git
- 48df498daf62e1292868005675331929305067f0 and later · before f42a9819ba84bed2e609a4dff56af37063dcabdcaffected · git
- 48df498daf62e1292868005675331929305067f0 and later · before 0dd84b319352bb8ba64752d4e45396d8b13e6018affected · git
- before 4.12not affected · semver
- 4.14.292 and later · up to and including 4.14.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.2-1 | 6.0.2-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49985Jun 18, 2025 · bpf: Don't use tnum_range on array range checking for poke descriptors28Monitor
- ← EarlierCVE-2022-49986Jun 18, 2025 · scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq22Monitor
- Later →CVE-2022-49989Jun 18, 2025 · xen/privcmd: fix error exit of privcmd_ioctl_dm_op()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0dd84b319352bb8ba64752d4e45396d8b13e6018 | Vendor (CNA) |
| Linux Linux | 1678ca35b80a94d474fdc31e2497ce5d7ed52512 | Vendor (CNA) |
| Linux Linux | 661c01b2181d9413c799127f13143583b69f20fd | Vendor (CNA) |
| Linux Linux | 690b5c90fd2d81fd1d2b6110fa36783232f6dce2 | Vendor (CNA) |
| Linux Linux | 8e7fb19f1a744fd34e982633ced756fee0498ef7 | Vendor (CNA) |
| Linux Linux | a5a58fab556bfe618b4c9719eb85712d78c6cb10 | Vendor (CNA) |
| Linux Linux | f42a9819ba84bed2e609a4dff56af37063dcabdc | Vendor (CNA) |
| debian:linux | 6.0.2-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/1678ca35b80a94d474fdc31e2497ce5d7ed52512
- git.kernel.org/stable/c/661c01b2181d9413c799127f13143583b69f20fd
- git.kernel.org/stable/c/690b5c90fd2d81fd1d2b6110fa36783232f6dce2
- git.kernel.org/stable/c/8e7fb19f1a744fd34e982633ced756fee0498ef7
- git.kernel.org/stable/c/a5a58fab556bfe618b4c9719eb85712d78c6cb10
- git.kernel.org/stable/c/f42a9819ba84bed2e609a4dff56af37063dcabdc
Vendor advisories and official records. Exploit/PoC links are deliberately left out.