CVE-2026-10644: bounds in zephyrproject zephyr
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.
AI Analysis
Technical Summary
The Microchip SERCOM-G1 UART driver in Zephyr 4.4.0 has an out-of-bounds write vulnerability in its asynchronous DMA receive path for the PIC32CM-JH SoC family. When uart_rx_enable() is called with a one-byte buffer and CONFIG_UART_MCHP_ASYNC is enabled, the RX-complete ISR initiates a DMA transfer that writes one byte beyond the end of the buffer. This overflow byte contains UART RX data from the connected serial peer. Exploitation requires enabling async UART and using a one-byte RX buffer, conditions not enabled by default. The impact is limited to a single-byte memory corruption adjacent to the RX buffer, potentially causing crashes or denial of service. The defect was introduced in version 4.4.0. The fix reads the first byte directly via CPU and disables DMA for one-byte buffers, adjusting DMA size for larger buffers.
Potential Impact
The vulnerability causes a single-byte out-of-bounds write adjacent to the RX buffer in the UART driver, which can lead to memory corruption. This may result in application crashes or denial of service. There is no confidentiality or integrity impact reported. Exploitation requires specific UART asynchronous configuration and a one-byte receive buffer, limiting the attack surface.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vendor has described a fix that reads the first byte with the CPU and disables DMA for one-byte buffers, adjusting DMA size for larger buffers. Until an official patch is available, avoid enabling asynchronous UART with one-byte receive buffers on affected hardware. The vulnerability is not exploitable by default configurations on in-tree PIC32CM-JH boards.
CVE-2026-10644: bounds in zephyrproject zephyr
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.
CVSS v3.1
Score 4.2medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Microchip SERCOM-G1 UART driver in Zephyr 4.4.0 has an out-of-bounds write vulnerability in its asynchronous DMA receive path for the PIC32CM-JH SoC family. When uart_rx_enable() is called with a one-byte buffer and CONFIG_UART_MCHP_ASYNC is enabled, the RX-complete ISR initiates a DMA transfer that writes one byte beyond the end of the buffer. This overflow byte contains UART RX data from the connected serial peer. Exploitation requires enabling async UART and using a one-byte RX buffer, conditions not enabled by default. The impact is limited to a single-byte memory corruption adjacent to the RX buffer, potentially causing crashes or denial of service. The defect was introduced in version 4.4.0. The fix reads the first byte directly via CPU and disables DMA for one-byte buffers, adjusting DMA size for larger buffers.
Potential Impact
The vulnerability causes a single-byte out-of-bounds write adjacent to the RX buffer in the UART driver, which can lead to memory corruption. This may result in application crashes or denial of service. There is no confidentiality or integrity impact reported. Exploitation requires specific UART asynchronous configuration and a one-byte receive buffer, limiting the attack surface.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vendor has described a fix that reads the first byte with the CPU and disables DMA for one-byte buffers, adjusting DMA size for larger buffers. Until an official patch is available, avoid enabling asynchronous UART with one-byte receive buffers on affected hardware. The vulnerability is not exploitable by default configurations on in-tree PIC32CM-JH boards.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- zephyr
- Date Reserved
- 2026-06-02T15:11:46.303Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a40ac0127e9c79719547625
Added to database: 06/28/2026, 05:07:13 UTC
Last enriched: 07/15/2026, 10:46:24 UTC
Last updated: 08/12/2026, 00:41:10 UTC
Views: 101
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.