Skip to main content
VulnerabilityPublished Updated

CVE-2026-98022: Linux kernel · net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in c2362c500931e5bd1826bce34e9ce28af80e7541 : patch Linux kernel soon.

Data as of 26 Oct 2026, 16:39 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in c2362c500931e5bd1826bce34e9ce28af80e7541, c8d4060610c69645733c92d94fceb4b93808ac4d, a03b927bae4af5c23fd5315a237855c17cc8f422 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 6a643ddb5624be7e0694d49f5765a8d41c1ab6d0, < c2362c500931e5bd1826bce34e9ce28af80e7541
Fixed in
  • c2362c500931e5bd1826bce34e9ce28af80e7541
LinuxLinuxAffected
  • ≥ 6a643ddb5624be7e0694d49f5765a8d41c1ab6d0, < c8d4060610c69645733c92d94fceb4b93808ac4d
Fixed in
  • c8d4060610c69645733c92d94fceb4b93808ac4d
LinuxLinuxAffected
  • ≥ 6a643ddb5624be7e0694d49f5765a8d41c1ab6d0, < a03b927bae4af5c23fd5315a237855c17cc8f422
Fixed in
  • a03b927bae4af5c23fd5315a237855c17cc8f422
LinuxLinuxAffected
  • ≥ 6a643ddb5624be7e0694d49f5765a8d41c1ab6d0, < 081340cf70a789b94b4174af54a63ffd49677a4e
Fixed in
  • 081340cf70a789b94b4174af54a63ffd49677a4e
LinuxLinuxAffected
  • ≥ 6a643ddb5624be7e0694d49f5765a8d41c1ab6d0, < 81c0e02076989743a603806a5a4f44d2c40dc01f
Fixed in
  • 81c0e02076989743a603806a5a4f44d2c40dc01f
LinuxLinuxAffected
  • ≥ 6a643ddb5624be7e0694d49f5765a8d41c1ab6d0, < 66ab4c59b74db7ab53a1c9083feaaede393a96a0
Fixed in
  • 66ab4c59b74db7ab53a1c9083feaaede393a96a0

AI-suggested

A fix is available and has been applied in the Linux kernel commits listed under fixedVersions. Systems should update to a kernel version including these fixes to prevent exploitation. The fix enforces a maximum tx_queue_len value of 32767, rejecting larger values at set time, thereby preventing oversized ring allocations. No additional mitigation is required once the patch is applied.

Description

A vulnerability in the Linux kernel allowed unprivileged users to set an excessively large tx_queue_len value, leading to oversized ring buffer allocations and potential global memory exhaustion. This issue affected several subsystems that allocate ring buffers based on tx_queue_len without an upper bound. The vulnerability has been fixed by capping tx_queue_len at S16_MAX (32767), rejecting oversized values at set time across all relevant interfaces.

References

Community reviews

Loading reviews…