Kernel warning via zero-length usbtmc ioctl
Published Dec 8, 2025 · Updated May 11, 2026
Improper direction validation in affected Linux kernels beginning with 4.20 allows local users to trigger a warning through a zero-length usbtmc ioctl. In drivers/usb/class/usbtmc.c, usbtmc_ioctl_request passes the supplied bRequestType direction into a zero-length control transfer instead of forcing OUT. Reachability requires local access to the usbtmc ioctl for a USB Test and Measurement device; the published trace reports a warning, not a crash or data compromise.
Summary
What happened
Improper direction validation in affected Linux kernels beginning with 4.20 allows local users to trigger a warning through a zero-length usbtmc ioctl. In drivers/usb/class/usbtmc.c, usbtmc_ioctl_request passes the supplied bRequestType direction into a zero-length control transfer instead of forcing OUT. Reachability requires local access to the usbtmc ioctl for a USB Test and Measurement device; the published trace reports a warning, not a crash or data compromise.
The record
- CVE
- CVE-2023-53761
- Published
- Dec 8, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 8, 2025CVE 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=4.20
- Affected versionversion=658f24f4523e41cda6a389c38b763f4c0cad6fbc <0ced12bdf624d8d8977ddb16eb130cd479d92bcf
- Affected versionversion=658f24f4523e41cda6a389c38b763f4c0cad6fbc <3b43d9df27a708f4079d518b879f517fea150a91
- Affected versionversion=658f24f4523e41cda6a389c38b763f4c0cad6fbc <50775a046c68e1d157d5e413cae2e5e00da1c463
- Affected versionversion=658f24f4523e41cda6a389c38b763f4c0cad6fbc <6340e432cf70bf156b19c6f5dd737d940eca02a3
- Affected versionversion=658f24f4523e41cda6a389c38b763f4c0cad6fbc <7cef7681aa7719ff585dd06113a061ab2def7da0
- Affected versionversion=658f24f4523e41cda6a389c38b763f4c0cad6fbc <94d25e9128988c6a1fc9070f6e98215a95795bd8
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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