CVE-2026-97524

HIGHCVSS 7.5/10EPSS 0.69%

Last modified

CVE-2026-97524 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: mptcp: avoid unneeded actions on subflow reset Once in a blue moon, the mptcp receive path can recursively call mptcp_data_ready() via state change under unlucky error conditions, and then try to hold the data lock again. Break the recursion loop explicitly checking for the exceptional condition. Add a new flag instead of using an existing one like 'closing', to exit early in subflow_state_change(), and explicitly flush the RX queue at reset time. This avoids unneeded processing to check for available data -- calling get_mapping_status() and more on a dying subflow -- but also in error reporting and worker scheduling. Note that we must consume the currently peeked skb before invoking mptcp_dss_corruption to avoid consuming it again after the eventual reset has freed it.. EPSS estimates a 0.69% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: mptcp: avoid unneeded actions on subflow reset Once in a blue moon, the mptcp receive path can recursively call mptcp_data_ready() via state change under unlucky error conditions, and then try to hold the data lock again. Break the recursion loop explicitly checking for the exceptional condition. Add a new flag instead of using an existing one like 'closing', to exit early in subflow_state_change(), and explicitly flush the RX queue at reset time. This avoids unneeded processing to check for available data -- calling get_mapping_status() and more on a dying subflow -- but also in error reporting and worker scheduling. Note that we must consume the currently peeked skb before invoking mptcp_dss_corruption to avoid consuming it again after the eventual reset has freed it.

Metrics

EPSS Probability
0.69%

51.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= fde99e972b8f88cebe619241d7aa43d288ef666a, < 6d669c740933124eae3df8cfc15995af9bcc6aba; >= 12c1676d598e3b8dd92a033b623b792cc2ea1ec5, < 83a7dcdd2b1060484528da70a643125174d47e5a; >= 35668f8ec84f6c944676e48ecc6bbc5fc8e6fe25, < a370e56024df0b07e3120c45a9773ae123819fd6; >= b8be15d1ae7ea4eedd547c3b3141f592fbddcd30, < 1962841387087970d75ba8b8d4c2aa2d45705e50; >= e32d262c89e2b22cb0640223f953b548617ed8a6, < 4b7abdcb5ba832fafab679f0d998af39cbc99307; >= e32d262c89e2b22cb0640223f953b548617ed8a6, < b2dbcc1ed48b5ac070a41db4a52aade6823c4df0; >= e32d262c89e2b22cb0640223f953b548617ed8a6, < ce7e4ede01ed3e47a48c0f1ce1d87bf4864bee9f; >= e32d262c89e2b22cb0640223f953b548617ed8a6, < 2b0f561f21b27c40c91ea4975268a06092bd7e9c; 8bfd391bde685df7289b928ce8876a3583be4bfb; >= 5.10.228, < 5.10.271; >= 5.15.169, < 5.15.222; >= 6.1.113, < 6.1.189; >= 6.6.57, < 6.6.158; >= 6.11.4, < 6.12
LinuxLinux6.12

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97524?
In the Linux kernel, the following vulnerability has been resolved: mptcp: avoid unneeded actions on subflow reset Once in a blue moon, the mptcp receive path can recursively call mptcp_data_ready() via state change under unlucky error conditions, and then try to hold the data lock again. Break the recursion loop explicitly checking for the exceptional condition. Add a new flag instead of using an existing one like 'closing', to exit early in subflow_state_change(), and explicitly flush the RX queue at reset time. This avoids unneeded processing to check for available data -- calling get_mapping_status() and more on a dying subflow -- but also in error reporting and worker scheduling. Note that we must consume the currently peeked skb before invoking mptcp_dss_corruption to avoid consuming it again after the eventual reset has freed it.
How severe is CVE-2026-97524?
CVE-2026-97524 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 0.69% probability of exploitation in the next 30 days.
How do I fix CVE-2026-97524?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-97524?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST