Vulnerability · Published Jan 14, 2026 · Assigned by Linux
CVE-2025-71144mptcp: ensure context reset on disconnect()
Medium 5.5
In plain English
A medium-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.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: mptcp: ensure context reset on disconnect() After the blamed commit below, if the MPC subflow is already in TCP_CLOSE status or has fallback to TCP at mptcp_disconnect() time, mptcp_do_fastclose() skips setting the `send_fastclose flag` and the later __mptcp_close_ssk() does not reset anymore the related subflow context. Any later connection will be created with both the `request_mptcp` flag and the msk-level fallback status off (it is unconditionally cleared at MPTCP disconnect time), leading to a warning in subflow_data_ready(): WARNING: CPU: 26 PID: 8996 at net/mptcp/subflow.c:1519 subflow_data_ready (net/mptcp/subflow.c:1519 (discriminator 13)) Modules linked in: CPU: 26 UID: 0 PID: 8996 Comm: syz.22.39 Not tainted 6.18.0-rc7-05427-g11fc074f6c36 #1 PREEMPT(voluntary) Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 RIP: 0010:subflow_data_ready (net/mptcp/subflow.c:1519 (discriminator 13)) Code: 90 0f 0b 90 90 e9 04 fe ff ff e8 b7 1e f5 fe 89 ee bf 07 00 00 00 e8 db 19 f5 fe 83 fd 07 0f 84 35 ff ff ff e8 9d 1e f5 fe 90 <0f> 0b 90 e9 27 ff ff ff e8 8f 1e f5 fe 4c 89 e7 48 89 de e8 14 09 RSP: 0018:ffffc9002646fb30 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88813b218000 RCX: ffffffff825c8435 RDX: ffff8881300b3580 RSI: ffffffff825c8443 RDI: 0000000000000005 RBP: 000000000000000b R08: ffffffff825c8435 R09: 000000000000000b R10: 0000000000000005 R11: 0000000000000007 R12: ffff888131ac0000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f88330af6c0(0000) GS:ffff888a93dd2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f88330aefe8 CR3: 000000010ff59000 CR4: 0000000000350ef0 Call Trace: <TASK> tcp_data_ready (net/ipv4/tcp_input.c:5356) tcp_data_queue (net/ipv4/tcp_input.c:5445) tcp_rcv_state_process (net/ipv4/tcp_input.c:7165) tcp_v4_do_rcv (net/ipv4/tcp_ipv4.c:1955) __release_sock (include/net/sock.h:1158 (discriminator 6) net/core/sock.c:3180 (discriminator 6)) release_sock (net/core/sock.c:3737) mptcp_sendmsg (net/mptcp/protocol.c:1763 net/mptcp/protocol.c:1857) inet_sendmsg (net/ipv4/af_inet.c:853 (discriminator 7)) __sys_sendto (net/socket.c:727 (discriminator 15) net/socket.c:742 (discriminator 15) net/socket.c:2244 (discriminator 15)) __x64_sys_sendto (net/socket.c:2247) do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) RIP: 0033:0x7f883326702d Address the issue setting an explicit `fastclosing` flag at fastclose time, and checking such flag after mptcp_do_fastclose().
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.164-1 | DSA-6163-1 |
| Debian:12 | linux | 6.1.164-1 | DEBIAN-CVE-2025-71144 |
| Debian:13 | linux | 6.12.69-1 | DEBIAN-CVE-2025-71144 |
| Debian:14 | linux | 6.18.5-1 | DEBIAN-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux | 6.8.0-110.110 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux | 6.17.0-29.29 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux | 6.17.0-29.29 | USN-8277-1 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1052.55 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1015.15 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1015.15 | USN-8277-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1017.17~24.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1017.17~24.04.1 | USN-8374-1 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1052.55~22.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1054.60 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1015.15 | USN-8310-1 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1015.15 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1015.15~24.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1015.15~24.04.1 | USN-8310-1 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1059.65~22.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1054.57 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1018.19 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1018.19 | USN-8374-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1018.19~24.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1018.19~24.04.1 | USN-8374-1 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1054.57~22.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1050.56 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1037.40 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-29.29~24.04.1 | USN-8277-1 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-29.29~24.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-110.110~22.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1051.51 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1051.51~22.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-110.110.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-110.110.1~22.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1051.54 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1026.26 | USN-8508-1 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1026.26 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1051.54~22.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1051.54.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1022.22 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1023.23 | USN-8277-1 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1023.23 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1049.50 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1014.14 | USN-8277-1 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1014.14 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1014.14~24.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1014.14~24.04.1 | USN-8277-2 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1049.50~22.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1052.56 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1017.17 | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1017.17 | USN-8277-1 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1013.15 | USN-8277-1 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1013.15 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-29.29.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | 6.17.0-29.29.1~24.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-110.110~22.04.1 | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-71144 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-71144 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9ea05fabce31ff93a0adae8221c58bc6d7b832f3 – before 226fff52e7ed9fc8cd63327133739b3d92537ffd3a13454fd098ed51e733958488f8ec62859a9ed8 – before 5c7c7135468f3fc6379cde9777a2c18bfe92d82ff6fb2cbc91a81178dea23d463503b4525a76825d – before 1c7c3a9314d8a7fc0e9a508606466a967c8e774aae155060247be8dcae3802a95bd1bdf93ab3215d – before f1a77dfc3b045c3dd5f6e64189b9f52b90399f07ae155060247be8dcae3802a95bd1bdf93ab3215d – before 86730ac255b0497a272704de9a1df559f5d6602ec4f7b0916b95fd2226e5ab98882482b08f52e1c06.1.159 – before 6.1.1646.6.119 – before 6.6.120 |
| Linux | Linux | 6.18 |
References
- https://git.kernel.org/stable/c/226fff52e7ed9fc8cd63327133739b3d92537ffd
- https://git.kernel.org/stable/c/5c7c7135468f3fc6379cde9777a2c18bfe92d82f
- https://git.kernel.org/stable/c/1c7c3a9314d8a7fc0e9a508606466a967c8e774a
- https://git.kernel.org/stable/c/f1a77dfc3b045c3dd5f6e64189b9f52b90399f07
- https://git.kernel.org/stable/c/86730ac255b0497a272704de9a1df559f5d6602e