CVE-2026-80613

veth: fix NAPI leak in XDP enable error path

HIGH
7.8
CVSS Score
Published: August 28, 2026 at 06:48 AM UTC
Updated: October 16, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11b02e5a0ebb172c8276cea3151942aac681f7a4a6
Vendor states this is fixed in 4559770b2a241344d762719e674241fcc8528f02 (fixed)
Vendor states this is fixed in 4bd2e5dbe62334aae1182d0f0d260f334a49d739 (fixed)
Vendor states this is fixed in 6739027cb72da26890edd424c77080d187b2a92e (fixed)
Vendor states this is fixed in 83090f5e7b54721d71875a6c224d2490b9e73050 (fixed)
Vendor states this is fixed in a9e6707322ef215d39d4655b176c094f45f0ab52 (fixed)
Vendor states this is fixed in d3eb258ad398cc9402bab3a5e730cd7c5b34efad (fixed)
Vendor states this is fixed in fc51373345e7e6ea73da2650cb497309c50b077a (fixed)
Vendor states this is fixed in 5.11 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card