CVE-2026-10644

LOWNVD 3.13.1
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 4 sources updated this week
3.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
3.1
EG Score
3.1(medium)
EPSS
4.5%
KEV
Not listed

Published

June 28, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jun 29, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Out-of-bounds write in Microchip SERCOM-G1 (PIC32CM-JH) async UART RX with 1-byte buffer · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-xv2x-56j7-6wc3
github_commit

commit 5251d2bc0070 (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 5251d2bc0070 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/5251d2bc0070be801769fb7ce7b9066fef5d9f81

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 19:21 UTCNVD updateCVSS v3 → 3.1 · severity → LOW
  4. 2026-07-14 19:00 UTCMITRE cvelistV5CVSS v3 → 4.2 · severity → MEDIUM
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 13:17 UTCEG score recompute
  7. 2026-07-13 06:12 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-10 11:24 UTCEG score recompute
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 15:15 UTCEPSS rescore
  13. 2026-07-08 15:15 UTCEPSS rescore
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-07 09:32 UTCEG score recompute 1.10
  16. 2026-07-06 21:35 UTCNVD updateCVSS v3 → 3.1 · severity → LOW
  17. 2026-07-06 09:03 UTCEG score recompute
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 08:32 UTCEG score recompute
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 08:03 UTCEG score recompute
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-03 07:33 UTCEG score recompute
  25. 2026-07-02 07:03 UTCEG score recompute
Show 10 more
  1. 2026-07-01 15:06 UTCEPSS rescore
  2. 2026-07-01 15:06 UTCEPSS rescore
  3. 2026-07-01 06:34 UTCEG score recompute
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-30 06:04 UTCEG score recompute
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-29 05:33 UTCEG score recompute
  8. 2026-06-28 14:07 UTCEPSS rescore
  9. 2026-06-28 05:03 UTCEG score recompute
  10. 2026-06-28 05:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-10644?
CVE-2026-10644 is a low vulnerability published on June 28, 2026. 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…
When was CVE-2026-10644 disclosed?
CVE-2026-10644 was first published in the National Vulnerability Database on June 28, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10644 actively exploited?
CVE-2026-10644 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10644?
CVE-2026-10644 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-10644?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10644, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10644

Explore →

Is Your Infrastructure Affected by CVE-2026-10644?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.