CVE-2026-10644 Details
Description
The Microchip SERCOM-G1 UART driver (drivers/serial/uart_mchp_sercom_g1.c), used by the PIC32CM-JH SoC family, contains an out-of-bounds write in its asynchronous (DMA) receive path. When uart_rx_enable() is invoked with a one-byte receive buffer (len == 1) and CONFIG_UART_MCHP_ASYNC is enabled, the RX-complete ISR starts a single-beat DMA transfer while a received byte is already pending in the SERCOM DATA register. On this SoC the peripheral-triggered DMA start sequencing then writes one byte past the end of the caller-supplied buffer (CWE-787). The overflowed byte's value is the UART RX data supplied by the connected serial peer (adjacent attacker), while its size and location are fixed at one byte immediately after the buffer. Exploitation requires the async UART config (not enabled by default on the in-tree PIC32CM-JH boards) and a consumer that enables RX with a one-byte buffer; impact is limited single-byte memory corruption adjacent to the RX buffer (possible crash / denial of service). The defect shipped in v4.4.0. The fix reads the first byte with the CPU and, for one-byte buffers, performs no DMA at all; for larger buffers it sizes the DMA for the remaining len-1 bytes.
A buffer overflow vulnerability has been identified in the Microchip SERCOM-G1 UART driver for the PIC32CM-JH SoC family, specifically in versions 4.4.0 prior to 4.5.0. The issue arises in the asynchronous DMA receive path when 'uart_rx_enable()' is called with a one-byte buffer. With the 'CONFIG_UART_MCHP_ASYNC' option enabled, the RX-complete interrupt service routine (ISR) initiates a DMA transfer while a byte is still pending in the SERCOM DATA register. This sequence causes the DMA to write one byte beyond the end of the provided buffer, leading to memory corruption. The overflowed byte contains UART RX data from the connected serial peer, creating a potential exploitation vector. The vulnerability requires the asynchronous UART configuration, which is not enabled by default on standard PIC32CM-JH boards, and a user that activates RX with a one-byte buffer.
Users can update to Zephyr version 4.5.0 or later, where this vulnerability has been fixed. Instructions for updating can be found in the Zephyr project documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 29, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| zephyrproject zephyr | >= 4.4.0, <= 4.4.1 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 25, 2026 | CVE Translated | [email protected] |
| Oct 15, 2026 | CVE Modified | [email protected] |
| Jul 14, 2026 | CVE Modified | [email protected] |
| Jul 6, 2026 | Initial Analysis | [email protected] |
| Jun 29, 2026 | CVE Modified | CISA-ADP |
| Jun 28, 2026 | New CVE Received | [email protected] |