drbd: fix "LOGIC BUG" in drbd_al_begin_io_nonblock()
Summary
| CVE | CVE-2026-23356 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-03-25 11:16:34 UTC |
| Updated | 2026-04-18 09:16:20 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: drbd: fix "LOGIC BUG" in drbd_al_begin_io_nonblock() Even though we check that we "should" be able to do lc_get_cumulative() while holding the device->al_lock spinlock, it may still fail, if some other code path decided to do lc_try_lock() with bad timing. If that happened, we logged "LOGIC BUG for enr=...", but still did not return an error. The rest of the code now assumed that this request has references for the relevant activity log extents. The implcations are that during an active resync, mutual exclusivity of resync versus application IO is not guaranteed. And a potential crash at this point may not realizs that these extents could have been target of in-flight IO and would need to be resynced just in case. Also, once the request completes, it will give up activity log references it does not even hold, which will trigger a BUG_ON(refcnt == 0) in lc_put(). Fix: Do not crash the kernel for a condition that is harmless during normal operation: also catch "e->refcnt == 0", not only "e == NULL" when being noisy about "al_complete_io() called on inactive extent %u\n". And do not try to be smart and "guess" whether something will work, then be surprised when it does not. Deal with the fact that it may or may not work. If it does not, remember a possible "partially in activity log" state (only possible for requests that cross extent boundaries), and return an error code from drbd_al_begin_io_nonblock(). A latter call for the same request will then resume from where we left off. |
Risk And Classification
EPSS: 0.000320000 probability, percentile 0.090980000 (date 2026-04-18)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 933d161baa3794547adee621c0bf52cbf2c1b3cd git | Not specified |
| CNA | Linux | Linux | affected 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 cf01aa6288e1190f89865e765056e2a9d8190639 git | Not specified |
| CNA | Linux | Linux | affected 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 7752569fc78e89794ce28946529850282233f99d git | Not specified |
| CNA | Linux | Linux | affected 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 e91d8d6565b7819d13dab21d4dbed5b45efba59b git | Not specified |
| CNA | Linux | Linux | affected 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 eef1390125b660b8b61f9f227a03bb9c5e6d36a5 git | Not specified |
| CNA | Linux | Linux | affected 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 d1ef3aed4df2ef1fe46befd8f2da9a6ec5445508 git | Not specified |
| CNA | Linux | Linux | affected 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 f558e5404a72054b525dced1a0c66aa95a144153 git | Not specified |
| CNA | Linux | Linux | affected 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 ab140365fb62c0bdab22b2f516aff563b2559e3b git | Not specified |
| CNA | Linux | Linux | affected 3.10 | Not specified |
| CNA | Linux | Linux | unaffected 3.10 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.253 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.203 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.167 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.130 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.77 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.17 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.7 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/cf01aa6288e1190f89865e765056e2a9d8190639 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/eef1390125b660b8b61f9f227a03bb9c5e6d36a5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d1ef3aed4df2ef1fe46befd8f2da9a6ec5445508 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/7752569fc78e89794ce28946529850282233f99d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ab140365fb62c0bdab22b2f516aff563b2559e3b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e91d8d6565b7819d13dab21d4dbed5b45efba59b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/933d161baa3794547adee621c0bf52cbf2c1b3cd | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f558e5404a72054b525dced1a0c66aa95a144153 | 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.