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

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

inet: frags: limit the truesize of a reassembly queue

The truesize of fragments in a reassembly queue is only bounded by the per netns ipfraghighthresh sysctl, which has no upper limit.

inetfragreasmfinish() sums the truesize of all fragments in an int. If this sum reaches 2^32, it wraps, and the final skwmemalloc adjustment of the socket owning the reassembled skb can cancel its own reference, leading to a use-after-free of this socket.

This can be triggered from an unprivileged user/network namespace, raising ipfraghighthresh and using padded TUN packets, which keep a large truesize after being trimmed by iprcvcore().

Track the sum of the truesize of fragments in each queue, and refuse a fragment that would make it bigger than INTMAX / 2. Callers kill the queue on this error. This bound is far above the needs of legitimate traffic.

Affected Software

7 affected componentsFixes available
linux/kernel>=5.4.285<5.5
5.5
linux/kernel>=5.10.227<5.11
5.11
linux/kernel>=5.15.168<5.16
5.16
linux/kernel>=6.1.85<6.2
6.2
linux/kernel>=6.6.26<6.7
6.7
linux/kernel>=6.8.5<6.9
6.9
linux/kernel>=6.9.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.5
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.11
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.16
  4. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.2
  5. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.7
  6. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.9
  7. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  8. Compensating control

    Track the total truesize of fragments in each reassembly queue and refuse any fragment that would make the total exceed INT_MAX / 2.

Frequently Asked Questions

1

Who can trigger this issue?

An unprivileged user in a user or network namespace can trigger it by raising the per-network-namespace ipfrag_high_thresh setting and sending padded TUN packets.

2

What conditions are needed for exploitation?

The attacker needs to create a fragment reassembly queue whose cumulative truesize reaches 2^32, causing an integer wrap during reassembly. Padded TUN packets are used because their truesize can remain large after trimming by ip_rcv_core().

3

What happens when the vulnerable condition is reached?

The wrapped truesize sum can cause the final sk_wmem_alloc adjustment to cancel the reference to the socket that owns the reassembled skb. This can result in a use-after-free of that socket.

4

How does the fix mitigate the problem?

The fix tracks cumulative fragment truesize for each reassembly queue and rejects a fragment that would raise it above INT_MAX / 2. When this occurs, callers destroy the affected reassembly queue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203