System crash via incomplete USB endpoint validation
Published May 1, 2024 · Updated May 11, 2026
Improper USB endpoint validation in Linux allows local users to crash the system through a crafted USB device during driver probing. The vmk80xx_find_usb_endpoints() function fails to verify that each discovered endpoint has the transfer type expected for the hardware model, so vmk80xx_reset_device() submits an URB through a mismatched pipe. Triggering requires an unexpected device endpoint layout, and the resulting warning becomes a system crash when panic_on_warn is enabled.
Summary
What happened
Improper USB endpoint validation in Linux allows local users to crash the system through a crafted USB device during driver probing. The vmk80xx_find_usb_endpoints() function fails to verify that each discovered endpoint has the transfer type expected for the hardware model, so vmk80xx_reset_device() submits an URB through a mismatched pipe. Triggering requires an unexpected device endpoint layout, and the resulting warning becomes a system crash when panic_on_warn is enabled.
The record
- CVE
- CVE-2024-27001
- Published
- May 1, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 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=3.9
- Affected versionversion=49253d542cc0f5f771dc254d248162a2a666649d <3a63ae0348d990e137cca04eced5b08379969ea9
- Affected versionversion=49253d542cc0f5f771dc254d248162a2a666649d <59f33af9796160f851641d960bd93937f282c696
- Affected versionversion=49253d542cc0f5f771dc254d248162a2a666649d <6ec3514a7d35ad9cfab600187612c29f669069d2
- Affected versionversion=49253d542cc0f5f771dc254d248162a2a666649d <a3b8ae7e9297dd453f2977b011c5bc75eb20e71b
- Affected versionversion=49253d542cc0f5f771dc254d248162a2a666649d <ac882d6b21bffecb57bcc4486701239eef5aa67b
- Affected versionversion=49253d542cc0f5f771dc254d248162a2a666649d <b0b268eeb087e324ef3ea71f8e6cabd07630517f
- Affected versionversion=49253d542cc0f5f771dc254d248162a2a666649d <d1718530e3f640b7d5f0050e725216eab57a85d8
- Affected versionversion=49253d542cc0f5f771dc254d248162a2a666649d <f15370e315976198f338b41611f37ce82af6cf54
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