CVE-2026-10642 Vulnerability Analysis & Exploit Details

CVE-2026-10642
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2026-10642 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Adjacent_network
    Attack Vector Under Analysis
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-10642 Details

Status: Analyzed

Last updated: 🕑 02 Jul 2026, 14:23 UTC
Originally published on: 🕙 24 Jun 2026, 22:16 UTC

Time between publication and last update: 7 days

CVSS Release: version 3

CVSS3 Source

vulnerabilities@zephyrproject.org

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE-2026-10642 Vulnerability Summary

CVE-2026-10642: The Zephyr PL011 UART driver (drivers/serial/uart_pl011.c) contains an unbounded software loop in pl011_irq_tx_enable() that repeatedly invokes the interrupt-driven application callback while the TX interrupt mask bit (PL011_IMSC_TXIM) is set, to work around the controller's level-transition TX-interrupt behavior. When CTS hardware flow control is enabled (devicetree hw-flow-control or runtime UART_CFG_FLOW_CTRL_RTS_CTS) and the wired serial peer de-asserts CTS, the controller stops draining the TX FIFO; pl011_fifo_fill() then returns 0 on every call while the application still has pending data and therefore never disables the TX interrupt. The loop condition never clears, so the thread that called uart_irq_tx_enable() (e.g. h4_send() in the Bluetooth HCI H4 driver) spins indefinitely, hanging the executing context and stalling the transport — a denial of service (CWE-835). An attacker controlling the device attached to the UART's CTS line can trigger the hang by withholding CTS during transmission. Impact is availability only; there is no memory-safety, confidentiality, or integrity consequence. The vulnerable loop was introduced in commit b783bc8448ef (Feb 2025) and shipped in releases v4.1.0 through v4.4.0. The fix breaks out of the loop when CTS is blocking and arms the CTS modem-status interrupt to resume transmission when CTS re-asserts.

Assessing the Risk of CVE-2026-10642

Access Complexity Graph

The exploitability of CVE-2026-10642 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-10642

With low attack complexity and no required privileges, CVE-2026-10642 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-10642, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-10642, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-10642 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-10642 poses no threat to data integrity.
  • Availability: High
    CVE-2026-10642 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-10642 References

External References

CWE Common Weakness Enumeration

CWE-835

Vulnerable Configurations

  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.1:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.1:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.1:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.1:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.1:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.1:rc1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-10642: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-12252 – In nltk/nltk versions 3.9.3 and earlier, five Stanford interface classes (StanfordPOSTagger, StanfordNERTagger, StanfordParser, StanfordDependencyP...
  • CVE-2025-71380 – The Execute Command node in n8n allows authenticated users to execute arbitrary commands on the host system where n8n runs. Attackers with user acc...
  • CVE-2025-71375 – picklescan before 0.0.34 fails to detect the _operator.methodcaller built-in function when scanning pickle files for malicious code. Attackers can ...
  • CVE-2025-71373 – picklescan before 0.0.33 fails to detect operator.methodcaller function calls in pickle files, allowing attackers to bypass security checks. Remote...
  • CVE-2025-71372 – Picklescan before 0.0.33 fails to detect the numpy.f2py.crackfortran.getlincoef gadget in pickle __reduce__ methods, allowing arbitrary code execut...