Kernel crash via gadget serial disconnect race
Published Dec 27, 2024 · Updated May 11, 2026
Null pointer dereference in affected Linux kernel versions allows local users to crash the kernel through concurrent USB gadget operations. In drivers/usb/gadget/function/u_serial.c, gs_start_io calls gs_free_requests through port_usb after gserial_disconnect sets that pointer to NULL in a competing thread. Reachability requires local access to open the gadget serial TTY while the USB gadget disconnects, and the resulting impact is a kernel crash.
Summary
What happened
Null pointer dereference in affected Linux kernel versions allows local users to crash the kernel through concurrent USB gadget operations. In drivers/usb/gadget/function/u_serial.c, gs_start_io calls gs_free_requests through port_usb after gserial_disconnect sets that pointer to NULL in a competing thread. Reachability requires local access to open the gadget serial TTY while the USB gadget disconnects, and the resulting impact is a kernel crash.
The record
- CVE
- CVE-2024-56670
- 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=2.6.27
- Affected versionversion=c1dca562be8ada614ef193aa246c6f8705bcd6b9 <1247e1df086aa6c17ab53cd1bedce70dd7132765
- Affected versionversion=c1dca562be8ada614ef193aa246c6f8705bcd6b9 <28b3c03a6790de1f6f2683919ad657840f0f0f58
- Affected versionversion=c1dca562be8ada614ef193aa246c6f8705bcd6b9 <4cfbca86f6a8b801f3254e0e3c8f2b1d2d64be2b
- Affected versionversion=c1dca562be8ada614ef193aa246c6f8705bcd6b9 <4efdfdc32d8d6307f968cd99f1db64468471bab1
- Affected versionversion=c1dca562be8ada614ef193aa246c6f8705bcd6b9 <8ca07a3d18f39b1669927ef536e485787e856df6
- Affected versionversion=c1dca562be8ada614ef193aa246c6f8705bcd6b9 <c83213b6649d22656b3a4e92544ceeea8a2c6c07
- Affected versionversion=c1dca562be8ada614ef193aa246c6f8705bcd6b9 <dd6b0ca6025f64ccb465a6a3460c5b0307ed9c44
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