Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-12629: dos in zephyrproject zephyr

0
Medium
VulnerabilityCVE-2026-12629cvecve-2026-12629
Published: 08/17/2026 (08/17/2026, 16:18:50 UTC)
Source: CVE Database V5
Vendor/Project: zephyrproject
Product: zephyr

Description

The ARM PL011 UART driver in drivers/serial/uart_pl011.c fails to acknowledge receive error interrupts. On the PL011, the framing, parity, break, and overrun error interrupts (PL011_IMSC_ERROR_MASK) are cleared only by writing the interrupt-clear register UARTICR; reading the data register clears the RX interrupt and the per-byte RSR status but not the error interrupt status in MIS. The interrupt service routine pl011_isr() acknowledged only the CTS modem-status interrupt and never wrote icr for the error bits, so an asserted error interrupt remains pending after the ISR returns. When an application enables error-interrupt reporting via the public uart_irq_err_enable() API, an attacker who controls the serial peer can deterministically assert these error bits by injecting line errors on the RX line — a baud/stop-bit mismatch or mid-character break (framing/break error), a flipped parity bit (parity error), or FIFO flooding (overrun error). Because the error interrupt is never cleared, the interrupt line stays asserted and the CPU re-enters pl011_isr() immediately and indefinitely, producing an interrupt-storm livelock from which the core makes no forward progress. The impact is an availability-only denial of service (permanent hang), reachable from an external or removable UART peer. Exploitation is gated by configuration: the error interrupt is off by default and no in-tree subsystem enables it, so only applications that explicitly call uart_irq_err_enable() on a PL011-based, interrupt-driven port are affected. The fix makes pl011_isr() acknowledge the pending error bits via uart->icr, breaking the loop, and additionally clears the latched RSR status in pl011_err_check().

CVSS v3.1

Score 4.6medium

Attack Vector
Physical
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected software

GitHub Actionsmore threats →cve
zephyr
pkg:github/zephyr
Affected versions
>=1.14.0 <4.4.2

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

AILast updated: 08/17/2026, 16:58:22 UTC

Technical Analysis

The ARM PL011 UART driver in Zephyr (drivers/serial/uart_pl011.c) does not properly clear receive error interrupts such as framing, parity, break, and overrun errors. The interrupt service routine (pl011_isr) acknowledges only the CTS modem-status interrupt and neglects to clear error interrupts by writing to the UART interrupt-clear register (UARTICR). When error interrupts are enabled via uart_irq_err_enable(), a malicious UART peer can inject line errors to assert these error bits, causing the interrupt line to remain asserted indefinitely. This results in the CPU repeatedly entering the ISR, creating an interrupt storm livelock and causing a denial of service by permanently hanging the core. The vulnerability is gated by configuration since error interrupts are off by default and no in-tree subsystem enables them. The fix involves modifying pl011_isr() to acknowledge error bits by writing to uart->icr and clearing latched error status in pl011_err_check().

Potential Impact

This vulnerability causes an availability impact only, specifically a denial of service through a permanent hang of the affected CPU core. It requires an attacker to control the UART peer to inject line errors and the system to have error interrupt reporting explicitly enabled on a PL011-based UART port. There is no confidentiality or integrity impact. Exploitation is local to the UART interface and not remotely exploitable over a network.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is applied, avoid enabling error interrupt reporting via uart_irq_err_enable() on PL011-based UART ports. Monitor vendor communications for an official fix that acknowledges and clears error interrupts properly in the ISR.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
zephyr
Date Reserved
2026-06-18T15:22:24.098Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a8339cebf8831d53935e2fa

Added to database: 08/17/2026, 16:41:50 UTC

Last enriched: 08/17/2026, 16:58:22 UTC

Last updated: 08/17/2026, 18:41:50 UTC

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses