CVE-2026-52981

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
7.5
EG Score
7.5(high)
EPSS
41.4%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (6)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

neigh: let neigh_xmit take skb ownership - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9247d59ca15bf60a57dca08103f055d8a4340877
generic

neigh: let neigh_xmit take skb ownership - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a89054a1ec0767aec25ed2bbac933da6ba3cf5a
generic

neigh: let neigh_xmit take skb ownership - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63063ba60d2dc334e34f1e3f9271d7f3f6f30307
generic

neigh: let neigh_xmit take skb ownership - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/445e45a2c3a078316a62d2d331a570cf34ef5079
generic

neigh: let neigh_xmit take skb ownership - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4438113be604ee67a7bf4f81da6e1cca41332ce4
generic

neigh: let neigh_xmit take skb ownership - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0084712e0bee204b284510cdb63182fd5a30c2b7

Vendor Advisories for CVE-2026-52981(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 37× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 22:27 UTCEG score recompute
  2. 2026-07-06 22:27 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:21 UTCEG score recompute
  6. 2026-07-06 11:21 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 23:54 UTCEG score recompute
  10. 2026-07-05 23:54 UTCGHSA enrichment
  11. 2026-07-05 12:47 UTCEG score recompute
  12. 2026-07-05 12:46 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 01:39 UTCEG score recompute
  16. 2026-07-05 01:39 UTCGHSA enrichment
  17. 2026-07-04 14:29 UTCEG score recompute
  18. 2026-07-04 14:29 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 03:23 UTCEG score recompute
  21. 2026-07-04 03:23 UTCGHSA enrichment
  22. 2026-07-03 16:12 UTCEG score recompute
  23. 2026-07-03 16:12 UTCGHSA enrichment
  24. 2026-07-03 05:05 UTCEG score recompute
  25. 2026-07-03 05:04 UTCGHSA enrichment
Show 24 more
  1. 2026-07-02 17:55 UTCEG score recompute
  2. 2026-07-02 17:55 UTCGHSA enrichment
  3. 2026-07-02 06:47 UTCEG score recompute
  4. 2026-07-02 06:47 UTCGHSA enrichment
  5. 2026-07-01 19:40 UTCEG score recompute
  6. 2026-07-01 19:40 UTCGHSA enrichment
  7. 2026-07-01 15:07 UTCEPSS rescore
  8. 2026-07-01 08:34 UTCEG score recompute
  9. 2026-07-01 08:34 UTCGHSA enrichment
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-30 21:27 UTCEG score recompute▲ 7.50
  12. 2026-06-30 21:27 UTCGHSA enrichment
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 19:57 UTCEG score recompute
  20. 2026-06-27 19:57 UTCGHSA enrichment
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-24 18:26 UTCEG score recompute
  24. 2026-06-24 18:02 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52981?
CVE-2026-52981 is a high vulnerability published on June 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).…
When was CVE-2026-52981 disclosed?
CVE-2026-52981 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52981 actively exploited?
CVE-2026-52981 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 41.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52981?
CVE-2026-52981 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-52981?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52981, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-52981

Explore →

Is Your Infrastructure Affected by CVE-2026-52981?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs