CVE-2025-71088
BaseFortify
Publication date: 2026-01-13
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.2 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.4 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.2.1 (inc) to 6.6.120 (exc) |
| linux | linux_kernel | From 6.1.110 (inc) to 6.1.160 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.65 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's Multipath TCP (MPTCP) implementation. Specifically, it involves a simult-connect race that leads to an inconsistent fallback status. The issue occurs because the TCP subflow can process a simult-connect SYN-ACK packet after transitioning to the TCP_FIN1 state, bypassing the MPTCP fallback check. This happens because the sk_state_change() callback is not invoked for transitions from any state to FIN_WAIT1. As a result, the socket moves to an inconsistent status, causing the next incoming data to trigger a kernel error (splat). The fix involves moving the simult-fallback check to the earliest possible stage, at SYN-ACK generation time, to close the race condition.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to enter an inconsistent state when handling Multipath TCP connections, potentially leading to kernel crashes or instability (kernel splats). This can disrupt network connectivity and affect system reliability, especially on systems using MPTCP for network communication.
What immediate steps should I take to mitigate this vulnerability?
Apply the available Linux kernel patches that fix the simult-connect race condition in the mptcp subflow handling. Specifically, update the kernel to include the fixes that move the simult-fallback check to the earliest possible stage (syn-ack generation time) to prevent inconsistent socket states. Ensure your kernel version includes the backported commits referenced in the fix tags.