Kernel crash via missing activity-log references
Published Mar 25, 2026 · Updated Mar 25, 2026
Reachable assertion in the Linux kernel's DRBD driver allows local users to crash the system during an active resynchronization. drbd_al_begin_io_nonblock() logs a failed lc_get_cumulative() call but continues without activity-log extent references, and completion releases references the request never held, triggering BUG_ON in lc_put(). Triggering requires local low-privileged access, DRBD activity, and a timing race with lc_try_lock(); the reported consequence is a kernel crash and possible missed resynchronization of in-flight I/O.
Summary
What happened
Reachable assertion in the Linux kernel's DRBD driver allows local users to crash the system during an active resynchronization. drbd_al_begin_io_nonblock() logs a failed lc_get_cumulative() call but continues without activity-log extent references, and completion releases references the request never held, triggering BUG_ON in lc_put(). Triggering requires local low-privileged access, DRBD activity, and a timing race with lc_try_lock(); the reported consequence is a kernel crash and possible missed resynchronization of in-flight I/O.
The record
- CVE
- CVE-2026-23356
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 <7752569fc78e89794ce28946529850282233f99d
- Affected versionversion=08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 <ab140365fb62c0bdab22b2f516aff563b2559e3b
- Affected versionversion=08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 <d1ef3aed4df2ef1fe46befd8f2da9a6ec5445508
- Affected versionversion=08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 <e91d8d6565b7819d13dab21d4dbed5b45efba59b
- Affected versionversion=08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 <eef1390125b660b8b61f9f227a03bb9c5e6d36a5
- Affected versionversion=08a1ddab6df7d3c7b6341774cb1cf4b21b96a214 <f558e5404a72054b525dced1a0c66aa95a144153
- Affected versionversion=3.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo