CVE-2025-71144: mptcp: ensure context reset on disconnect()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1c7c3a9314d8a7fc0e9a508606466a967c8e774a, 226fff52e7ed9fc8cd63327133739b3d92537ffd, 5c7c7135468f3fc6379cde9777a2c18bfe92d82f.
Low priority for now. Upgrade to Linux Linux 1c7c3a9314d8a7fc0e9a508606466a967c8e774a, 226fff52e7ed9fc8cd63327133739b3d92537ffd, 5c7c7135468f3fc6379cde9777a2c18bfe92d82f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Jan 14, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- c4f7b0916b95fd2226e5ab98882482b08f52e1c0, 6.18affected
- 9ea05fabce31ff93a0adae8221c58bc6d7b832f3 and later · before 226fff52e7ed9fc8cd63327133739b3d92537ffdaffected · git
- 3a13454fd098ed51e733958488f8ec62859a9ed8 and later · before 5c7c7135468f3fc6379cde9777a2c18bfe92d82faffected · git
- f6fb2cbc91a81178dea23d463503b4525a76825d and later · before 1c7c3a9314d8a7fc0e9a508606466a967c8e774aaffected · git
- ae155060247be8dcae3802a95bd1bdf93ab3215d and later · before f1a77dfc3b045c3dd5f6e64189b9f52b90399f07affected · git
- ae155060247be8dcae3802a95bd1bdf93ab3215d and later · before 86730ac255b0497a272704de9a1df559f5d6602eaffected · git
- 6.1.159 and later · before 6.1.164affected · semver
- 6.6.119 and later · before 6.6.120affected · semver
- 6.12.60 and later · before 6.12.65affected · semver
- 6.17.10 and later · before 6.18affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.18.1 and later · before 6.18.5
- linux linux kernel6.12.60 and later · before 6.12.65
- linux linux kernel6.17.10 and later · before 6.18
- linux linux kernel6.1.159 and later · before 6.1.164
- linux linux kernel6.18
- linux linux kernel6.19
- linux linux kernel6.6.119
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux-6.1 | before 6.1.164-1~deb11u1 | 6.1.164-1~deb11u1 |
| Debian:12 | linux | before 6.1.164-1 | 6.1.164-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.5-1 | 6.18.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-71139Jan 14, 2026 · kernel/kexec: fix IMA when allocation happens in CMA area22Monitor
- ← EarlierCVE-2025-71143Jan 14, 2026 · clk: samsung: exynos-clkout: Assign .num before accessing .hws31Monitor
- Later →CVE-2025-71104Jan 14, 2026 · KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c7c3a9314d8a7fc0e9a508606466a967c8e774a | Vendor (CNA) |
| Linux Linux | 226fff52e7ed9fc8cd63327133739b3d92537ffd | Vendor (CNA) |
| Linux Linux | 5c7c7135468f3fc6379cde9777a2c18bfe92d82f | Vendor (CNA) |
| Linux Linux | 6.1.164 | Vendor (CNA) |
| Linux Linux | 6.12.65 | Vendor (CNA) |
| Linux Linux | 6.18 | Vendor (CNA) |
| Linux Linux | 6.6.120 | Vendor (CNA) |
| Linux Linux | 86730ac255b0497a272704de9a1df559f5d6602e | Vendor (CNA) |
| Linux Linux | f1a77dfc3b045c3dd5f6e64189b9f52b90399f07 | Vendor (CNA) |
| debian:linux | 6.1.164-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.164-1~deb11u1 · Debian:11 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.