System crash via null USB product name
Published Dec 27, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel Wacom HID driver allows local users to crash the system by attaching a malformed USB device. In wacom_update_name, the driver replaced its fallback product_name with the nullable USB dev->product descriptor and later passed that null pointer to string handling. Triggering the fault requires attaching a device that exposes an empty product descriptor while the Wacom driver probes it; the reported consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in the Linux kernel Wacom HID driver allows local users to crash the system by attaching a malformed USB device. In wacom_update_name, the driver replaced its fallback product_name with the nullable USB dev->product descriptor and later passed that null pointer to string handling. Triggering the fault requires attaching a device that exposes an empty product descriptor while the Wacom driver probes it; the reported consequence is a kernel crash.
The record
- CVE
- CVE-2024-56629
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476
- 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=09dc28acaec74d7467c7c9b81dc8676e5bc957ce <2cd323c55bd3f356bf23ae1b4c20100abcdc29d6
- Affected versionversion=09dc28acaec74d7467c7c9b81dc8676e5bc957ce <2ed3e3a3ac06af8a6391c3d6a7791b7967d7d43a
- Affected versionversion=09dc28acaec74d7467c7c9b81dc8676e5bc957ce <5912a921289edb34d40aeab32ea6d52d41e75fed
- Affected versionversion=09dc28acaec74d7467c7c9b81dc8676e5bc957ce <59548215b76be98cf3422eea9a67d6ea578aca3d
- Affected versionversion=09dc28acaec74d7467c7c9b81dc8676e5bc957ce <a7f0509556fa2f9789639dbcee9eed46e471ccef
- Affected versionversion=09dc28acaec74d7467c7c9b81dc8676e5bc957ce <d031eef3cc2e3bf524509e38fb898e5335c85c96
- Affected versionversion=09dc28acaec74d7467c7c9b81dc8676e5bc957ce <e689bc6697a7fcebd4a945ab0b1e1112c76024d8
- Affected versionversion=4.14
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