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 fqdirpreexit() flush
On netns teardown, fqdirpreexit() walks the fqdir rhashtable and flushes every fragment queue that is not yet complete using inetfragqueueflush(). That helper frees all the skbs queued on the fragment queue but does not set INETFRAGCOMPLETE, and leaves q->fragmentstail and q->lastrunhead pointing at the freed skbs. The queue itself stays in the rhashtable.
fqdirpreexit() first lowers highthresh to 0 to stop new queue lookups, but it cannot stop a fragment that already obtained the queue through inetfragfind() earlier and stalled just before taking the queue lock. Once that fragment resumes after the flush and takes the queue lock, it passes the INETFRAGCOMPLETE check and then dereferences the freed fragmentstail. inetfragqueueinsert() reads FRAGCB() and ->len of that pointer and, on the append path, writes ->nextfrag, causing a slab use-after-free. IPv6, nfconntrackreasm6 and 6lowpan reassembly share the same flush path and are affected as well.
Reset rbfragments, fragmentstail and lastrunhead in inetfragqueueflush() 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 fragmentstail. ipfragreinit() already performed this reset after its own flush, so drop the now duplicate code there.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Fixed in 6lowpan reassembly
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53175?
CVE-2026-53175 has a risk score of 47, indicating a moderate level of severity.
How do I fix CVE-2026-53175?
Fixing CVE-2026-53175 involves updating the Linux kernel to the latest patched version that addresses this use-after-free vulnerability.
What types of systems are affected by CVE-2026-53175?
CVE-2026-53175 affects systems running certain versions of the Linux kernel that are utilizing the inet fragment handling mechanism.
Can CVE-2026-53175 be exploited remotely?
Yes, CVE-2026-53175 can potentially be exploited remotely if an attacker can manipulate network traffic to trigger the vulnerability.
What is the primary cause of CVE-2026-53175?
The primary cause of CVE-2026-53175 is a use-after-free error related to the fqdir_pre_exit() function during network namespace teardown.