Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-23145mptcp: fix NULL pointer in can_accept_new_subflow

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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 18 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-23145, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.59% · top 51% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 9466a1ccebbe54ac57fb8a89c2b4b854826546a8 – < 8cf7fef1bb2ffea7792bcbf71ca00216cecc725d
    • affected 9466a1ccebbe54ac57fb8a89c2b4b854826546a8 – < b3088bd2a6790c8efff139d86d7a9d0b1305977b
    • affected 9466a1ccebbe54ac57fb8a89c2b4b854826546a8 – < 855bf0aacd51fced11ea9aa0d5101ee0febaeadb
    • affected 9466a1ccebbe54ac57fb8a89c2b4b854826546a8 – < 7f9ae060ed64aef8f174c5f1ea513825b1be9af1
    • affected 9466a1ccebbe54ac57fb8a89c2b4b854826546a8 – < dc81e41a307df523072186b241fa8244fecd7803
    • affected 9466a1ccebbe54ac57fb8a89c2b4b854826546a8 – < efd58a8dd9e7a709a90ee486a4247c923d27296f
    • affected 9466a1ccebbe54ac57fb8a89c2b4b854826546a8 – < 4b2649b9717678aeb097893cc49f59311a1ecab0
    • affected 9466a1ccebbe54ac57fb8a89c2b4b854826546a8 – < 443041deb5ef6a1289a99ed95015ec7442f141dc
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.237 – ≤ 5.10.*
    • unaffected 5.15.181 – ≤ 5.15.*
    • unaffected 6.1.135 – ≤ 6.1.*
    • unaffected 6.6.88 – ≤ 6.6.*
    • unaffected 6.12.24 – ≤ 6.12.*
    • unaffected 6.13.12 – ≤ 6.13.*
    • unaffected 6.14.3 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-23145 badge
[![CVE-2025-23145](https://cveledger.app/badge/CVE-2025-23145.svg)](https://cveledger.app/cve/CVE-2025-23145)

Record last updated .