CVE-2026-10644
Last modified
CVE-2026-10644 is a low-severity vulnerability rated 3.1/10 on the CVSS scale. 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. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Zephyrproject | Zephyr | >= 4.4.0, <= 4.4.1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-10644?
How severe is CVE-2026-10644?
How do I fix CVE-2026-10644?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-106434The explicit decryption component of MongoDB libmongocrypt c…4.3
- CVE-2026-106435The MongoDB Python Driver's binary accelerator can read outs…4.7
- CVE-2026-106436The BSON encoder in the MongoDB PHP Driver does not check so…6.5
- CVE-2026-106437The BSON buffer-reservation API in the MongoDB C Driver can …7.4
- CVE-2026-106438An incorrect calculation in Decimal128 string parsing in the…3.7
- CVE-2026-106439Hydra is a framework for elegantly configuring complex appli…8.5
- CVE-2026-106440Hydra is a framework for elegantly configuring complex appli…7.8
- CVE-2026-106441Hydra is a framework for elegantly configuring complex appli…7.8
- CVE-2026-106442Hydra is a framework for elegantly configuring complex appli…7.8
- CVE-2026-106443WeasyPrint helps web developers to create PDF documents. Pri…8.8
- CVE-2026-106444Handlebars provides the power necessary to let users build s…4.7
- CVE-2026-106445Handlebars provides the power necessary to let users build s…9.2
Are you affected by CVE-2026-10644?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
