Kernel panic via null driver-name cleanup
Published Oct 21, 2024 · Updated May 23, 2026
NULL pointer dereference in the Linux kernel driver core allows local users to trigger a kernel panic during driver registration. If kasprintf fails in module_add_driver, its exit path removes a second sysfs link with a null driver_name, causing kernfs_name_hash to pass that pointer to strlen. The demonstrated path requires local access, driver loading, and an injected allocation failure; the published record does not establish direct control of that failure.
Summary
What happened
NULL pointer dereference in the Linux kernel driver core allows local users to trigger a kernel panic during driver registration. If kasprintf fails in module_add_driver, its exit path removes a second sysfs link with a null driver_name, causing kernfs_name_hash to pass that pointer to strlen. The demonstrated path requires local access, driver loading, and an injected allocation failure; the published record does not establish direct control of that failure.
The record
- CVE
- CVE-2024-47688
- Published
- Oct 21, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=28f5a08600d0ea6831629d450193c4045094e729 <b8e45b910525704010d10c9dcbf2abf3005aa97c
- Affected versionversion=51dacb1b0467b616463a334cbcd048f5710ba2aa
- Affected versionversion=6.10
- Affected versionversion=6.6.33 <6.6.54
- Affected versionversion=6.9.4 <6.10
- Affected versionversion=85d2b0aa170351380be39fe4ff7973df1427fe76 <18ec12c97b39ff6aa15beb8d2b25d15cd44b87d8
- Affected versionversion=85d2b0aa170351380be39fe4ff7973df1427fe76 <4b5d48b7a29cc6d508121a4b4e0c97a891e5273c
- Affected versionversion=85d2b0aa170351380be39fe4ff7973df1427fe76 <dcb9d581dee4c23f2378b6650511ece80dda4e2f
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