CVE-2026-64112
Received Received - Intake

Race Condition in Linux Kernel RBD Module

Vulnerability report for CVE-2026-64112, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-19

Last updated on: 2026-07-20

Assigner: kernel.org

Description

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().

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-19
Last Modified
2026-07-20
Generated
2026-07-20
AI Q&A
2026-07-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel *
linux_kernel rbd *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a race condition in the rbd (RADOS Block Device) lock_dwork draining process during unmap operations. The issue occurs when lock_dwork is requeued unnecessarily due to timing issues between I/O requests and lock acquisition, leading to a time-of-check-time-of-use (TOCTOU) race. This can cause the lock_dwork to execute after resources are freed, potentially violating assertions in the kernel code.

Detection Guidance

This vulnerability is specific to the Linux kernel's rbd (RADOS Block Device) module and involves a race condition during lock management. Detection requires checking kernel logs for rbd-related errors or crashes, particularly during image unmapping or lock operations. Monitor for kernel oops messages or system hangs related to rbd devices.

Impact Analysis

This vulnerability could lead to kernel crashes or instability if exploited, as it may cause invalid memory access or assertion failures. Systems using rbd devices might experience unexpected behavior or failures during unmap operations, potentially disrupting storage operations.

Compliance Impact

This vulnerability is specific to the Linux kernel's rbd (RADOS Block Device) module and involves a race condition in lock management during image unmapping. It does not directly impact compliance with standards like GDPR or HIPAA, as those focus on data protection, privacy, and security controls rather than kernel-level storage device operations.

Mitigation Strategies

Apply the latest kernel patches or updates that address this specific issue. If using Ceph RBD, consider temporarily disabling exclusive lock operations if they are not critical. Monitor kernel logs for any signs of the race condition occurring.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64112. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart