Kernel crash via missing USB endpoint check
Published Jul 28, 2025 · Updated May 11, 2026
Improper endpoint handling in the Linux kernel sierra USB network driver allows local users to crash the system via a crafted USB device. The sierra_net_bind function accepts a three-endpoint interface after checking only bulk input and output, then continues when dev->status is null because no interrupt input endpoint was found. Exploitation requires low-privileged local access and control of USB descriptors that bind to the sierra driver; the established consequence is a kernel crash.
Summary
What happened
Improper endpoint handling in the Linux kernel sierra USB network driver allows local users to crash the system via a crafted USB device. The sierra_net_bind function accepts a three-endpoint interface after checking only bulk input and output, then continues when dev->status is null because no interrupt input endpoint was found. Exploitation requires low-privileged local access and control of USB descriptors that bind to the sierra driver; the established consequence is a kernel crash.
The record
- CVE
- CVE-2025-38474
- Published
- Jul 28, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-166, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 28, 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=2.6.34
- Affected versionversion=eb4fd8cd355c8ec425a12ec6cbdac614e8a4819d <0a263ccb905b4ae2af381cd4280bd8d2477b98b8
- Affected versionversion=eb4fd8cd355c8ec425a12ec6cbdac614e8a4819d <4c4ca3c46167518f8534ed70f6e3b4bf86c4d158
- Affected versionversion=eb4fd8cd355c8ec425a12ec6cbdac614e8a4819d <5408cc668e596c81cdd29e137225432aa40d1785
- Affected versionversion=eb4fd8cd355c8ec425a12ec6cbdac614e8a4819d <5849980faea1c792d1d5e54fdbf1e69ac0a9bfb9
- Affected versionversion=eb4fd8cd355c8ec425a12ec6cbdac614e8a4819d <5dd6a441748dad2f02e27b256984ca0b2d4546b6
- Affected versionversion=eb4fd8cd355c8ec425a12ec6cbdac614e8a4819d <65c666aff44eb7f9079c55331abd9687fb77ba2d
- Affected versionversion=eb4fd8cd355c8ec425a12ec6cbdac614e8a4819d <a6a238c4126eb3ddb495d3f960193ca5bb778d92
- Affected versionversion=eb4fd8cd355c8ec425a12ec6cbdac614e8a4819d <bfe8ef373986e8f185d3d6613eb1801a8749837a
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