CVE-2026-10644 Out-of-bounds write in Microchip SERCOM-G1 (PIC32CM-JH) async UART RX with 1-byte buffer
An out-of-bounds write in the Zephyr SERCOM-G1 UART driver allows adjacent attackers to cause a denial of service via memory corruption when async RX is enabled with a one-byte buffer.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-10644?
CVE-2026-10644 is a medium-severity memory corruption vulnerability in Zephyrproject Zephyr, published on 28 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Weakness: CWE-787
Which versions are affected by CVE-2026-10644?
It affects 1 product.
Products include Zephyrproject Zephyr.
How do I fix CVE-2026-10644?
No fix has been published for CVE-2026-10644 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-10644 being exploited?
There is no known exploitation of CVE-2026-10644 in the wild and no public exploit code.
Other vulnerabilities in Zephyrproject Zephyr
- CVE-2026-5067 Out-of-bounds read/write in HTTP WebSocket upgrade via non-null-terminated Sec-WebSocket-Key
- CVE-2022-3806 Bluetooth HCI Error Handling Double Free
- CVE-2017-14199 Memory corruption in getaddrinfo
- CVE-2018-1000800 Null dereference in n/a
- CVE-2021-3329 DOS: Incorrect handling of the initial HCI ACL_MTU handshake packet leads to crash of bluetooth host layer
Sources
Also known as GHSA-xv2x-56j7-6wc3.