Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-68622: CWE-121: Stack-based Buffer Overflow in espressif esp-usb

0
Medium
VulnerabilityCVE-2025-68622cvecve-2025-68622cwe-121
Published: Mon Jan 12 2026 (01/12/2026, 17:08:22 UTC)
Source: CVE Database V5
Vendor/Project: espressif
Product: esp-usb

Description

Espressif ESP-IDF USB Host UVC Class Driver allows video streaming from USB cameras. Prior to 2.4.0, a vulnerability in the esp-usb UVC host implementation allows a malicious USB Video Class (UVC) device to trigger a stack buffer overflow during configuration-descriptor parsing. When UVC configuration-descriptor printing is enabled, the host prints detailed descriptor information provided by the connected USB device. A specially crafted UVC descriptor may advertise an excessively large length. Because this value is not validated before being copied into a fixed-size stack buffer, an attacker can overflow the buffer and corrupt memory. This vulnerability is fixed in 2.4.0.

AI-Powered Analysis

AILast updated: 01/12/2026, 17:38:07 UTC

Technical Analysis

The vulnerability identified as CVE-2025-68622 affects the Espressif ESP-IDF USB Host UVC Class Driver used for video streaming from USB cameras. In versions prior to 2.4.0, the driver parses configuration descriptors from connected USB Video Class (UVC) devices to print detailed descriptor information. The vulnerability occurs because the length field in the UVC configuration descriptor is not validated before being copied into a fixed-size stack buffer. A malicious UVC device can advertise an excessively large length value, causing a stack-based buffer overflow during the descriptor parsing process. This overflow can overwrite adjacent memory on the stack, potentially leading to memory corruption, arbitrary code execution, or denial of service through system crashes. The vulnerability does not require any privileges or user interaction but does require physical access to connect a malicious USB device. The CVSS v3.1 score is 6.8, reflecting medium severity with high impact on confidentiality, integrity, and availability, but limited attack vector (physical). The issue is resolved in ESP-IDF version 2.4.0, where proper validation of descriptor length is implemented. No known exploits are currently reported in the wild. This vulnerability is categorized under CWE-121 (Stack-based Buffer Overflow), a common and dangerous class of memory corruption bugs. Espressif’s ESP-IDF is widely used in embedded IoT devices, which may be deployed in industrial, consumer, or commercial environments.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to embedded systems and IoT devices using Espressif ESP-IDF with USB host UVC functionality. Exploitation can lead to arbitrary code execution, allowing attackers to take control of affected devices, disrupt operations, or exfiltrate sensitive data. This is particularly concerning for critical infrastructure, industrial control systems, and smart devices prevalent in sectors such as manufacturing, healthcare, and transportation. The requirement for physical access limits remote exploitation but increases the threat from insider attacks or supply chain compromises. Memory corruption can also cause device instability or denial of service, impacting availability. Given the growing adoption of Espressif chips in European IoT deployments, the vulnerability could affect a broad range of devices, potentially cascading into larger operational disruptions if exploited at scale.

Mitigation Recommendations

1. Upgrade all Espressif ESP-IDF USB Host UVC Class Driver implementations to version 2.4.0 or later, where the vulnerability is fixed. 2. If upgrading is not immediately feasible, disable UVC configuration-descriptor printing to prevent the vulnerable code path from executing. 3. Implement strict physical security controls to restrict USB port access to trusted personnel and devices, minimizing the risk of malicious USB device insertion. 4. Employ USB device whitelisting or port control solutions to allow only authorized USB devices to connect. 5. Conduct regular firmware audits and vulnerability scanning on embedded devices to detect outdated ESP-IDF versions. 6. Monitor device logs for unusual USB connection events or crashes that may indicate exploitation attempts. 7. For critical deployments, consider network segmentation and device isolation to limit the impact of compromised devices. 8. Engage with device manufacturers and suppliers to ensure timely patching and secure device lifecycle management.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-19T18:50:09.991Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69652e21da2266e838e2547e

Added to database: 1/12/2026, 5:23:45 PM

Last enriched: 1/12/2026, 5:38:07 PM

Last updated: 1/12/2026, 8:03:08 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats