Kernel crash via unlocked LED brightness access
Published Dec 27, 2024 · Updated May 11, 2026
Race condition in the Linux kernel LED class allows local users to crash the kernel by reading LED brightness during HID setup. The brightness_show() and max_brightness_show() paths access led_cdev fields without holding led_access while HID registration can leave the device state unavailable. Triggering the race requires local access to the LED sysfs attribute during concurrent HID device addition, and the resulting NULL dereference interrupts the system.
Summary
What happened
Race condition in the Linux kernel LED class allows local users to crash the kernel by reading LED brightness during HID setup. The brightness_show() and max_brightness_show() paths access led_cdev fields without holding led_access while HID registration can leave the device state unavailable. Triggering the race requires local access to the LED sysfs attribute during concurrent HID device addition, and the resulting NULL dereference interrupts the system.
The record
- CVE
- CVE-2024-56587
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- 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=2.6.26
- Affected versionversion=29d76dfa29fe22583aefddccda0bc56aa81035dc <4ca7cd938725a4050dcd62ae9472e931d603118d
- Affected versionversion=29d76dfa29fe22583aefddccda0bc56aa81035dc <50d9f68e4adf86901cbab1bd5b91f710aa9141b9
- Affected versionversion=29d76dfa29fe22583aefddccda0bc56aa81035dc <84b42d5b5fcd767c9b7f30b0b32065ed949fe804
- Affected versionversion=29d76dfa29fe22583aefddccda0bc56aa81035dc <b8283d52ed15c02bb2eb9b1b8644dcc34f8e98f1
- Affected versionversion=29d76dfa29fe22583aefddccda0bc56aa81035dc <bb4a6236a430cfc3713f470f3a969f39d6d4ca25
- Affected versionversion=29d76dfa29fe22583aefddccda0bc56aa81035dc <ddcfc5708da9972ac23a9121b3d819b0a53d6f21
- Affected versionversion=29d76dfa29fe22583aefddccda0bc56aa81035dc <f6d6fb563e4be245a17bc4261a4b294e8bf8a31e
What conditions does exploitation require?
What is affected?
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