CVE-2026-80613

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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:

veth: fix NAPI leak in XDP enable error path

During XDP enablement in veth, if xdp_rxq_info_reg() or xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes.

However, the rollback loop: for (i--; i >= start; i--) {

decrements the loop index 'i' before the first iteration. This correctly skips unregistering the rxq for the failed index 'i' (as registration failed or was already cleaned up), but it also erroneously skips calling netif_napi_deli() for rq[i].xdp_napi.

Since netif_napi_add() was already called for index 'i', this leaves a dangling napi_struct in the device's napi_list. When the veth device is later destroyed, the freed queue memory (which contains the leaked NAPI structure) can be reused.

The subsequent device teardown iterates the NAPI list and corrupts the reallocated memory, leading to UAF.

Fix this by explicitly deleting the NAPI association for the failed index 'i' before rolling back the successfully configured queues.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (7)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

veth: fix NAPI leak in XDP enable error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6739027cb72da26890edd424c77080d187b2a92e
generic

veth: fix NAPI leak in XDP enable error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4bd2e5dbe62334aae1182d0f0d260f334a49d739
generic

veth: fix NAPI leak in XDP enable error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a9e6707322ef215d39d4655b176c094f45f0ab52
generic

veth: fix NAPI leak in XDP enable error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d3eb258ad398cc9402bab3a5e730cd7c5b34efad
generic

veth: fix NAPI leak in XDP enable error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83090f5e7b54721d71875a6c224d2490b9e73050
generic

veth: fix NAPI leak in XDP enable error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4559770b2a241344d762719e674241fcc8528f02
generic

veth: fix NAPI leak in XDP enable error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fc51373345e7e6ea73da2650cb497309c50b077a

Vendor Advisories for CVE-2026-80613(1)

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 12× in last 7d / 12× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 19:14 UTCEG score recompute
  3. 2026-08-29 19:13 UTCGHSA enrichment
  4. 2026-08-29 07:27 UTCEG score recompute
  5. 2026-08-29 07:27 UTCGHSA enrichment
  6. 2026-08-29 06:37 UTCEG score recompute 7.80
  7. 2026-08-29 06:37 UTCGHSA enrichment
  8. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-28 08:20 UTCNVD update
  11. 2026-08-28 07:36 UTCEG score recompute
  12. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80613?
CVE-2026-80613 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: veth: fix NAPI leak in XDP enable error path During XDP enablement in veth, if xdprxqinfo_reg() or xdprxqinforegmem_model() fails, the driver rolls back the changes. However, the rollback loop: for (i--; i >= start; i--) {…
When was CVE-2026-80613 disclosed?
CVE-2026-80613 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80613 actively exploited?
CVE-2026-80613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-80613?
CVE-2026-80613 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80613, 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-80613

Explore →

Is Your Infrastructure Affected by CVE-2026-80613?

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