Vulnerability · Published Jun 25, 2026 · Assigned by Linux

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

Critical 9.8

In plain English

A critical-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 24% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)9.8Critical
Exploit odds (30 days)0.3%top 75.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.0.13-1DEBIAN-CVE-2026-53175
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux7.0.0-29.29UBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux7.0.0-29.29USN-8629-1
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-53175
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-aws7.0.0-1010.10USN-8629-1
Ubuntu:26.04:LTSlinux-aws7.0.0-1010.10UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1010.10~24.04.1USN-8629-2
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1010.10~24.04.1UBUNTU-CVE-2026-53175
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-azure7.0.0-1011.11USN-8629-1
Ubuntu:26.04:LTSlinux-azure7.0.0-1011.11UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-53175
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1010.10USN-8629-1
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1010.10UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-53175
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-gcp7.0.0-1010.10USN-8660-1
Ubuntu:26.04:LTSlinux-gcp7.0.0-1010.10UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-gke7.0.0-1005.6USN-8660-1
Ubuntu:26.04:LTSlinux-gke7.0.0-1005.6UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-29.29~24.04.2UBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-29.29~24.04.2USN-8629-3
Ubuntu:26.04:LTSlinux-ibm7.0.0-1011.11USN-8629-1
Ubuntu:26.04:LTSlinux-ibm7.0.0-1011.11UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1016.16UBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1032.32USN-8748-1
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1032.32UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2016.16UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1033.33UBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1033.33USN-8911-1
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1010.10UBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1010.10USN-8637-1
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-oracle7.0.0-1009.9USN-8629-1
Ubuntu:26.04:LTSlinux-oracle7.0.0-1009.9UBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-53175
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-raspi7.0.0-1016.16USN-8629-1
Ubuntu:26.04:LTSlinux-raspi7.0.0-1016.16UBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-53175
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-realtime7.0.0-29.29.1USN-8629-1
Ubuntu:26.04:LTSlinux-realtime7.0.0-29.29.1UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-53175
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-53175
Ubuntu:26.04:LTSlinux-riscv7.0.0-29.29.1UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-53175
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-30.30.1~24.04.1UBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-53175
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-53175

Affected products (as reported)

VendorProductVersions
Linux Linux 22ee4010866da81aeee08e1ea3fddbe418feb212 – before 0e823ca0e7391630784ae7dd0981b7ad170a93d9543555954b1ee8d1903a7020324efb41b0c97428 – before c22599cc90e1cd5f8129c8670bd68a02ff7177b4c70df25214ac9b32b53e18e6ae3b8f073ffa6903 – before 89b909e9704587bfecc1aab1d37e98faee03b9f9006a5035b495dec008805df249f92c22c89c3d2e – before 010c3313a4d178dc2d3ce958d2e5cb055e2864c1006a5035b495dec008805df249f92c22c89c3d2e – before 32594b09854970d7ba83eb2dc8c69a2edd158c8e6.12.93 – before 6.12.946.18.3 – before 6.18.36
Linux Linux 6.19

Weakness: CWE-825 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References