CVE-2026-10644: Out-of-bounds write in Microchip SERCOM-G1 (PIC32CM-JH) async UART RX with 1-byte buffer

Published Jun 28, 2026
·
Updated

The Microchip SERCOM-G1 UART driver (drivers/serial/uartmchpsercomg1.c), used by the PIC32CM-JH SoC family, contains an out-of-bounds write in its asynchronous (DMA) receive path. When uartrxenable() is invoked with a one-byte receive buffer (len == 1) and CONFIGUARTMCHPASYNC 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.

Affected Software

2 affected components
Microchip SERCOM-G1 (PIC32CM-JH) async UART driver (uart_mchp_sercom_g1.c)=4.4.0
zephyrproject zephyr>=4.4.0<=4.4.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Microchip SERCOM-G1 UART driver (drivers/serial/uart_mchp_sercom_g1.c) / PIC32CM-JH SoC family to a version that resolves this vulnerability.

    Fixed in v4.4.0

Event History

Jun 28, 2026
CVE Published
via MITRE·04:02 AM
Data Sourced
via MITRE·04:02 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-10644?

The severity of CVE-2026-10644 is rated as medium with a score of 4.2.

2

How do I fix CVE-2026-10644?

To fix CVE-2026-10644, ensure that the receive buffer length is greater than one byte when using the uart_rx_enable() function.

3

What software is affected by CVE-2026-10644?

CVE-2026-10644 affects the Microchip SERCOM-G1 UART driver used by the PIC32CM-JH SoC family.

4

What type of vulnerability is CVE-2026-10644?

CVE-2026-10644 is an out-of-bounds write vulnerability in the asynchronous UART RX with a 1-byte buffer.

5

What are the implications of CVE-2026-10644?

The implications of CVE-2026-10644 include potential data corruption and system instability due to improper handling of UART data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203