Wind River Support Network

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.