Answer in brief
CVE-2025-23145 records a High severity (CVSS 7.5) vulnerability in mptcp: fix NULL pointer in can_accept_new_subflow. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9466a1ccebbe54ac57fb8a89c2b4b854826546a8 <8cf7fef1bb2ffea7792bcbf71ca00216cecc725d || >=9466a1ccebbe54ac57fb8a89c2b4b854826546a8 <b3088bd2a6790c8efff139d86d7a9d0b1305977b || >=9466a1ccebbe54ac57fb8a89c2b4b854826546a8 <855bf0aacd51fced11ea9aa0d5101ee0febaeadb || >=9466a1ccebbe54ac57fb8a89c2b4b854826546a8 <7f9ae060ed64aef8f174c5f1ea513825b1be9af1 || >=9466a1ccebbe54ac57fb8a89c2b4b854826546a8 <dc81e41a307df523072186b241fa8244fecd7803 || >=9466a1ccebbe54ac57fb8a89c2b4b854826546a8 <efd58a8dd9e7a709a90ee486a4247c923d27296f || >=9466a1ccebbe54ac57fb8a89c2b4b854826546a8 <4b2649b9717678aeb097893cc49f59311a1ecab0 || >=9466a1ccebbe54ac57fb8a89c2b4b854826546a8 <443041deb5ef6a1289a99ed95015ec7442f141dc | 8cf7fef1bb2ffea7792bcbf71ca00216cecc725d, b3088bd2a6790c8efff139d86d7a9d0b1305977b, 855bf0aacd51fced11ea9aa0d5101ee0febaeadb, 7f9ae060ed64aef8f174c5f1ea513825b1be9af1, dc81e41a307df523072186b241fa8244fecd7803, efd58a8dd9e7a709a90ee486a4247c923d27296f, 4b2649b9717678aeb097893cc49f59311a1ecab0, 443041deb5ef6a1289a99ed95015ec7442f141dc |
| Linux/Linuxgeneric | 5.9 | Not reported |
Published upstream
May 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: mptcp: fix NULL pointer in can_accept_new_subflow When testing valkey benchmark tool with MPTCP, the kernel panics in 'mptcp_can_accept_new_subflow' because subflow_req->msk is NULL. Call trace: mptcp_can_accept_new_subflow (./net/mptcp/subflow.c:63 (discriminator 4)) (P) subflow_syn_recv_sock (./net/mptcp/subflow.c:854) tcp_check_req (./net/ipv4/tcp_minisocks.c:863) tcp_v4_rcv (./net/ipv4/tcp_ipv4.c:2268) ip_protocol_deliver_rcu (./net/ipv4/ip_input.c:207) ip_local_deliver_finish (./net/ipv4/ip_input.c:234) ip_local_deliver (./net/ipv4/ip_input.c:254) ip_rcv_finish (./net/ipv4/ip_input.c:449) ... According to the debug log, the same req received two SYN-ACK in a very short time, very likely because the client retransmits the syn ack due to multiple reasons. Even if the packets are transmitted with a relevant time interval, they can be processed by the server on different CPUs concurrently). The 'subflow_req->msk' ownership is transferred to the subflow the first, and there will be a risk of a null pointer dereference here. This patch fixes this issue by moving the 'subflow_req->msk' under the `own_req == true` conditional. Note that the !msk check in subflow_hmac_valid() can be dropped, because the same check already exists under the own_req mpj branch where the code has been moved to.
Quoted source text, attributed separately from HOL analysis.