All reports
Low

kernel: neigh: let neigh_xmit take skb ownership

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-52981

Probability of exploitation in the next 30 days: 0.53%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: neigh: let neigh_xmit take skb ownership neigh_xmit always releases the skb, except when no neighbour table is found. But even the first added user of neigh_xmit (mpls) relied on neigh_xmit to release the skb (or queue it for tx). sashiko reported: If neigh_xmit() is called with an uninitialized neighbor table (for example, NEIGH_ND_TABLE when IPv6 is disabled), it returns -EAFNOSUPPORT and bypasses its internal out_kfree_skb error path. Because the return value of neigh_xmit() is ignored here, does this leak the SKB? Assume full ownership and remove the last code path that doesn't xmit or free skb.

A flaw was found in the Linux kernel. The neigh_xmit function, when called with an uninitialized neighbor table (such as NEIGH_ND_TABLE when IPv6 is disabled), can return an error without properly releasing the allocated skb (socket buffer). This can lead to a memory leak, potentially impacting system stability and resource availability.