FKIE_CVE-2026-98022

Vulnerability from fkie_nvd - Published: 2026-09-25 11:17 - Updated: 2026-09-25 11:17
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations Several subsystems allocate ring buffers sized by dev->tx_queue_len with no upper bound. An unprivileged user (via unshare -Urn) can set a huge tx_queue_len and exhaust global memory with ring allocations: - pfifo_fast: pfifo_fast_init() and pfifo_fast_change_tx_queue_len() allocate 3 skb_array rings of tx_queue_len entries each. - tun: tun_queue_resize() and the queue-attach path resize ptr_rings to tx_queue_len on the NETDEV_CHANGE_TX_QUEUE_LEN notifier. - tap (macvtap/ipvtap): tap_queue_resize() and tap_init() resize/init ptr_rings to tx_queue_len on the same notifier. netif_change_tx_queue_len() is the single entry point for IFLA_TXQLEN, sysfs, and the SIOCSIFTXQLEN ioctl. Cap new_len at S16_MAX (32767) there so the oversized value is rejected at set time. This takes effect whether the device is up or down, before dev->tx_queue_len is written, before any notifier fires, and before any ring is allocated. The "> S16_MAX" check also subsumes the previous unsigned-long truncation test, and a negative ifr_qlen from the ioctl lands far above the cap after conversion, so both old failure modes are covered by the one comparison. tx_queue_len is ambigious: both a per-ring sizing multiplier and a default queue-length/limit knob for consumers that allocate nothing at set time (pfifo/bfifo/gred/plug/sfb limits, htb direct_qlen, qfq max_classes, teql). 32767 is chosen as the largest value NLA_POLICY_FULL_RANGE can express for the u32 IFLA_TXQLEN policy in patch 2/3 while staying a legitimate queue length on high-BDP paths; the ring-memory trade-off of a shared knob is disclosed below. Conditions to recreate the bug: - CONFIG_NET_SCHED=y, CONFIG_VETH=y, CONFIG_USER_NS=y, CONFIG_NET_NS=y. - Unprivileged user in a fresh user+net namespace (unshare -Urn). - pfifo_fast: create veth pairs, set tx_queue_len to 500000, attach mq+pfifo_fast. ~28 iterations OOMs a 2GB guest. - tun: create 50 tun devices with IFF_MULTI_QUEUE, set tx_queue_len to 500000, open 8 queues each. ~1.6GB of ptr_ring allocations OOMs a 512MB guest. - tap: same as tun with IFF_TAP. ~960MB OOMs a 512MB guest. - On the fixed kernel the oversized tx_queue_len is rejected with -ERANGE at set time (all four paths: RTM_SETLINK, RTM_NEWLINK create, sysfs, ioctl - the latter two via this check, the former two via this check and the 2/3 parse policy respectively).
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/081340cf70a789b94b4174af54a63ffd49677a4e
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/66ab4c59b74db7ab53a1c9083feaaede393a96a0
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/81c0e02076989743a603806a5a4f44d2c40dc01f
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/a03b927bae4af5c23fd5315a237855c17cc8f422
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/core/dev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "81c0e02076989743a603806a5a4f44d2c40dc01f",
              "status": "affected",
              "version": "6a643ddb5624be7e0694d49f5765a8d41c1ab6d0",
              "versionType": "git"
            },
            {
              "lessThan": "081340cf70a789b94b4174af54a63ffd49677a4e",
              "status": "affected",
              "version": "6a643ddb5624be7e0694d49f5765a8d41c1ab6d0",
              "versionType": "git"
            },
            {
              "lessThan": "a03b927bae4af5c23fd5315a237855c17cc8f422",
              "status": "affected",
              "version": "6a643ddb5624be7e0694d49f5765a8d41c1ab6d0",
              "versionType": "git"
            },
            {
              "lessThan": "66ab4c59b74db7ab53a1c9083feaaede393a96a0",
              "status": "affected",
              "version": "6a643ddb5624be7e0694d49f5765a8d41c1ab6d0",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/core/dev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.16"
            },
            {
              "lessThan": "4.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.111",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.53",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: cap tx_queue_len at S16_MAX to prevent oversized ring allocations\n\nSeveral subsystems allocate ring buffers sized by dev-\u003etx_queue_len\nwith no upper bound. An unprivileged user (via unshare -Urn) can set a\nhuge tx_queue_len and exhaust global memory with ring allocations:\n\n- pfifo_fast: pfifo_fast_init() and pfifo_fast_change_tx_queue_len()\n  allocate 3 skb_array rings of tx_queue_len entries each.\n- tun: tun_queue_resize() and the queue-attach path resize ptr_rings\n  to tx_queue_len on the NETDEV_CHANGE_TX_QUEUE_LEN notifier.\n- tap (macvtap/ipvtap): tap_queue_resize() and tap_init() resize/init\n  ptr_rings to tx_queue_len on the same notifier.\n\nnetif_change_tx_queue_len() is the single entry point for IFLA_TXQLEN,\nsysfs, and the SIOCSIFTXQLEN ioctl. Cap new_len at S16_MAX (32767)\nthere so the oversized value is rejected at set time. This takes\neffect whether the device is up or down, before dev-\u003etx_queue_len is\nwritten, before any notifier fires, and before any ring is allocated.\nThe \"\u003e S16_MAX\" check also subsumes the previous unsigned-long\ntruncation test, and a negative ifr_qlen from the ioctl lands far\nabove the cap after conversion, so both old failure modes are covered\nby the one comparison.\n\ntx_queue_len is ambigious: both a per-ring sizing multiplier and a\ndefault queue-length/limit knob for consumers that allocate\nnothing at set time (pfifo/bfifo/gred/plug/sfb limits, htb\ndirect_qlen, qfq max_classes, teql). 32767 is chosen as the largest\nvalue NLA_POLICY_FULL_RANGE can express for the u32 IFLA_TXQLEN\npolicy in patch 2/3 while staying a legitimate queue length on\nhigh-BDP paths; the ring-memory trade-off of a shared knob is\ndisclosed below.\n\nConditions to recreate the bug:\n- CONFIG_NET_SCHED=y, CONFIG_VETH=y, CONFIG_USER_NS=y, CONFIG_NET_NS=y.\n- Unprivileged user in a fresh user+net namespace (unshare -Urn).\n- pfifo_fast: create veth pairs, set tx_queue_len to 500000, attach\n  mq+pfifo_fast. ~28 iterations OOMs a 2GB guest.\n- tun: create 50 tun devices with IFF_MULTI_QUEUE, set tx_queue_len to\n  500000, open 8 queues each. ~1.6GB of ptr_ring allocations OOMs a\n  512MB guest.\n- tap: same as tun with IFF_TAP. ~960MB OOMs a 512MB guest.\n- On the fixed kernel the oversized tx_queue_len is rejected with\n  -ERANGE at set time (all four paths: RTM_SETLINK, RTM_NEWLINK\n  create, sysfs, ioctl - the latter two via this check, the former\n  two via this check and the 2/3 parse policy respectively)."
    }
  ],
  "id": "CVE-2026-98022",
  "lastModified": "2026-09-25T11:17:30.740",
  "metrics": {},
  "published": "2026-09-25T11:17:30.740",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/081340cf70a789b94b4174af54a63ffd49677a4e"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/66ab4c59b74db7ab53a1c9083feaaede393a96a0"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/81c0e02076989743a603806a5a4f44d2c40dc01f"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/a03b927bae4af5c23fd5315a237855c17cc8f422"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.