Kernel panic via unavailable UBD driver data
Published Dec 27, 2024 · Updated May 11, 2026
Linux contains a UBD device-release flaw that allows local users to trigger a User Mode Linux kernel panic by removing a block device. ubd_device_release() calls dev_get_drvdata() after the core has cleared the device's driver data, then passes the invalid UBD pointer to blk_mq_free_tag_set(). The path requires a running User Mode Linux instance with mconsole enabled and an idle removable UBD; the host kernel remains unaffected by a guest crash.
Summary
What happened
Linux contains a UBD device-release flaw that allows local users to trigger a User Mode Linux kernel panic by removing a block device. ubd_device_release() calls dev_get_drvdata() after the core has cleared the device's driver data, then passes the invalid UBD pointer to blk_mq_free_tag_set(). The path requires a running User Mode Linux instance with mconsole enabled and an idle removable UBD; the host kernel remains unaffected by a guest crash.
The record
- CVE
- CVE-2024-53184
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=0998d0631001288a5974afc0b2a5f568bcdecb4d <16cf8511680809a9f20b3dd224c06d482648f9e2
- Affected versionversion=0998d0631001288a5974afc0b2a5f568bcdecb4d <23d742a3fcd4781eed015a3a93e6a0e3ab1ef2a8
- Affected versionversion=0998d0631001288a5974afc0b2a5f568bcdecb4d <2d194d951895df214e066d08146e77cb6e02c1d4
- Affected versionversion=0998d0631001288a5974afc0b2a5f568bcdecb4d <300e277e463e6326938dd55ea560eafa0f5c88a5
- Affected versionversion=0998d0631001288a5974afc0b2a5f568bcdecb4d <509ba8746f812e45a05034ba18b73db574693d11
- Affected versionversion=0998d0631001288a5974afc0b2a5f568bcdecb4d <5727343348f34e11a7c5a2a944d5aa505731d876
- Affected versionversion=0998d0631001288a5974afc0b2a5f568bcdecb4d <5bee35e5389f450a7eea7318deb9073e9414d3b1
- Affected versionversion=0998d0631001288a5974afc0b2a5f568bcdecb4d <a5a75207efae4b558aaa34c288de7d6f2e926b4b
- Affected versionversion=0998d0631001288a5974afc0b2a5f568bcdecb4d <e6e5a4cded9bef3a1b0a4fac815b7176eb9a18ec
- Affected versionversion=3.6
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
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