Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.8

CVE-2026-53175: Linux Kernel IPv4 Fragment Queue Use-After-Free Fix

CVE-2026-53175 CVE-2026-53175
Summary

A fix has been made to the Linux kernel to prevent a use-after-free error in IPv4 fragment queues when the network namespace is being torn down. This error could potentially cause a crash or other issues. The issue is now resolved, but it's still a good idea to apply the latest kernel updates to ensure you have the latest security patches.

What to do

No fix is available yet. Check with your software vendor for updates.

Affected software
VendorProductAffected versions
linux linux_kernel >= 6.18.3, < 6.18.36
>= 6.19.1, < 7.0.13
6.12.93
6.19
7.1
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux < 0e823ca0e7391630784ae7dd0981b7ad170a93d9
6.19
Original title
In the Linux kernel, the following vulnerability has been resolved: inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush On netns teardown, fqdir_pre_exit() walks the fqdir rhasht...
Original description
In the Linux kernel, the following vulnerability has been resolved:

inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush

On netns teardown, fqdir_pre_exit() walks the fqdir rhashtable and
flushes every fragment queue that is not yet complete using
inet_frag_queue_flush(). That helper frees all the skbs queued on the
fragment queue but does not set INET_FRAG_COMPLETE, and leaves
q->fragments_tail and q->last_run_head pointing at the freed skbs.
The queue itself stays in the rhashtable.

fqdir_pre_exit() first lowers high_thresh to 0 to stop new queue lookups,
but it cannot stop a fragment that already obtained the queue through
inet_frag_find() earlier and stalled just before taking the queue lock.
Once that fragment resumes after the flush and takes the queue lock,
it passes the INET_FRAG_COMPLETE check and then dereferences the freed
fragments_tail. inet_frag_queue_insert() reads FRAG_CB() and ->len of
that pointer and, on the append path, writes ->next_frag, causing a
slab use-after-free. IPv6, nf_conntrack_reasm6 and 6lowpan reassembly
share the same flush path and are affected as well.

Reset rb_fragments, fragments_tail and last_run_head in
inet_frag_queue_flush() so a flushed queue no longer points at the
freed skbs. A fragment that resumes after the flush and takes the
queue lock then finds an empty queue and starts a new run instead of
dereferencing the freed fragments_tail. ip_frag_reinit() already
performed this reset after its own flush, so drop the now duplicate
code there.
Vulnerability type
CWE-416 Use After Free
Published: 25 Jun 2026 · Updated: 23 Jul 2026 · First seen: 25 Jun 2026