Zephyr denial of service in IPv6 router advertisement handling
- Exploited
- No known exploitation
- Fix
- Fixed in 4.3.2, 4.5.0
- Who is exposed
- Not reported
Summary
Zephyr's IPv6 neighbour discovery code leaks packet references when it handles Router Advertisements, which can exhaust the packet buffer pool. An attacker on the same network link can trigger this remotely, without logging in, by sending unauthenticated Router Advertisement messages, leaving the affected node unable to send any traffic.
Written by a model
Original description
The IPv6 neighbour discovery code in subsys/net/ip/ipv6_nbr.c keeps packets that are waiting for address resolution on a per-neighbour pending queue. A queued packet holds two references: the one handed over by the sender and a second one taken by net_ipv6_send_ns() when the packet is put on the queue. The Router Advertisement handler handle_ra_input() popped each packet off the queue and passed it to net_send_data(), relying on a trailing nbr_clear_ns_pending() call to release the queue reference — but that call then found the queue already empty and released nothing, so one reference was leaked for every pending packet flushed on an RA.
Router Advertisements are unauthenticated link-local ICMPv6 messages, so any node on the same link can trigger the flush. An attacker can make the leak deterministic by advertising itself as a router without a source link-layer address option, so the victim's neighbour entry stays INCOMPLETE, then inducing the victim to transmit through that next hop (the packet is queued and a neighbour solicitation is sent), leaving the solicitation unanswered and sending a further RA to drain the queue. Each round leaks one struct net_pkt together with its net_buf chain.
Leaked packets are never returned to the fixed-size pools, so the loss is permanent for the lifetime of the boot. With CONFIG_NET_PKT_TX_COUNT defaulting to 4 (14 with CONFIG_NET_PKT_LARGE_DEFAULTS), a small number of repetitions exhausts the transmit packet slab and the node stops being able to send any traffic. The impact is availability only: the reference count is always too high, never too low, so no use-after-free or memory corruption arises.
The fix moves the flush into a helper, nbr_send_pending(), which releases the queue reference for every packet it takes off the queue before handing the remaining reference to net_send_data(), and releases that one too if the send is refused.
What to do
Upgrade to a fixed version: 4.3.2, 4.5.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-95827 (Network packet reference leak in IPv6 Router Advertisement handling leads to buffer pool exhaustion), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-95827 (entry last updated 2026-11-20):
Affected:
- zephyrproject zephyr: from 4.3.0, fixed in 4.3.2; from 4.4.0, fixed in 4.5.0
Fixed versions: 4.3.2, 4.5.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-95827 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-95827 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/zephyrproject-rtos/zephyr/commit/49365642e6ade44d699bd2751ff28d6097064918
- https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r5mf-pgjr-5jrh
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-95827
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-95827"}.Affected versions
- zephyrFrom 4.3.0 · fixed in 4.3.2; From 4.4.0 · fixed in 4.5.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · zephyrproject-rtos/zephyr · Advisory GHSA-r5mf-pgjr-5jrh |
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-95827 |
| Other links 1 | |
| Patch | GitHub · zephyrproject-rtos/zephyr · Commit 49365642 |
Questions about CVE-2026-95827
Is CVE-2026-95827 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-95827?
zephyr: from 4.3.0 before 4.3.2; from 4.4.0 before 4.5.0.
Source: cve.now feed data
How do I fix CVE-2026-95827?
Upgrade to a fixed version: 4.3.2, 4.5.0.
Source: cve.now feed data
Related
- CVE-2026-77685Bluetooth Classic RFCOMM: integer underflow in the MCC TEST command handler leads to out-of-bounds read disclosed to the peer and…
- CVE-2026-91007Arbitrary supervisor-mode function pointer injection via charger_set_prop() syscall in the charger driver API
- CVE-2026-90833Signed offset bypasses bounds check in simulated EEPROM driver, allowing out-of-bounds kernel memory read and write from user mode
- CVE-2026-95826Out-of-bounds write in the SMSC911x Ethernet driver when transmitting frames larger than the staging buffer
- CVE-2026-95823Use-after-free and net_buf leak in Zephyr TCP header linearization (tcp_pkt_linearize)
- CVE-2026-95824Infinite loop in IPv6 Router Advertisement handling when the RA omits the source link-layer address option
No corrections so far. Something wrong on this page? Report an error.