neigh: let neigh_xmit take skb ownership
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 · < 4438113be604ee67a7bf4f81da6e1cca41332ce4| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
Linux kernel neigh_xmit can leak a socket buffer when called with an uninitialized neighbor table, such as when IPv6 is disabled. The supplied description does not establish whether an attacker can trigger this remotely or locally, or whether authentication or user interaction is required.
Teams running Linux kernels should check whether their kernel includes the affected neigh_xmit code; affected versions were not provided.