Kernel warning via invalid UVC entity IDs
Published Oct 20, 2025 · Updated Oct 20, 2025
Improper UVC entity handling in Linux 5.7 and later allows physically proximate attackers to trigger kernel warnings via a crafted USB camera. The uvcvideo parser accepts zero or duplicate unit and terminal IDs, so entity lookup can resolve an output unit to itself or later use an entity with invalid pads while building the media graph. Physical attachment or equivalent control of a UVC device is required, and the documented consequence is a kernel warning during device probing rather than a confirmed crash.
Summary
What happened
Improper UVC entity handling in Linux 5.7 and later allows physically proximate attackers to trigger kernel warnings via a crafted USB camera. The uvcvideo parser accepts zero or duplicate unit and terminal IDs, so entity lookup can resolve an output unit to itself or later use an entity with invalid pads while building the media graph. Physical attachment or equivalent control of a UVC device is required, and the documented consequence is a kernel warning during device probing rather than a confirmed crash.
The record
- CVE
- CVE-2025-40016
- Published
- Oct 20, 2025
- Updated
- Oct 20, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1200
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 20, 2025CVE publishedPublication date reported by the CVE source.
- Oct 20, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.7
- Affected versionversion=a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b <000b2a6bed7f30e0aadfb19bce9af6458d879304
- Affected versionversion=a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b <0e2ee70291e64a30fe36960c85294726d34a103e
- Affected versionversion=a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b <0f140cede24334b3ee55e3e1127071266cbb8287
- Affected versionversion=a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b <15c0e136bd8cd70a1136a11c7876d6aae0eef8c8
- Affected versionversion=a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b <f617d515d66c05e9aebc787a8fe48b7163fc7b70
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