CVE-2026-95827: Network packet reference leak in IPv6 Router Advertisement handling leads to buffer pool exhaustion
The IPv6 neighbour discovery code in subsys/net/ip/ipv6nbr.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 netipv6sendns() when the packet is put on the queue. The Router Advertisement handler handlerainput() popped each packet off the queue and passed it to netsenddata(), relying on a trailing nbrclearnspending() 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 netpkt together with its netbuf chain.
Leaked packets are never returned to the fixed-size pools, so the loss is permanent for the lifetime of the boot. With CONFIGNETPKTTXCOUNT defaulting to 4 (14 with CONFIGNETPKTLARGEDEFAULTS), 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, nbrsendpending(), which releases the queue reference for every packet it takes off the queue before handing the remaining reference to netsenddata(), and releases that one too if the send is refused.