CVE-2025-40016: media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Fixed version: Linux Linux 000b2a6bed7f30e0aadfb19bce9af6458d879304, 0e2ee70291e64a30fe36960c85294726d34a103e, 0f140cede24334b3ee55e3e1127071266cbb8287; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.
Low priority for now. Upgrade to Linux Linux 000b2a6bed7f30e0aadfb19bce9af6458d879304, 0e2ee70291e64a30fe36960c85294726d34a103e, 0f140cede24334b3ee55e3e1127071266cbb8287; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID Per UVC 1.1+ specification 3.7.2, units and terminals must have a non-zero unique ID. ``` Each Unit and Terminal within the video function is assigned a unique identification number, the Unit ID (UID) or Terminal ID (TID), contained in the bUnitID or bTerminalID field of the descriptor. The value 0x00 is reserved for undefined ID, ``` If we add a new entity with id 0 or a duplicated ID, it will be marked as UVC_INVALID_ENTITY_ID. In a previous attempt commit 3dd075fe8ebb ("media: uvcvideo: Require entities to have a non-zero unique ID"), we ignored all the invalid units, this broke a lot of non-compatible cameras. Hopefully we are more lucky this time. This also prevents some syzkaller reproducers from triggering warnings due to a chain of entities referring to themselves. In one particular case, an Output Unit is connected to an Input Unit, both with the same ID of 1. But when looking up for the source ID of the Output Unit, that same entity is found instead of the input entity, which leads to such warnings. In another case, a backward chain was considered finished as the source ID was 0. Later on, that entity was found, but its pads were not valid. Here is a sample stack trace for one of those cases. [ 20.650953] usb 1-1: new high-speed USB device number 2 using dummy_hcd [ 20.830206] usb 1-1: Using ep0 maxpacket: 8 [ 20.833501] usb 1-1: config 0 descriptor?? [ 21.038518] usb 1-1: string descriptor 0 read error: -71 [ 21.038893] usb 1-1: Found UVC 0.00 device <unnamed> (2833:0201) [ 21.039299] uvcvideo 1-1:0.0: Entity type for entity Output 1 was not initialized! [ 21.041583] uvcvideo 1-1:0.0: Entity type for entity Input 1 was not initialized! [ 21.042218] ------------[ cut here ]------------ [ 21.042536] WARNING: CPU: 0 PID: 9 at drivers/media/mc/mc-entity.c:1147 media_create_pad_link+0x2c4/0x2e0 [ 21.043195] Modules linked in: [ 21.043535] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.11.0-rc7-00030-g3480e43aeccf #444 [ 21.044101] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [ 21.044639] Workqueue: usb_hub_wq hub_event [ 21.045100] RIP: 0010:media_create_pad_link+0x2c4/0x2e0 [ 21.045508] Code: fe e8 20 01 00 00 b8 f4 ff ff ff 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 0f 0b eb e9 0f 0b eb 0a 0f 0b eb 06 <0f> 0b eb 02 0f 0b b8 ea ff ff ff eb d4 66 2e 0f 1f 84 00 00 00 00 [ 21.046801] RSP: 0018:ffffc9000004b318 EFLAGS: 00010246 [ 21.047227] RAX: ffff888004e5d458 RBX: 0000000000000000 RCX: ffffffff818fccf1 [ 21.047719] RDX: 000000000000007b RSI: 0000000000000000 RDI: ffff888004313290 [ 21.048241] RBP: ffff888004313290 R08: 0001ffffffffffff R09: 0000000000000000 [ 21.048701] R10: 0000000000000013 R11: 0001888004313290 R12: 0000000000000003 [ 21.049138] R13: ffff888004313080 R14: ffff888004313080 R15: 0000000000000000 [ 21.049648] FS: 0000000000000000(0000) GS:ffff88803ec00000(0000) knlGS:0000000000000000 [ 21.050271] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 21.050688] CR2: 0000592cc27635b0 CR3: 000000000431c000 CR4: 0000000000750ef0 [ 21.051136] PKRU: 55555554 [ 21.051331] Call Trace: [ 21.051480] <TASK> [ 21.051611] ? __warn+0xc4/0x210 [ 21.051861] ? media_create_pad_link+0x2c4/0x2e0 [ 21.052252] ? report_bug+0x11b/0x1a0 [ 21.052540] ? trace_hardirqs_on+0x31/0x40 [ 21.052901] ? handle_bug+0x3d/0x70 [ 21.053197] ? exc_invalid_op+0x1a/0x50 [ 21.053511] ? asm_exc_invalid_op+0x1a/0x20 [ 21.053924] ? media_create_pad_link+0x91/0x2e0 [ 21.054364] ? media_create_pad_link+0x2c4/0x2e0 [ 21.054834] ? media_create_pad_link+0x91/0x2e0 [ 21.055131] ? _raw_spin_unlock+0x1e/0x40 [ 21.055441] ? __v4l2_device_register_subdev+0x202/0x210 [ 21.055837] uvc_mc_register_entities+0x358/0x400 [ 21.056144] uvc_register_chains+0x1 ---truncated---
- Published
- Oct 20, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.7affected
- a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b and later · before 983a1d327e2642832a43f969761e27339b0d2a8faffected · git
- a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b and later · before 59f64514bc347d0e93b70c6b612ad824b63ae7caaffected · git
- a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b and later · before f617d515d66c05e9aebc787a8fe48b7163fc7b70affected · git
- a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b and later · before 000b2a6bed7f30e0aadfb19bce9af6458d879304affected · git
- a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b and later · before 15c0e136bd8cd70a1136a11c7876d6aae0eef8c8affected · git
- a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b and later · before 0f140cede24334b3ee55e3e1127071266cbb8287affected · git
- a3fbc2e6bb05a3b1ea341cd29dea09b4a033727b and later · before 0e2ee70291e64a30fe36960c85294726d34a103eaffected · git
- before 5.7not affected · semver
- 5.15.203 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.16.11-1 | 6.16.11-1 |
| openSUSE:Tumbleweed | kernel-source | before 6.17.5-1.1 | 6.17.5-1.1 |
| openSUSE:Tumbleweed | kernel-source-longterm | before 6.18.16-1.1 | 6.18.16-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40013Oct 20, 2025 · ASoC: qcom: audioreach: fix potential null pointer dereference0Monitor
- ← EarlierCVE-2025-40015Oct 20, 2025 · media: stm32-csi: Fix dereference before NULL check0Monitor
- Later →CVE-2025-40017Oct 20, 2025 · media: iris: Fix memory leak by freeing untracked persist buffer0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 000b2a6bed7f30e0aadfb19bce9af6458d879304 | Vendor (CNA) |
| Linux Linux | 0e2ee70291e64a30fe36960c85294726d34a103e | Vendor (CNA) |
| Linux Linux | 0f140cede24334b3ee55e3e1127071266cbb8287 | Vendor (CNA) |
| Linux Linux | 15c0e136bd8cd70a1136a11c7876d6aae0eef8c8 | Vendor (CNA) |
| Linux Linux | 59f64514bc347d0e93b70c6b612ad824b63ae7ca | Vendor (CNA) |
| Linux Linux | 983a1d327e2642832a43f969761e27339b0d2a8f | Vendor (CNA) |
| Linux Linux | f617d515d66c05e9aebc787a8fe48b7163fc7b70 | Vendor (CNA) |
| azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 | 6.6.112.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 6.17.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-source-longterm | 6.18.16-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/0e2ee70291e64a30fe36960c85294726d34a103e
- git.kernel.org/stable/c/0f140cede24334b3ee55e3e1127071266cbb8287
- git.kernel.org/stable/c/15c0e136bd8cd70a1136a11c7876d6aae0eef8c8
- git.kernel.org/stable/c/59f64514bc347d0e93b70c6b612ad824b63ae7ca
- git.kernel.org/stable/c/983a1d327e2642832a43f969761e27339b0d2a8f
- git.kernel.org/stable/c/f617d515d66c05e9aebc787a8fe48b7163fc7b70
Vendor advisories and official records. Exploit/PoC links are deliberately left out.