Linux vulnerability

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.

Published 15 Aug 2026Updated 21 Sep 20264 sources
CVSS 7.5

What happened

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.

Affected versions

Linux: c9aa889b035fca4598ae985a0f0c76ebbb547ad2 through before fea33968592559a55a3f5a96a6386bebcaf988a8 (git); c9aa889b035fca4598ae985a0f0c76ebbb547ad2 through before 11b35d1906a7277a3d64afe34224133b44327328 (git); c9aa889b035fca4598ae985a0f0c76ebbb547ad2 through before d1324b41dabd26787559efaeb430643c627c1eb0 (git); c9aa889b035fca4598ae985a0f0c76ebbb547ad2 through before 393d687131d8aa8c7e4de2cb494438e145d20fc2 (git); 39db562b3fedb93978a7e42dd216b306740959f8 (git); 5.15.111 through before 5.16 (semver); 5.17 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.