Kernel crash via brd initialization use-after-free
Published Dec 28, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux brd block driver allows local users to crash the kernel during failed module initialization. brd_init creates RAM disks before block-device registration succeeds, then frees visible disks after a later allocation error while pending or concurrent closes retain references to the released operations table. Triggering requires local access, a brd initialization failure, and a deferred or concurrent close of an exposed RAM-disk device; the demonstrated consequence is a kernel oops that can become a panic.
Summary
What happened
Use-after-free in the Linux brd block driver allows local users to crash the kernel during failed module initialization. brd_init creates RAM disks before block-device registration succeeds, then frees visible disks after a later allocation error while pending or concurrent closes retain references to the released operations table. Triggering requires local access, a brd initialization failure, and a deferred or concurrent close of an exposed RAM-disk device; the demonstrated consequence is a kernel oops that can become a panic.
The record
- CVE
- CVE-2024-56693
- Published
- Dec 28, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=5.14
- Affected versionversion=7f9b348cb5e94259acdcbafbcaed55d3bb515304 <259bf925583ec9e3781df778cadf00594095090d
- Affected versionversion=7f9b348cb5e94259acdcbafbcaed55d3bb515304 <410896624db639500f24f46478b4bfa05c76bf56
- Affected versionversion=7f9b348cb5e94259acdcbafbcaed55d3bb515304 <41219c147df8bbd6591f59af5d695fb6c9a1cbff
- Affected versionversion=7f9b348cb5e94259acdcbafbcaed55d3bb515304 <63dfd728b30f79495dacc886127695a379805152
- Affected versionversion=7f9b348cb5e94259acdcbafbcaed55d3bb515304 <826cc42adf44930a633d11a5993676d85ddb0842
- Affected versionversion=7f9b348cb5e94259acdcbafbcaed55d3bb515304 <c0c2744cd2939ec5999c51dbaf2af16886548b7b
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