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.
CVSS
7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
from 4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 before 8a89054a1ec0767aec25ed2bbac933da6ba3cf5a; from 4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 before 9247d59ca15bf60a57dca08103f055d8a4340877; from 4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 before 0084712e0bee204b284510cdb63182fd5a30c2b7; from 4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 before 63063ba60d2dc334e34f1e3f9271d7f3f6f30307; from 4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 before 445e45a2c3a078316a62d2d331a570cf34ef5079; from 4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 before 4438113be604ee67a7bf4f81da6e1cca41332ce4
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.
Printed from infosecsignals.com. Every record links back to the agency that published it.
Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.