CVE-2026-64112

In the Linux kernel, the following vulnerability has been resolved: rbd: eliminate a race in lock_dwork draining on unmap Given how rbd_lock_add_request() and rbd_img_exclusive_lock() are written, lock_dwork may be (re)queued more than it's actually needed: for example in case a new I/O request comes in while we are in the middle of rbd_acquire_lock() on behalf of another I/O request. This is expected and with rbd_release_lock() preemptively canceling lock_dwork is benign under normal operation. A more problematic example is maybe_kick_acquire(): if (have_requests || delayed_work_pending(&rbd_dev->lock_dwork)) { dout("%s rbd_dev %p kicking lock_dwork\n", __func__, rbd_dev); mod_delayed_work(rbd_dev->task_wq, &rbd_dev->lock_dwork, 0); } It's not unrealistic for lock_dwork to get canceled right after delayed_work_pending() returns true and for mod_delayed_work() to requeue it right there anyway. This is a classic TOCTOU race. When it comes to unmapping the image, there is an implicit assumption of no self-initiated exclusive lock activity past the point of return from rbd_dev_image_unlock() which unlocks the lock if it happens to be held. This unlock is assumed to be final and lock_dwork (as well as all other exclusive lock tasks, really) isn't expected to get queued again. However, lock_dwork is canceled only in cancel_tasks_sync() (i.e. later in the unmap sequence) and on top of that the cancellation can get in effect nullified by maybe_kick_acquire(). This may result in rbd_acquire_lock() executing after rbd_dev_device_release() and rbd_dev_image_release() run and free and/or reset a bunch of things. One of the possible failure modes then is a violated rbd_assert(rbd_image_format_valid(rbd_dev->image_format)); in rbd_dev_header_info() which is called via rbd_dev_refresh() from rbd_post_acquire_action(). Redo exclusive lock task draining to provide saner semantics and try to meet the assumptions around rbd_dev_image_unlock().

• CWE-367

• https://git.kernel.org/stable/c/3427d7ae38337066ce88b68302e285d344ab756bPatch
• https://git.kernel.org/stable/c/9400efc76b42c751211974a25c91d2c19c65b01bPatch
• https://git.kernel.org/stable/c/9dcd4f5c99b491c37be90b0bd9988db48225fb75Patch
• https://git.kernel.org/stable/c/9fc75b71fdd38465c76c6f6a884cdd4ae3c72d90Patch

Published

Jul 19, 2026

Last Modified

Aug 12, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-64107In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64108In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64109In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-6411This vulnerability, in the MAXHUB Pivot client application v…7.3
• CVE-2026-64110In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64111In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2026-64113In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-64114In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64115In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-64116In the Linux kernel, the following vulnerability has been re…7.5
• CVE-2026-64117In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-64118In the Linux kernel, the following vulnerability has been re…8.4