CVE-2026-23356 — drbd: fix "LOGIC BUG" in drbd_al_begin_io_nonblock()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 3.10≥ 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 and < ab140365fb62c0bdab22b2f516aff563b2559e3b≥ 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 and < f558e5404a72054b525dced1a0c66aa95a144153≥ 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 and < d1ef3aed4df2ef1fe46befd8f2da9a6ec5445508≥ 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 and < eef1390125b660b8b61f9f227a03bb9c5e6d36a5≥ 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 and < e91d8d6565b7819d13dab21d4dbed5b45efba59b≥ 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 and < 7752569fc78e89794ce28946529850282233f99d≥ 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 and < cf01aa6288e1190f89865e765056e2a9d8190639 and 1 more≥ 08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 and < 933d161baa3794547adee621c0bf52cbf2c1b3cd |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 7.0-rc5version 7.0-rc7version 7.0-rc6≥ 3.10.1 and < 5.10.253version 7.0-rc4version 7.0-rc3version 7.0-rc2version 7.0-rc1 and 7 moreversion 3.10≥ 6.19 and < 6.19.7≥ 6.13 and < 6.18.17≥ 6.7 and < 6.12.77≥ 6.2 and < 6.6.130≥ 5.16 and < 6.1.167≥ 5.11 and < 5.15.203 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.13%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Analyzed → Modified
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 5.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
11 on the record
- git.kernel.org/stable/c/f558e5404a72054b525dced1a0c66aa95a144153
- git.kernel.org/stable/c/e91d8d6565b7819d13dab21d4dbed5b45efba59b
- git.kernel.org/stable/c/ab140365fb62c0bdab22b2f516aff563b2559e3b
- git.kernel.org/stable/c/eef1390125b660b8b61f9f227a03bb9c5e6d36a5
- git.kernel.org/stable/c/7752569fc78e89794ce28946529850282233f99d
- git.kernel.org/stable/c/933d161baa3794547adee621c0bf52cbf2c1b3cd
- git.kernel.org/stable/c/cf01aa6288e1190f89865e765056e2a9d8190639
- git.kernel.org/stable/c/d1ef3aed4df2ef1fe46befd8f2da9a6ec5445508
- nvd.nist.gov/vuln/detail/CVE-2026-23356
- github.com/advisories/GHSA-rp6p-x9w7-2rqg
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 7h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 7h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-23356 is "drbd: fix "LOGIC BUG" in drbd_al_begin_io_nonblock()", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.