CVE-2026-72438: Linux kernel · md/raid10: fix writes_pending and barrier reference leaks on discard failures
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in fea33968592559a55a3f5a96a6386bebcaf988a8 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in fea33968592559a55a3f5a96a6386bebcaf988a8, d1324b41dabd26787559efaeb430643c627c1eb0, 393d687131d8aa8c7e4de2cb494438e145d20fc2 +3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix writes_pending and barrier reference leaks on discard failures raid10_make_request() acquires a writes_pending reference with md_write_start() before calling raid10_handle_discard(). Several failure paths in raid10_handle_discard() complete the bio and return without releasing the corresponding reference, causing md_write_end() to be skipped. Call md_write_end() before returning from these failure paths to keep writes_pending accounting balanced. Additionally, discard split allocation failures can occur after wait_barrier() succeeds. Those paths return without calling allow_barrier(), leaking the associated barrier reference. Release the barrier before returning from those paths.
References
- git.kernel.org/stable/c/80ac31cce55432034a9eb98262c92ace7866e494 (opens in a new tab)
- git.kernel.org/stable/c/fea33968592559a55a3f5a96a6386bebcaf988a8 (opens in a new tab)
- git.kernel.org/stable/c/11b35d1906a7277a3d64afe34224133b44327328 (opens in a new tab)
- git.kernel.org/stable/c/d1324b41dabd26787559efaeb430643c627c1eb0 (opens in a new tab)
- git.kernel.org/stable/c/393d687131d8aa8c7e4de2cb494438e145d20fc2 (opens in a new tab)