md/raid10: fix writes_pending and barrier reference leaks on discard failures
CVE-2026-72438 · published 15 Aug 2026
How serious is it
- Severity: high, CVSS score 7.5 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-72438?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: c9aa889b035fca4598ae985a0f0c76ebbb547ad2 to < 80ac31cce55432034a9eb98262c92ace7866e494, c9aa889b035fca4598ae985a0f0c76ebbb547ad2 to < fea33968592559a55a3f5a96a6386bebcaf988a8, c9aa889b035fca4598ae985a0f0c76ebbb547ad2 to < 11b35d1906a7277a3d64afe34224133b44327328, c9aa889b035fca4598ae985a0f0c76ebbb547ad2 to < d1324b41dabd26787559efaeb430643c627c1eb0
- Linux Linux: 5.17
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/80ac31cce55432034a9eb98262c92ace7866e494
- git.kernel.org/stable/c/fea33968592559a55a3f5a96a6386bebcaf988a8
- git.kernel.org/stable/c/11b35d1906a7277a3d64afe34224133b44327328
- git.kernel.org/stable/c/d1324b41dabd26787559efaeb430643c627c1eb0
- git.kernel.org/stable/c/393d687131d8aa8c7e4de2cb494438e145d20fc2
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON