CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures
Noroxi assessment
Priority: Monitor (action score 0/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.18% (FIRST EPSS).
- Fixed version: Linux Linux 5.16, 55dc3d1d6a9983867273d3531e3ddd743428db8d, b6667d925c274910423385042edf18f6788dbceb; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 5.16, 55dc3d1d6a9983867273d3531e3ddd743428db8d, b6667d925c274910423385042edf18f6788dbceb; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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/raid10: fix writes_pending leak on write request failures raid10_make_request() acquires a writes_pending reference with md_write_start() before dispatching write requests. Several failure paths in raid10_write_request() complete the bio and return without reaching the normal write completion path, causing the corresponding md_write_end() to be skipped. Make raid10_write_request() return a status indicating whether the write request was successfully queued. This allows raid10_make_request() to release the writes_pending reference with md_write_end() when a write request fails.
- Published
- Aug 15, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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.
—
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
- 39db562b3fedb93978a7e42dd216b306740959f8, 5.17affected
- c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and later · before 55dc3d1d6a9983867273d3531e3ddd743428db8daffected · git
- c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and later · before f076460c5205c9687059e5a3afeed37d2f2ceb6baffected · git
- c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and later · before b6667d925c274910423385042edf18f6788dbcebaffected · git
- c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and later · before c642583adc136d4c70ce3c65c3f43e847d26c776affected · git
- c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and later · before f94031c94eaebe14a7c9e91720064de0c5a54a6caffected · git
- c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and later · before e045d6ed33f8faa3e3dd6dc33c62ec01e3ad275daffected · git
- 5.15.111 and later · before 5.16affected · semver
- before 5.17not affected · semver
- 6.1.191 and later · up to and including 6.1.*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 | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72437Aug 15, 2026 · md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry0Monitor
- ← EarlierCVE-2026-72438Aug 15, 2026 · md/raid10: fix writes_pending and barrier reference leaks on discard failures30Monitor
- Later →CVE-2026-72440Aug 15, 2026 · md/raid1: fix writes_pending and barrier reference leaks on write failures28Monitor
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 | 5.16 | Vendor (CNA) |
| Linux Linux | 55dc3d1d6a9983867273d3531e3ddd743428db8d | Vendor (CNA) |
| Linux Linux | b6667d925c274910423385042edf18f6788dbceb | Vendor (CNA) |
| Linux Linux | c642583adc136d4c70ce3c65c3f43e847d26c776 | Vendor (CNA) |
| Linux Linux | e045d6ed33f8faa3e3dd6dc33c62ec01e3ad275d | Vendor (CNA) |
| Linux Linux | f076460c5205c9687059e5a3afeed37d2f2ceb6b | Vendor (CNA) |
| Linux Linux | f94031c94eaebe14a7c9e91720064de0c5a54a6c | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.1.5-1 · Debian:14 | 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/b6667d925c274910423385042edf18f6788dbceb
- git.kernel.org/stable/c/c642583adc136d4c70ce3c65c3f43e847d26c776
- git.kernel.org/stable/c/e045d6ed33f8faa3e3dd6dc33c62ec01e3ad275d
- git.kernel.org/stable/c/f076460c5205c9687059e5a3afeed37d2f2ceb6b
- git.kernel.org/stable/c/f94031c94eaebe14a7c9e91720064de0c5a54a6c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.