Kernel hang via recursive MPTCP data locking
Published Sep 25, 2026 · Updated Sep 25, 2026
Improper locking in Linux MPTCP allows attackers to hang kernel networking when exceptional receive errors reset a subflow. The receive path can reenter mptcp_data_ready through subflow_state_change and reacquire the MPTCP data lock that it already holds, creating a deadlock; reset processing can also revisit an skb after freeing it. Triggering the condition requires an MPTCP subflow reset during the rare error path, and the documented consequence is stalled receive processing rather than data disclosure or modification.
Summary
What happened
Improper locking in Linux MPTCP allows attackers to hang kernel networking when exceptional receive errors reset a subflow. The receive path can reenter mptcp_data_ready through subflow_state_change and reacquire the MPTCP data lock that it already holds, creating a deadlock; reset processing can also revisit an skb after freeing it. Triggering the condition requires an MPTCP subflow reset during the rare error path, and the documented consequence is stalled receive processing rather than data disclosure or modification.
The record
- CVE
- CVE-2026-97524
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12c1676d598e3b8dd92a033b623b792cc2ea1ec5
- Affected versionversion=35668f8ec84f6c944676e48ecc6bbc5fc8e6fe25
- Affected versionversion=5.10.228 <5.11
- Affected versionversion=5.15.169 <5.16
- Affected versionversion=6.1.113 <6.2
- Affected versionversion=6.11.4 <6.12
- Affected versionversion=6.12
- Affected versionversion=6.6.57 <6.7
- Affected versionversion=8bfd391bde685df7289b928ce8876a3583be4bfb
- Affected versionversion=b8be15d1ae7ea4eedd547c3b3141f592fbddcd30
- Affected versionversion=e32d262c89e2b22cb0640223f953b548617ed8a6 <2b0f561f21b27c40c91ea4975268a06092bd7e9c
- Affected versionversion=e32d262c89e2b22cb0640223f953b548617ed8a6 <4b7abdcb5ba832fafab679f0d998af39cbc99307
- Affected versionversion=e32d262c89e2b22cb0640223f953b548617ed8a6 <b2dbcc1ed48b5ac070a41db4a52aade6823c4df0
- Affected versionversion=e32d262c89e2b22cb0640223f953b548617ed8a6 <ce7e4ede01ed3e47a48c0f1ce1d87bf4864bee9f
- Affected versionversion=fde99e972b8f88cebe619241d7aa43d288ef666a
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started