Kernel crash via RBD lock-work requeue race
Published Jul 19, 2026 · Updated Jul 19, 2026
Race condition in the Linux Kernel RBD driver allows local users to crash the kernel during concurrent image unmapping. maybe_kick_acquire checks lock_dwork state and can requeue the work after cancellation, allowing rbd_acquire_lock to run after release paths free or reset device state. Triggering requires local low-privileged access and concurrent RBD lock and unmap activity; the published record identifies an assertion failure but does not demonstrate privilege escalation.
Summary
What happened
Race condition in the Linux Kernel RBD driver allows local users to crash the kernel during concurrent image unmapping. maybe_kick_acquire checks lock_dwork state and can requeue the work after cancellation, allowing rbd_acquire_lock to run after release paths free or reset device state. Triggering requires local low-privileged access and concurrent RBD lock and unmap activity; the published record identifies an assertion failure but does not demonstrate privilege escalation.
The record
- CVE
- CVE-2026-64112
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=0 <6.12.92
- Affected versionversion=0 <6.18.34
- Affected versionversion=0 <7.0.11
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3427d7ae38337066ce88b68302e285d344ab756b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9400efc76b42c751211974a25c91d2c19c65b01b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9dcd4f5c99b491c37be90b0bd9988db48225fb75
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9fc75b71fdd38465c76c6f6a884cdd4ae3c72d90
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.
Weakness, pattern, technique
No sourced classifications are available.
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