Answer in brief
CVE-2026-52981 records a High severity (CVSS 7.5) vulnerability in neigh: let neigh_xmit take skb ownership. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <8a89054a1ec0767aec25ed2bbac933da6ba3cf5a || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <9247d59ca15bf60a57dca08103f055d8a4340877 || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <0084712e0bee204b284510cdb63182fd5a30c2b7 || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <63063ba60d2dc334e34f1e3f9271d7f3f6f30307 || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <445e45a2c3a078316a62d2d331a570cf34ef5079 || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <4438113be604ee67a7bf4f81da6e1cca41332ce4 | 8a89054a1ec0767aec25ed2bbac933da6ba3cf5a, 9247d59ca15bf60a57dca08103f055d8a4340877, 0084712e0bee204b284510cdb63182fd5a30c2b7, 63063ba60d2dc334e34f1e3f9271d7f3f6f30307, 445e45a2c3a078316a62d2d331a570cf34ef5079, 4438113be604ee67a7bf4f81da6e1cca41332ce4 |
| Linux/Linuxgeneric | 4.1 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-52981 records a High severity (CVSS 7.5) vulnerability in neigh: let neigh_xmit take skb ownership. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <8a89054a1ec0767aec25ed2bbac933da6ba3cf5a || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <9247d59ca15bf60a57dca08103f055d8a4340877 || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <0084712e0bee204b284510cdb63182fd5a30c2b7 || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <63063ba60d2dc334e34f1e3f9271d7f3f6f30307 || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <445e45a2c3a078316a62d2d331a570cf34ef5079 || >=4fd3d7d9e868ffbdb0e7a67c5c8e9dfdcd846a62 <4438113be604ee67a7bf4f81da6e1cca41332ce4 | 8a89054a1ec0767aec25ed2bbac933da6ba3cf5a, 9247d59ca15bf60a57dca08103f055d8a4340877, 0084712e0bee204b284510cdb63182fd5a30c2b7, 63063ba60d2dc334e34f1e3f9271d7f3f6f30307, 445e45a2c3a078316a62d2d331a570cf34ef5079, 4438113be604ee67a7bf4f81da6e1cca41332ce4 |
| Linux/Linuxgeneric | 4.1 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.