CVE - CVE-2025-23145

CVE-ID
CVE-2025-23145	Learn more at National Vulnerability Database (NVD) • CVSS Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings • CPE Information
Description
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.
References
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
MISC:https://git.kernel.org/stable/c/443041deb5ef6a1289a99ed95015ec7442f141dc URL:https://git.kernel.org/stable/c/443041deb5ef6a1289a99ed95015ec7442f141dc MISC:https://git.kernel.org/stable/c/4b2649b9717678aeb097893cc49f59311a1ecab0 URL:https://git.kernel.org/stable/c/4b2649b9717678aeb097893cc49f59311a1ecab0 MISC:https://git.kernel.org/stable/c/7f9ae060ed64aef8f174c5f1ea513825b1be9af1 URL:https://git.kernel.org/stable/c/7f9ae060ed64aef8f174c5f1ea513825b1be9af1 MISC:https://git.kernel.org/stable/c/855bf0aacd51fced11ea9aa0d5101ee0febaeadb URL:https://git.kernel.org/stable/c/855bf0aacd51fced11ea9aa0d5101ee0febaeadb MISC:https://git.kernel.org/stable/c/8cf7fef1bb2ffea7792bcbf71ca00216cecc725d URL:https://git.kernel.org/stable/c/8cf7fef1bb2ffea7792bcbf71ca00216cecc725d MISC:https://git.kernel.org/stable/c/b3088bd2a6790c8efff139d86d7a9d0b1305977b URL:https://git.kernel.org/stable/c/b3088bd2a6790c8efff139d86d7a9d0b1305977b MISC:https://git.kernel.org/stable/c/dc81e41a307df523072186b241fa8244fecd7803 URL:https://git.kernel.org/stable/c/dc81e41a307df523072186b241fa8244fecd7803 MISC:https://git.kernel.org/stable/c/efd58a8dd9e7a709a90ee486a4247c923d27296f URL:https://git.kernel.org/stable/c/efd58a8dd9e7a709a90ee486a4247c923d27296f
Assigning CNA
kernel.org
Date Record Created
20250111	Disclaimer: The record creation date may reflect when the CVE ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20250111)
Votes (Legacy)

Comments (Legacy)

Proposed (Legacy)
N/A
This is an record on the CVE List, which provides common identifiers for publicly known cybersecurity vulnerabilities.
Search CVE Using Keywords: You can also search by reference using the CVE Reference Maps.
For More Information: CVE Request Web Form (select "Other" from dropdown)