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.
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
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:14 | linux | 7.0.13-1 | DEBIAN-CVE-2026-53175 |
| Ubuntu:25.10 | linux | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux | 7.0.0-29.29 | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux | 7.0.0-29.29 | USN-8629-1 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:25.10 | linux-aws | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1010.10 | USN-8629-1 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1010.10 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | 7.0.0-1010.10~24.04.1 | USN-8629-2 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | 7.0.0-1010.10~24.04.1 | UBUNTU-CVE-2026-53175 |
| Ubuntu:25.10 | linux-azure | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1011.11 | USN-8629-1 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1011.11 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-53175 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1010.10 | USN-8629-1 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1010.10 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:25.10 | linux-gcp | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1010.10 | USN-8660-1 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1010.10 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1005.6 | USN-8660-1 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1005.6 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-29.29~24.04.2 | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-29.29~24.04.2 | USN-8629-3 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1011.11 | USN-8629-1 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1011.11 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-nvidia | 7.0.0-1016.16 | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1032.32 | USN-8748-1 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1032.32 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | 7.0.0-2016.16 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1033.33 | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1033.33 | USN-8911-1 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1010.10 | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1010.10 | USN-8637-1 |
| Ubuntu:25.10 | linux-oracle | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1009.9 | USN-8629-1 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1009.9 | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-53175 |
| Ubuntu:25.10 | linux-raspi | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1016.16 | USN-8629-1 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1016.16 | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:25.10 | linux-realtime | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-29.29.1 | USN-8629-1 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-29.29.1 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:25.10 | linux-riscv | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-29.29.1 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-30.30.1~24.04.1 | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-53175 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-53175 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| 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
- https://git.kernel.org/stable/c/0e823ca0e7391630784ae7dd0981b7ad170a93d9
- https://git.kernel.org/stable/c/c22599cc90e1cd5f8129c8670bd68a02ff7177b4
- https://git.kernel.org/stable/c/89b909e9704587bfecc1aab1d37e98faee03b9f9
- https://git.kernel.org/stable/c/010c3313a4d178dc2d3ce958d2e5cb055e2864c1
- https://git.kernel.org/stable/c/32594b09854970d7ba83eb2dc8c69a2edd158c8e
- https://access.redhat.com/security/cve/CVE-2026-53175 vdb-entry, x_refsource_REDHAT
- RHBZ#2492840 issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53175.json x_sadp-csaf-vex