Adjacent denial of service via RX packet leak
Published Aug 31, 2026 · Updated Sep 1, 2026
Memory leak in Zephyr RTOS 4.4.0 through 4.4.1 allows attackers to interrupt network reception via broadcast or multicast Ethernet frames. eth_bridge_input_process() returns NET_OK after local bridge delivery without consuming the packet, causing processing_data() to retain each RX net_pkt. Exploitation requires access to the bridged L2 segment and an affected bridge configuration; pool exhaustion persists until the device is rebooted.
Summary
What happened
Memory leak in Zephyr RTOS 4.4.0 through 4.4.1 allows attackers to interrupt network reception via broadcast or multicast Ethernet frames. eth_bridge_input_process() returns NET_OK after local bridge delivery without consuming the packet, causing processing_data() to retain each RX net_pkt. Exploitation requires access to the bridged L2 segment and an affected bridge configuration; pool exhaustion persists until the device is rebooted.
The record
- CVE
- CVE-2026-14696
- Published
- Aug 31, 2026
- Updated
- Sep 1, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-401, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2026CVE publishedPublication date reported by the CVE source.
- Sep 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.4.0 <4.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo