Kernel crash via concurrent HID++ battery initialization
Published Feb 29, 2024 · Updated Aug 5, 2026
Race condition in the Linux kernel allows physically proximate attackers to crash a host through a malicious HID++ device. Concurrent hidpp_connect_event() paths can register two power supplies sharing hidpp->battery.desc, then receiver disconnection frees properties still used by power_supply_uevent(). Exploitation requires a Logitech-compatible Bluetooth or Unifying RF peripheral that can race device connection and disconnection without an operating-system account.
Summary
What happened
Race condition in the Linux kernel allows physically proximate attackers to crash a host through a malicious HID++ device. Concurrent hidpp_connect_event() paths can register two power supplies sharing hidpp->battery.desc, then receiver disconnection frees properties still used by power_supply_uevent(). Exploitation requires a Logitech-compatible Bluetooth or Unifying RF peripheral that can race device connection and disconnection without an operating-system account.
The record
- CVE
- CVE-2023-52478
- Published
- Feb 29, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-367, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 29, 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=3.19
- Affected versionversion=c39e3d5fc9dd3e16c6f59dd94d827540040de66d <093af62c023537f097d2ebdfaa0bc7c1a6e874e1
- Affected versionversion=c39e3d5fc9dd3e16c6f59dd94d827540040de66d <28ddc1e0b898291323b62d770b1b931de131a528
- Affected versionversion=c39e3d5fc9dd3e16c6f59dd94d827540040de66d <44481b244fcaa2b895a53081d6204c574720c38c
- Affected versionversion=c39e3d5fc9dd3e16c6f59dd94d827540040de66d <ca0c4cc1d215dc22ab0e738c9f017c650f3183f5
- Affected versionversion=c39e3d5fc9dd3e16c6f59dd94d827540040de66d <cd0e2bf7fb22fe9b989c59c42dca06367fd10e6b
- Affected versionversion=c39e3d5fc9dd3e16c6f59dd94d827540040de66d <dac501397b9d81e4782232c39f94f4307b137452
- Affected versionversion=c39e3d5fc9dd3e16c6f59dd94d827540040de66d <f7b2c7d9831af99369fe8ad9b2a68d78942f414e
- Affected versionversion=c39e3d5fc9dd3e16c6f59dd94d827540040de66d <fd72ac9556a473fc7daf54efb6ca8a97180d621d
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