CVE-2026-74742veth: fix queue index used to wake the peer txq in veth_poll
- 7.5HighCVSS base score
- 0.46%Exploitation in 30 daysEPSS · top 60% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Received | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.46% · top 60% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
- affected 9fe31b3f314534e238aa6d0b6fb492134cbcf8be – < b662a1fb4f3a5ea19bac24eea8315b1d05be51e7
- affected dc82a33297fc2c58cb0b2b008d728668d45c0f6a – < 73f8dd22b1e533a99ecc3f9b5de6c6daccaecace
- affected dc82a33297fc2c58cb0b2b008d728668d45c0f6a – < 90bb11fb29d3c55a2c46dc7c386d096b286e7fcf
- affected dc82a33297fc2c58cb0b2b008d728668d45c0f6a – < 60db47f02bfa2aa688938aa199117ec4f8e31d23
- affected 6.12.61 – < 6.12.105
- affected 6.16
- unaffected < 6.16
- unaffected 6.12.105 – ≤ 6.12.*
- unaffected 6.18.46 – ≤ 6.18.*
- unaffected 7.1.10 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/b662a1fb4f3a5ea19bac24eea8315b1d05be51e7 (opens in a new tab)
- https://git.kernel.org/stable/c/73f8dd22b1e533a99ecc3f9b5de6c6daccaecace (opens in a new tab)
- https://git.kernel.org/stable/c/90bb11fb29d3c55a2c46dc7c386d096b286e7fcf (opens in a new tab)
- https://git.kernel.org/stable/c/60db47f02bfa2aa688938aa199117ec4f8e31d23 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-66572 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74742)Record last updated .