PT-2026-153066
CVE-2026-95824
·
تاريخ النشر
2026-11-20
·
تاريخ التحديث
2026-11-20
الوصف من
CVSS 3.1
6.5
متوسطةالمقاييسAV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The IPv6 Neighbor Discovery code in subsys/net/ip/ipv6 nbr.c flushes a neighbour's queued packets at the end of handle ra input(). The Source Link-Layer Address Option (SLLAO) is optional in a Router Advertisement; when it is absent, handle ra input() still obtains (or creates) a neighbour cache entry for the RA source via net ipv6 nbr add() with a NULL link-layer address, so the entry stays in NET IPV6 NBR STATE INCOMPLETE with nbr->idx == NET NBR LLADDR UNKNOWN. The pending-packet drain loop was entered unconditionally for that unresolved entry.
Each net send data() in the drain loop runs synchronously into net ipv6 prepare for send(), which finds the neighbour still unresolved and hands the packet to net ipv6 send ns(), which puts it straight back onto the same pending queue. The loop therefore never sees an empty queue. With a single queued packet it transmits a fresh Neighbor Solicitation on every iteration; with two or more queued packets it rotates the queue with no allocation and no transmission at all. The loop runs in the network RX thread with the global IPv6 neighbour mutex held.
An unauthenticated attacker on the same link can trigger this deterministically: advertise itself as a router, induce the victim to queue off-link traffic toward that router (for example by sending echo requests with an off-link source address) while leaving the solicitation unanswered, then send a second Router Advertisement without an SLLAO option. Spoofing an SLLAO-less RA from the legitimate router's link-local address has the same effect whenever traffic is queued for it. Router Advertisements are processed with no authentication whenever CONFIG NET IPV6 ND is enabled, which is the default for IPv6-capable builds.
The result is a permanent denial of service: the RX thread spins forever holding the neighbour lock, so all IPv6 transmission and every other user of the neighbour cache blocks, and the Neighbor Advertisement that would resolve the entry can no longer be processed. The ipv6 ns reply timer work item that would normally drop the pending packets also blocks on the same mutex. In the single-packet variant the loop additionally floods the link with Neighbor Solicitations. The fix restricts the flush to resolved entries (nbr->idx != NET NBR LLADDR UNKNOWN), leaving the packets queued for the NS reply timeout. There is no memory-safety impact.
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾