Back to CVE records
Critical 9.8Published Jun 25, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects Linux and 2 other products. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-825
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Modified
Record last updated
Sep 1, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
22ee4010866da81aeee08e1ea3fddbe418feb212 builds before 0e823ca0e7391630784ae7dd0981b7ad170a93d9; from 543555954b1ee8d1903a7020324efb41b0c97428 before c22599cc90e1cd5f8129c8670bd68a02ff7177b4; from c70df25214ac9b32b53e18e6ae3b8f073ffa6903 before 89b909e9704587bfecc1aab1d37e98faee03b9f9; from 006a5035b495dec008805df249f92c22c89c3d2e before 010c3313a4d178dc2d3ce958d2e5cb055e2864c1; from 006a5035b495dec008805df249f92c22c89c3d2e before 32594b09854970d7ba83eb2dc8c69a2edd158c8e; from 6.12.93 before 6.12.94; from 6.18.3 before 6.18.36
CNA record
10
CISA ADP
linux linux_kernel
linux:linux_kernel
from 6.18.3 before 6.18.36; from 6.19.1 before 7.0.13; 6.12.93; 6.19; 6.19; 6.19; 6.19; 6.19; and 10 more ranges
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.