Skip to content
Threat Brief

← All advisories

CVE-2026-98021

High 7.1No known exploitationFix available

net: reject oversized tx_queue_len at netlink parse time

Record last updated

CVSS score

7.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 7% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: net: reject oversized tx_queue_len at netlink parse time rtnl_create_link() assigns IFLA_TXQLEN directly to dev->tx_queue_len without going through netif_change_tx_queue_len(), so a device created with "ip link add ... txqueuelen 500000" bypasses the S16_MAX cap and still triggers the oversized ring allocations in pfifo_fast, tun and tap. The veth peer nest (rtnl_nla_parse_ifinfomsg()) and the RTM_NEWLINK-on-existing-device path reach the same sinks. Enforce the cap in ifla_policy instead: IFLA_TXQLEN becomes NLA_POLICY_FULL_RANGE(NLA_U32, &txqlen_range) with txqlen_range = { .min = 0, .max = S16_MAX }. All netlink consumers parse against this policy - rtnl_setlink(), rtnl_newlink() (create and change), and the veth peer nest - so every netlink path is capped at parse time and rejects the attribute with -ERANGE plus a proper "integer out of range" extack message before any device state is modified (the RTM_SETLINK half-application wart is gone with it). Document the bound in the rt-link.yaml netlink spec. 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): ip link add v0 txqueuelen 500000 type veth peer name v1 -> on the fixed kernel this is rejected with -ERANGE ("integer out of range" extack) instead of installing an oversized tx_queue_len that later inflates pfifo_fast/tun/tap ring allocations. - ip link set v0 txqueuelen 500000 is likewise rejected at parse time.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 38f7b870d4a6a5d3ec21557e849620cb7d032965 before a638a2625aa83160a394abe8e8b2e524a80c771ba638a2625aa83160a394abe8e8b2e524a80c771bCVE Program
LinuxLinuxfrom 38f7b870d4a6a5d3ec21557e849620cb7d032965 before 1aa9e143bf51405665a793d4cc925e1c4f0c59221aa9e143bf51405665a793d4cc925e1c4f0c5922CVE Program
LinuxLinuxfrom 38f7b870d4a6a5d3ec21557e849620cb7d032965 before 26ee5f99ffe7ab98e635071290eff14192e9e34a26ee5f99ffe7ab98e635071290eff14192e9e34aCVE Program
LinuxLinuxfrom 38f7b870d4a6a5d3ec21557e849620cb7d032965 before 45ca9f59b6c7ea70e0a17054902b8a556913db3445ca9f59b6c7ea70e0a17054902b8a556913db34CVE Program
LinuxLinuxfrom 38f7b870d4a6a5d3ec21557e849620cb7d032965 before 2fd0880f0272ec022906a05587fd91416ebecc382fd0880f0272ec022906a05587fd91416ebecc38CVE Program
LinuxLinux2.6.23Not documentedCVE Program
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.159.1-1 on Azure Linux 3.0Not documented6.6.161.1-1Microsoft MSRC
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.111 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.53 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.160 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.7 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 2.6.23Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Advisory change

    Microsoft advisory revised (6.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  8. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references