System crash via disabled USB endpoint queue
Published Feb 12, 2024 · Updated Nov 3, 2025
Improper endpoint-state validation in the Linux kernel through 6.7.4 allows local users to crash the system through a gadget-printer write. The printer_write function queues a USB request through usb_ep_queue without first rejecting writes made while the IN endpoint is disabled. A low-privileged process must access the configured USB Gadget printer device and issue a write before endpoint enablement, triggering a kernel warning and service interruption.
Summary
What happened
Improper endpoint-state validation in the Linux kernel through 6.7.4 allows local users to crash the system through a gadget-printer write. The printer_write function queues a USB request through usb_ep_queue without first rejecting writes made while the IN endpoint is disabled. A low-privileged process must access the configured USB Gadget printer device and issue a write before endpoint enablement, triggering a kernel warning and service interruption.
The record
- CVE
- CVE-2024-25741
- Published
- Feb 12, 2024
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-703, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Syzkaller USB Gadget printer crash reproducerproof of concept · demonstrated
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