Cyber Resilience

CVE-2026-4179

DoS in Zephyrproject Zephyr ≤ 4.3.0

Public PoCDoS
Published
16 March 2026
Modified
02 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
EPSS Score 0.0018 8th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-4179 is a medium-severity Infinite Loop (CWE-835) vulnerability in Zephyrproject Zephyr. Its CVSS base score is 6.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Issues in stm32 USB device driver (drivers/usb/device/usb_dc_stm32.c) can lead to an infinite while loop.

CWE(s)
CWE-835

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
Why these techniques?

Infinite loop in USB driver enables local or physical exploitation leading to application/system DoS via resource exhaustion.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-10642Same product: Zephyrproject Zephyr
CVE-2025-2962Same product: Zephyrproject Zephyr
CVE-2026-10668Same product: Zephyrproject Zephyr
CVE-2026-10637Same product: Zephyrproject Zephyr
CVE-2026-10655Same product: Zephyrproject Zephyr
CVE-2026-13351Same product: Zephyrproject Zephyr
CVE-2025-1673Same product: Zephyrproject Zephyr
CVE-2026-10656Same product: Zephyrproject Zephyr
CVE-2026-5590Same product: Zephyrproject Zephyr
CVE-2026-10657Same product: Zephyrproject Zephyr

Affected Assets

zephyrproject
zephyr
≤ 4.3.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • SA-11 Developer Testing and Evaluation
Detect
Catch it (NIST detect / respond)
  • SI-4 System Monitoring
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-2 Flaw Remediation good match
prevent

Directly requires timely remediation of the identified infinite-loop flaw in usb_dc_stm32.c before or after deployment.

SA-11 Developer Testing and Evaluation good match
prevent

Mandates developer security testing and fuzzing that would detect the unreachable exit condition (CWE-835) in the STM32 USB driver.

SI-4 System Monitoring partial match
detect

Enables continuous monitoring of driver responsiveness and USB stack behavior to identify when the infinite while loop has been triggered.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (reviews, testing, static analysis) directly prevent introduction of infinite-loop defects.

ID.RA-01 partial match
prevents

Static analysis and vuln scanning during asset assessment can detect unreachable loop exits.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can uncover infinite-loop conditions before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify loop-termination rules, indirectly reducing the weakness.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address loop termination and prevent infinite loops.

A.8.27 Secure system architecture and engineering principles none match
none

Secure architecture principles encourage designs that avoid unreachable exit conditions.

A.8.32 Change management none match
none

Change management can require review of loop logic when code is modified.

References