CVE-2026-74742

veth: fix queue index used to wake the peer txq in veth_poll

Published Aug 26, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

veth: fix queue index used to wake the peer txq in veth_poll

veth_poll() derives the index of the peer TX queue to wake from
rq->xdp_rxq.queue_index. That field is only initialized by
xdp_rxq_info_reg() in veth_enable_xdp_range(), which runs only when an
XDP program is attached. On the plain GRO/NAPI path
(veth_napi_enable_range()) xdp_rxq_info_reg() is never called, so
queue_index stays 0 for every queue, as priv->rq is zero-allocated.

So in a multi-queue setup with GRO enabled and no XDP program attached,
every NAPI instance looks at the peer's TX queue 0. If veth_xmit() stops
peer TX queue 1 because the ptr_ring is full (NETDEV_TX_BUSY), nothing
ever wakes it again: the poller draining queue 1 wakes queue 0 instead.
veth implements no ndo_tx_timeout, so the netdev watchdog does not kick
in either, and the queue stays stopped indefinitely.

Derive the index from the position of the rq within priv->rq instead,
which is correct regardless of whether XDP was ever enabled.

Scripts to reproduce the stall are available at
https://github.com/netoptimizer/veth-backpressure-performance-testing

Analysis

AI-generated

Technical impact

In the Linux kernel, the veth_poll() routine mistakenly derives the peer TX queue index from rq->xdp_rxq.queue_index, a field that is initialized only when an XDP program is attached. In a multi‑queue veth device with Generic Receive Offload enabled and no XDP program, this field defaults to 0 for every queue. Consequently, when the peer’s queue 1 becomes busy and stops, the poller continues to target queue 0, never waking the stalled queue. The driver also lacks a tx‑timeout handler, so the stalled queue remains blocked indefinitely, causing a denial of service on the virtual network link. This weakness corresponds to CWE‑1285.

Affected Systems

All Linux kernel implementations that include the veth driver prior to the patch and are configured with multi‑queue veth interfaces and GRO enabled are affected. The CVE record does not specify particular kernel versions, so any kernel lacking the fix is potentially vulnerable.

Risk and Exploitability

The CVSS score of 7.5 and an EPSS score of < 1% indicate a moderate severity and a low chance of exploitation. Based on the description, it is inferred that the vulnerability is local and can be triggered by a local user or process that can create or manipulate veth interfaces and generate traffic that triggers back‑pressure. It is also inferred that remote hosts cannot directly influence the peer queue indices. Since the kernel does not invoke a watchdog timeout, the affected queue can remain stalled for an extended period, resulting in sustained denial of service for traffic on the veth pair.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that contains the veth_poll queue‑index fix.
  • If a kernel upgrade is not immediately possible, disable Generic Receive Offload on the veth interfaces to bypass the faulty wake path.
  • Ensure that veth devices use a single transmit queue or attach an XDP program before enabling multi‑queue operation to avoid the stale queue‑index scenario.

Generated by OpenCVE AI on August 28, 2026 at 19:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4788-1 linux-6.12 security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9160-1 Linux kernel (Azure) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-399
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Weaknesses CWE-399
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: veth: fix queue index used to wake the peer txq in veth_poll veth_poll() derives the index of the peer TX queue to wake from rq->xdp_rxq.queue_index. That field is only initialized by xdp_rxq_info_reg() in veth_enable_xdp_range(), which runs only when an XDP program is attached. On the plain GRO/NAPI path (veth_napi_enable_range()) xdp_rxq_info_reg() is never called, so queue_index stays 0 for every queue, as priv->rq is zero-allocated. So in a multi-queue setup with GRO enabled and no XDP program attached, every NAPI instance looks at the peer's TX queue 0. If veth_xmit() stops peer TX queue 1 because the ptr_ring is full (NETDEV_TX_BUSY), nothing ever wakes it again: the poller draining queue 1 wakes queue 0 instead. veth implements no ndo_tx_timeout, so the netdev watchdog does not kick in either, and the queue stays stopped indefinitely. Derive the index from the position of the rq within priv->rq instead, which is correct regardless of whether XDP was ever enabled. Scripts to reproduce the stall are available at https://github.com/netoptimizer/veth-backpressure-performance-testing
Title veth: fix queue index used to wake the peer txq in veth_poll
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-1285

    Improper Validation of Specified Index, Position, or Offset in Input

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 27, 2026, 5:01 AM
Reserved
Aug 15, 2026, 5:44 AM
Status
Received
Published
Aug 26, 2026, 3:16 PM
Modified
Aug 27, 2026, 6:17 AM
Severity
Moderate
Public date
Aug 26, 2026, 12:00 AM