CVE-2026-74742

CVE CVE-2026-74742EUVD EUVD-2026-66572Published 2026-08-26T14:36:53.000ZLast changed 2026-08-27T05:01:02.000ZCVSS 7.5

What the advisory describes

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

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 6.12.61 <6.12.105; 6.16; patch: 0; dc82a33297fc2c58cb0b2b008d728668d45c0f6a <90bb11fb29d3c55a2c46dc7c386d096b286e7fcf; dc82a33297fc2c58cb0b2b008d728668d45c0f6a <60db47f02bfa2aa688938aa199117ec4f8e31d23; patch: 6.18.46; patch: 6.12.105; 9fe31b3f314534e238aa6d0b6fb492134cbcf8be <b662a1fb4f3a5ea19bac24eea8315b1d05be51e7; dc82a33297fc2c58cb0b2b008d728668d45c0f6a <73f8dd22b1e533a99ecc3f9b5de6c6daccaecace; patch: 7.2; patch: 7.1.10

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.