Skip to main content
Vulnerability Database/CVE-2026-108952

CVE-2026-108952: RT-Thread USB CDC Driver DOS Vulnerability

CVE-2026-108952 is a denial of service vulnerability in RT-Thread USB CDC driver caused by memory corruption. Connected USB hosts can trigger writes past ring buffers leading to system crashes. This article covers technical details, affected versions through 5.3.0, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-108952 Overview

CVE-2026-108952 is a memory corruption vulnerability in the RT-Thread real-time operating system through version 5.3.0. The flaw resides in the legacy USB Communications Device Class (CDC) virtual COM port driver (cdc_vcom.c). The driver incorrectly aliases rx_ringbuffer as a Serial V2 rt_serial_rx_fifo structure inside _function_enable(). When a USB host configures the CDC device, the driver writes past the ring buffer into adjacent struct vcom members and performs an invalid rt_free() on close. The condition is tracked under [CWE-843] (Access of Resource Using Incompatible Type, also known as type confusion).

Critical Impact

A physically connected USB host can corrupt kernel memory and trigger a denial-of-service condition on the target embedded device running RT-Thread.

Affected Products

  • RT-Thread real-time operating system through version 5.3.0
  • Legacy USB device stack component components/legacy/usb/usbdevice/class/cdc_vcom.c
  • Builds using the CDC virtual COM port driver with Serial V2 enabled

Discovery Timeline

  • 2026-10-12 - CVE-2026-108952 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-108952

Vulnerability Analysis

The RT-Thread legacy USB CDC VCOM driver manages a receive ring buffer (rx_ringbuffer) that stores inbound serial data. When Serial V2 (RT_USING_SERIAL_V2) is enabled, the driver reinterprets this ring buffer as a rt_serial_rx_fifo structure within _function_enable(). The two structures have incompatible layouts and sizes. Treating one as the other causes writes to extend beyond the original buffer and overwrite adjacent fields in struct vcom.

When a USB host enumerates and configures the CDC interface, the driver triggers these writes during endpoint setup. Memory beyond the allocated ring buffer is corrupted, and on device close the driver passes an incorrectly derived pointer to rt_free(). The invalid free further destabilizes the heap and results in denial of service.

Root Cause

The root cause is a type confusion defect. The code aliases a struct rt_ringbuffer allocation as a struct rt_serial_rx_fifo without allocating or initializing the target type. Field offsets and allocation sizes do not match, so legitimate serial FIFO operations write outside the intended object boundaries.

Attack Vector

Exploitation requires physical access. An attacker connects a USB host (such as a laptop or a programmable USB device) to the RT-Thread target that exposes the CDC VCOM function. Standard USB configuration requests from the host trigger _function_enable() and the subsequent out-of-bounds writes. No authentication or user interaction on the target is required.

c
 static rt_err_t _ep_out_handler(ufunction_t func, rt_size_t size)
 {
     rt_base_t level;
+    rt_bool_t notify_rx = RT_FALSE;
     struct vcom *data;
 #ifdef RT_USING_SERIAL_V2
     struct rt_serial_rx_fifo *rx_fifo;

Source: RT-Thread patch commit ceef6e0 — the fix adds proper Serial V2 handling in _ep_out_handler() and corrects buffer management so the ring buffer is no longer aliased as an incompatible FIFO structure.

Detection Methods for CVE-2026-108952

Indicators of Compromise

  • Unexpected RT-Thread device resets, kernel panics, or hangs shortly after a USB host is attached
  • Heap corruption assertions or rt_free() failure messages in serial debug logs when the CDC VCOM interface is disconnected
  • Repeated USB enumeration cycles followed by loss of the virtual COM port

Detection Strategies

  • Inventory firmware builds for inclusion of components/legacy/usb/usbdevice/class/cdc_vcom.c compiled with RT_USING_SERIAL_V2
  • Audit source trees against upstream commit ceef6e0ccd646aef61b907aeb9f29269d1caba50 to confirm whether the fix is present
  • Enable RT-Thread memory heap integrity checks in debug builds to surface corruption early during QA

Monitoring Recommendations

  • Monitor USB host-side logs on engineering workstations for repeated CDC enumeration failures against RT-Thread targets
  • Collect serial console output from fielded devices and alert on rt_free or ringbuffer assertion strings
  • Track physical USB port access on production and lab devices through facility controls and endpoint telemetry

How to Mitigate CVE-2026-108952

Immediate Actions Required

  • Identify all firmware images using the RT-Thread legacy USB CDC VCOM driver through version 5.3.0
  • Rebuild affected firmware against RT-Thread mainline including commit ceef6e0ccd646aef61b907aeb9f29269d1caba50 from pull request #11770
  • Restrict physical USB access to deployed devices until patched firmware is distributed

Patch Information

The upstream fix is merged in the RT-Thread GitHub repository and tracked under issue #11739 and pull request #11770. Additional context is available in the VulnCheck advisory. Vendors shipping RT-Thread images should pull commit ceef6e0ccd646aef61b907aeb9f29269d1caba50 and reissue builds.

Workarounds

  • Disable the legacy USB CDC VCOM class in the RT-Thread configuration if the virtual COM port is not required
  • Build with RT_USING_SERIAL_V2 disabled where application requirements permit, which avoids the aliasing path
  • Enclose devices to prevent unauthorized USB connections and remove exposed USB ports on production hardware
bash
# Disable the CDC VCOM class in RT-Thread menuconfig
# RT-Thread Components -> Device Drivers -> USB -> Using USB device
#   [ ] Enable composite device
#   [ ] Enable to use device as CDC-ACM device
scons --menuconfig
scons -c && scons -j8

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.