Vulnerability · Published Jun 25, 2026 · Assigned by Linux

CVE-2026-53260tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req().

Critical 9.8

In plain English

A critical-severity race condition 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 22% 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 77.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req(). syzbot reported a weird reqsk->rsk_refcnt underflow in __inet_csk_reqsk_queue_drop(). The captured reqsk_put() in __inet_csk_reqsk_queue_drop() is called only when it successfully removes reqsk from ehash. Moreover, reqsk_timer_handler() calls another reqsk_put() after that. This indicates that the reqsk was missing both refcnts for ehash and the timer itself. Since all the syzbot reports had PREEMPT_RT enabled, the only possible scenario is that reqsk_queue_hash_req() is preempted after mod_timer() and before refcount_set(), and then the timer triggered after 1s aborts the reqsk due to its listener's close(). Let's wrap mod_timer() and refcount_set() with preempt_disable_nested() and preempt_enable_nested(). Note that inet_ehash_insert() holds the normal spin_lock() (mutex in PREEMPT_RT), so it must be called outside of preempt_disable_nested(), but this is fine. The lookup path just ignores 0 sk_refcnt entries in ehash and tries to create another reqsk, but this will fail at inet_ehash_insert(). [0]: refcount_t: underflow; use-after-free. WARNING: lib/refcount.c:28 at refcount_warn_saturate+0xb2/0x110 lib/refcount.c:28, CPU#0: ktimers/0/16 Modules linked in: CPU: 0 UID: 0 PID: 16 Comm: ktimers/0 Tainted: G L syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:refcount_warn_saturate+0xb2/0x110 lib/refcount.c:28 Code: e4 7d d1 0a 67 48 0f b9 3a eb 4a e8 38 3d 23 fd 48 8d 3d e1 7d d1 0a 67 48 0f b9 3a eb 37 e8 25 3d 23 fd 48 8d 3d de 7d d1 0a <67> 48 0f b9 3a eb 24 e8 12 3d 23 fd 48 8d 3d db 7d d1 0a 67 48 0f RSP: 0000:ffffc90000157948 EFLAGS: 00010246 RAX: ffffffff84a1301b RBX: 0000000000000003 RCX: ffff88801ca98000 RDX: 0000000000000100 RSI: 0000000000000000 RDI: ffffffff8f72ae00 RBP: ffffffff99ae3b01 R08: ffff88801ca98000 R09: 0000000000000005 R10: 0000000000000100 R11: 0000000000000004 R12: ffff8880425ef568 R13: ffff8880425ef4f8 R14: ffff8880425ef578 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff888126386000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7b46710e9c CR3: 000000000dbb6000 CR4: 00000000003526f0 Call Trace: <TASK> __refcount_sub_and_test include/linux/refcount.h:400 [inline] __refcount_dec_and_test include/linux/refcount.h:432 [inline] refcount_dec_and_test include/linux/refcount.h:450 [inline] reqsk_put include/net/request_sock.h:136 [inline] __inet_csk_reqsk_queue_drop+0x3ce/0x440 net/ipv4/inet_connection_sock.c:1007 reqsk_timer_handler+0x651/0xdf0 net/ipv4/inet_connection_sock.c:1137 call_timer_fn+0x192/0x5e0 kernel/time/timer.c:1748 expire_timers kernel/time/timer.c:1799 [inline] __run_timers kernel/time/timer.c:2374 [inline] __run_timer_base+0x6a3/0x9f0 kernel/time/timer.c:2386 run_timer_base kernel/time/timer.c:2395 [inline] run_timer_softirq+0x67/0x170 kernel/time/timer.c:2403 handle_softirqs+0x1de/0x6d0 kernel/softirq.c:622 __do_softirq kernel/softirq.c:656 [inline] run_ktimerd+0x69/0x100 kernel/softirq.c:1151 smpboot_thread_fn+0x541/0xa50 kernel/smpboot.c:160 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK>

Affected packages & fixed versions

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

Affected products (as reported)

VendorProductVersions
Linux Linux d2d6422f8bd17c6bb205133e290625a564194496 – before 889fc99967007e2493833515a645cb2d800f6742d2d6422f8bd17c6bb205133e290625a564194496 – before de5a46f3b2c8d3cd20afa158bd3a725e3e3d6fd3d2d6422f8bd17c6bb205133e290625a564194496 – before b183215ff714efb747d9d5a429322ba6404b5401d2d6422f8bd17c6bb205133e290625a564194496 – before e10902df24488ca722303133acfc82490f7d59ad
Linux Linux 6.12

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

References