{
  "id": "CVE-2026-74742",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-74742",
  "published_at": "2026-08-26T14:36:53.58Z",
  "title": "veth: fix queue index used to wake the peer txq in veth_poll",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.5,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nveth: fix queue index used to wake the peer txq in veth_poll\n\nveth_poll() derives the index of the peer TX queue to wake from\nrq-\u003exdp_rxq.queue_index. That field is only initialized by\nxdp_rxq_info_reg() in veth_enable_xdp_range(), which runs only when an\nXDP program is attached. On the plain GRO/NAPI path\n(veth_napi_enable_range()) xdp_rxq_info_reg() is never called, so\nqueue_index stays 0 for every queue, as priv-\u003erq is zero-allocated.\n\nSo in a multi-queue setup with GRO enabled and no XDP program attached,\nevery NAPI instance looks at the peer's TX queue 0. If veth_xmit() stops\npeer TX queue 1 because the ptr_ring is full (NETDEV_TX_BUSY), nothing\never wakes it again: the poller draining queue 1 wakes queue 0 instead.\nveth implements no ndo_tx_timeout, so the netdev watchdog does not kick\nin either, and the queue stays stopped indefinitely.\n\nDerive the index from the position of the rq within priv-\u003erq instead,\nwhich is correct regardless of whether XDP was ever enabled.\n\nScripts to reproduce the stall are available at\nhttps://github.com/netoptimizer/veth-backpressure-performance-testing",
  "cvss_by_source": {
    "cna": 7.5
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 9fe31b3f314534e238aa6d0b6fb492134cbcf8be, \u003c b662a1fb4f3a5ea19bac24eea8315b1d05be51e7",
          "\u003e= dc82a33297fc2c58cb0b2b008d728668d45c0f6a, \u003c 73f8dd22b1e533a99ecc3f9b5de6c6daccaecace",
          "\u003e= dc82a33297fc2c58cb0b2b008d728668d45c0f6a, \u003c 90bb11fb29d3c55a2c46dc7c386d096b286e7fcf",
          "\u003e= dc82a33297fc2c58cb0b2b008d728668d45c0f6a, \u003c 60db47f02bfa2aa688938aa199117ec4f8e31d23",
          "\u003e= 6.12.61, \u003c 6.12.105"
        ],
        "fixed_in": [
          "b662a1fb4f3a5ea19bac24eea8315b1d05be51e7",
          "73f8dd22b1e533a99ecc3f9b5de6c6daccaecace",
          "90bb11fb29d3c55a2c46dc7c386d096b286e7fcf",
          "60db47f02bfa2aa688938aa199117ec4f8e31d23",
          "6.12.105"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "6.16"
        ],
        "fixed_in": [
          "0",
          "6.12.105",
          "6.18.46",
          "7.1.10",
          "7.2"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to b662a1fb4f3a5ea19bac24eea8315b1d05be51e7 or 73f8dd22b1e533a99ecc3f9b5de6c6daccaecace or 90bb11fb29d3c55a2c46dc7c386d096b286e7fcf or 60db47f02bfa2aa688938aa199117ec4f8e31d23 or 6.12.105 or later.",
      "Upgrade Linux to 0 or 6.12.105 or 6.18.46 or 7.1.10 or 7.2 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
