In the Linux kernel, the following vulnerability has been resolved:
neigh: let neigh_xmit take skb ownership
neighxmit always releases the skb, except when no neighbour table is found. But even the first added user of neighxmit (mpls) relied on neigh_xmit to release the skb (or queue it for tx).
sashiko reported: If neighxmit() is called with an uninitialized neighbor table (for example, NEIGHNDTABLE when IPv6 is disabled), it returns -EAFNOSUPPORT and bypasses its internal outkfreeskb error path. Because the return value of neighxmit() is ignored here, does this leak the SKB?
Assume full ownership and remove the last code path that doesn't xmit or free skb.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/52xxx/CVE-2026-52981.json",
"cna_assigner": "Linux"
}