CVE-2026-53175: inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush
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.
Security readout for executives and security teams
Plain-English summary
A race in Linux network-fragment cleanup can leave kernel pointers referencing freed packet buffers. If fragment processing resumes during network-namespace teardown, the kernel may read or write freed memory. The supplied CVSS rates potential confidentiality, integrity, and availability impact as critical, but the bundle does not establish real-world exploitation.
Executive priority
Treat this as urgent for systems running vendor-confirmed affected kernels, especially where network namespaces are routinely torn down. Patch on an accelerated cycle after compatibility testing. Do not characterize it as an active exploitation emergency: the bundle provides no such evidence, and exact distribution package status requires vendor confirmation.
Technical view
During network-namespace teardown, fqdir_pre_exit() flushes fragment queues without marking them complete or clearing pointers to freed skbs. A fragment that previously found the queue can resume, pass the completion check, and dereference fragments_tail, causing a slab use-after-free. IPv4, IPv6, nf_conntrack_reasm6, and 6LoWPAN share the affected path.
Likely exposure
Exposure concerns kernels identified as affected where fragment reassembly can overlap network-namespace teardown. The bundle lists 6.19, 6.12.94, 6.18.36, 7.0.13, 7.1, and an ambiguous "0" entry. Confirm distribution backports and package status; do not infer safety from version numbers alone.
Exploitation context
The supplied record states KEV is false, and no cited material reports active exploitation or a public exploit. The CVSS vector describes network-reachable, low-complexity, unauthenticated impact, but the bundle does not demonstrate reliable triggering or security impact in practice.
Researcher notes
The fix resets rb_fragments, fragments_tail, and last_run_head after freeing queued skbs. This prevents a previously found queue from retaining stale pointers when processing resumes. The affected-version metadata is unusual and includes an ambiguous "0" entry, so researchers should validate branch-specific commits and distribution backports rather than extrapolating version ranges.
Mitigation direction
Update to a vendor-supported kernel containing the linked fragment-queue flush fix or an equivalent distribution backport.
Check your Linux distributor’s CVE guidance for exact fixed packages and restart requirements.
Prioritize vendor-confirmed affected systems where network namespaces are frequently created or destroyed.
If patching is delayed, request vendor-supported mitigations; none are specified in the supplied sources.
Validation and detection
Inventory running kernel versions and distribution package release identifiers across potentially exposed systems.
Compare each package against the distributor’s CVE status, accounting for backported fixes.
Verify the installed package contains a linked fix commit or an equivalent backport.
After updating and restarting as directed, confirm systems run the intended fixed kernel package.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-825: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
1ADP providers
9Source links
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-825 · source CWE mapping
Expired Pointer Dereference
Expired Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.