Skip to main content
VulnerabilityPublished

CVE-2026-99709: Linux kernel · inet: frags: limit the truesize of a reassembly queue

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 20 Nov 2026, 06:36 UTC

Severity
High

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

Thin evidence

One scorer or none
Patch
Available – fixed in b7f84486c44c2ce03dffe5f09a42a38acbaa1551, 6.9, 6.7 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.4.285 <5.5
  • >=5.10.227 <5.11
  • >=5.15.168 <5.16
  • >=6.1.85 <6.2
  • >=6.6.26 <6.7
  • >=6.8.5 <6.9
Fixed in
  • b7f84486c44c2ce03dffe5f09a42a38acbaa1551
  • 6.9
  • 6.7
  • 6.2
  • 5.16
  • 5.11
  • 5.5
  • 3ae20e4697eb969104fe4b1e98a675f0100382b6
LinuxLinuxAffected
  • =6.9
Fixed in–

AI-suggested

This vulnerability has been fixed in Linux kernel versions 5.5, 5.11, 5.16, 6.2, 6.7, 6.9, and later. Users and administrators should upgrade to these or later kernel versions to mitigate the issue. No additional mitigation is required beyond applying the official fix.

Description

A vulnerability in the Linux kernel's fragment reassembly queue allows an unprivileged user or network namespace to trigger a use-after-free condition by exploiting an integer wraparound in the truesize sum of fragments. This occurs because the sum of fragment sizes can overflow a 32-bit integer, leading to incorrect memory management and potential socket use-after-free. The issue is fixed by limiting the total truesize of fragments in a queue to prevent overflow.

References

Community reviews

Loading reviews…