md/raid1: fix writes_pending and barrier reference leaks on write failures
CVE-2026-72440 · published 15 Aug 2026
How serious is it
- Severity: high, CVSS score 7.1 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-72440?
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: 5aa705039c4fca84575539bfa2b8a28454a3d2ca to < 921e2baa626d1504bf30295816aaeb90ac8c82f4, 5aa705039c4fca84575539bfa2b8a28454a3d2ca to < a846affa813013204d0cce0cfdaeb99e8fcce188, 5aa705039c4fca84575539bfa2b8a28454a3d2ca to < 7a450460687919e79b5f8503bdeb13ecf4cca311, 5aa705039c4fca84575539bfa2b8a28454a3d2ca to < bffbbfcbd9393e315a7a4286dcd70e875265db9a
- 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/raid1: fix writes_pending and barrier reference leaks on write failures
raid1_make_request() acquires a writes_pending reference with
md_write_start() before calling raid1_write_request(). Several failure
paths in raid1_write_request() complete the bio and return without
reaching the normal write completion path, causing the corresponding
md_write_end() to be skipped.
Make raid1_write_request() return a status indicating whether the write
request was successfully queued. This allows raid1_make_request() to
call md_write_end() when raid1_write_request() fails.
Additionally, if wait_blocked_rdev() fails after wait_barrier()
succeeds, the associated barrier reference is not released.
Call allow_barrier() before returning from that path to keep the barrier
accounting balanced.
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/921e2baa626d1504bf30295816aaeb90ac8c82f4
- git.kernel.org/stable/c/a846affa813013204d0cce0cfdaeb99e8fcce188
- git.kernel.org/stable/c/7a450460687919e79b5f8503bdeb13ecf4cca311
- git.kernel.org/stable/c/bffbbfcbd9393e315a7a4286dcd70e875265db9a
- git.kernel.org/stable/c/8e065a1602511282fc0da2dc89445e0eb71a681c
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON