CVE-2026-64112·Kernel vulnerability
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().
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.11
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.10% — in the bottom 1% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-64112 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.10%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.11
Fixed in: 7.0.11
How to fix this CVE
Update your Linux kernel to version 7.0.11 or later to resolve a race condition in the RBD (RADOS Block Device) exclusive lock mechanism that could cause kernel assertions and system instability during device unmapping. This patch eliminates a timing window where lock acquisition tasks could execute after device release, potentially corrupting internal state. Prioritize this update for systems actively using RBD storage.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check installed kernel version: uname -r
- Verify if RBD modules are loaded: lsmod | grep rbd
- Search kernel logs for RBD lock-related assertions: sudo dmesg | grep -i 'rbd.*lock\|image_format_valid'
- After patching, confirm new version is running: uname -r (should show 7.0.11 or later) and verify no RBD-related warnings in dmesg
FAQ
What is CVE-2026-64112?
This is a race condition vulnerability in the Linux kernel's RBD (RADOS Block Device) locking mechanism where lock acquisition tasks may execute after device unmapping, causing assertion failures and system instability. The issue stems from improper synchronization between lock task scheduling and device cleanup routines.
Is CVE-2026-64112 being actively exploited?
No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog and no public exploits are available. It is primarily a reliability issue affecting RBD storage users.
What versions of Kernel are affected by CVE-2026-64112?
Linux kernel versions 6.19 through 7.0.10 are vulnerable. The fix is included in kernel 7.0.11 and all later versions.
How do I check if my server is vulnerable to CVE-2026-64112?
Run 'uname -r' to check your kernel version. If it shows 6.19 or later but earlier than 7.0.11, you are vulnerable. Additionally, verify RBD usage with 'lsmod | grep rbd' to determine if this vulnerability could impact your system.
Does Defensia detect CVE-2026-64112?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-64112 will appear in your dashboard with remediation steps and affected version ranges.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-64112. Free for 1 server.
Get started free