{"id":"CVE-2026-23356","summary":"drbd: fix \"LOGIC BUG\" in drbd_al_begin_io_nonblock()","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrbd: fix \"LOGIC BUG\" in drbd_al_begin_io_nonblock()\n\nEven though we check that we \"should\" be able to do lc_get_cumulative()\nwhile holding the device-\u003eal_lock spinlock, it may still fail,\nif some other code path decided to do lc_try_lock() with bad timing.\n\nIf that happened, we logged \"LOGIC BUG for enr=...\",\nbut still did not return an error.\n\nThe rest of the code now assumed that this request has references\nfor the relevant activity log extents.\n\nThe implcations are that during an active resync, mutual exclusivity of\nresync versus application IO is not guaranteed. And a potential crash\nat this point may not realizs that these extents could have been target\nof in-flight IO and would need to be resynced just in case.\n\nAlso, once the request completes, it will give up activity log references it\ndoes not even hold, which will trigger a BUG_ON(refcnt == 0) in lc_put().\n\nFix:\n\nDo not crash the kernel for a condition that is harmless during normal\noperation: also catch \"e-\u003erefcnt == 0\", not only \"e == NULL\"\nwhen being noisy about \"al_complete_io() called on inactive extent %u\\n\".\n\nAnd do not try to be smart and \"guess\" whether something will work, then\nbe surprised when it does not.\nDeal with the fact that it may or may not work.  If it does not, remember a\npossible \"partially in activity log\" state (only possible for requests that\ncross extent boundaries), and return an error code from\ndrbd_al_begin_io_nonblock().\n\nA latter call for the same request will then resume from where we left off.","modified":"2026-04-02T13:12:22.940218Z","published":"2026-03-25T10:27:40.454Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23356.json"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/7752569fc78e89794ce28946529850282233f99d"},{"type":"WEB","url":"https://git.kernel.org/stable/c/ab140365fb62c0bdab22b2f516aff563b2559e3b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/d1ef3aed4df2ef1fe46befd8f2da9a6ec5445508"},{"type":"WEB","url":"https://git.kernel.org/stable/c/e91d8d6565b7819d13dab21d4dbed5b45efba59b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/eef1390125b660b8b61f9f227a03bb9c5e6d36a5"},{"type":"WEB","url":"https://git.kernel.org/stable/c/f558e5404a72054b525dced1a0c66aa95a144153"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23356.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23356"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"08a1ddab6df7d3c7b6341774cb1cf4b21b96a214"},{"fixed":"7752569fc78e89794ce28946529850282233f99d"},{"fixed":"e91d8d6565b7819d13dab21d4dbed5b45efba59b"},{"fixed":"eef1390125b660b8b61f9f227a03bb9c5e6d36a5"},{"fixed":"d1ef3aed4df2ef1fe46befd8f2da9a6ec5445508"},{"fixed":"f558e5404a72054b525dced1a0c66aa95a144153"},{"fixed":"ab140365fb62c0bdab22b2f516aff563b2559e3b"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23356.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.10.0"},{"fixed":"6.1.167"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.130"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.77"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.17"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"6.19.7"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23356.json"}}],"schema_version":"1.7.5"}