md/raid10: fix writes_pending and barrier reference leaks on discard failures
Summary
| CVE | CVE-2026-72438 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:22:17 UTC |
| Updated | 2026-10-21 13:19:37 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7.5 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS: 0.004600000 probability, percentile 0.384590000 (date 2026-10-16)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | CNA | DECLARED | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected c9aa889b035fca4598ae985a0f0c76ebbb547ad2 80ac31cce55432034a9eb98262c92ace7866e494 git | Not specified |
| CNA | Linux | Linux | affected c9aa889b035fca4598ae985a0f0c76ebbb547ad2 fea33968592559a55a3f5a96a6386bebcaf988a8 git | Not specified |
| CNA | Linux | Linux | affected c9aa889b035fca4598ae985a0f0c76ebbb547ad2 11b35d1906a7277a3d64afe34224133b44327328 git | Not specified |
| CNA | Linux | Linux | affected c9aa889b035fca4598ae985a0f0c76ebbb547ad2 d1324b41dabd26787559efaeb430643c627c1eb0 git | Not specified |
| CNA | Linux | Linux | affected c9aa889b035fca4598ae985a0f0c76ebbb547ad2 393d687131d8aa8c7e4de2cb494438e145d20fc2 git | Not specified |
| CNA | Linux | Linux | affected 39db562b3fedb93978a7e42dd216b306740959f8 git | Not specified |
| CNA | Linux | Linux | affected 5.15.111 5.16 semver | Not specified |
| CNA | Linux | Linux | affected 5.17 | Not specified |
| CNA | Linux | Linux | unaffected 5.17 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.111 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.5 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/80ac31cce55432034a9eb98262c92ace7866e494 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/11b35d1906a7277a3d64afe34224133b44327328 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/fea33968592559a55a3f5a96a6386bebcaf988a8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d1324b41dabd26787559efaeb430643c627c1eb0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/393d687131d8aa8c7e4de2cb494438e145d20fc2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.