CVE-2025-21972: net: mctp: unshare packets when reassembling
In the Linux kernel, the following vulnerability has been resolved:
net: mctp: unshare packets when reassembling
Ensure that the frag_list used for reassembly isn't shared with other
packets. This avoids incorrect reassembly when packets are cloned, and
prevents a memory leak due to circular references between fragments and
their skb_shared_info.
The upcoming MCTP-over-USB driver uses skb_clone which can trigger the
problem - other MCTP drivers don't share SKBs.
A kunit test is added to reproduce the issue.
Security readout for executives and security teams
Plain-English summary
A Linux MCTP packet-reassembly flaw can corrupt reassembled traffic and leak kernel memory when packet fragments are cloned. The supplied record rates it high at CVSS 8.8, but the vulnerable condition appears limited: existing MCTP drivers reportedly do not share these packet buffers.
Executive priority
Prioritize systems actively using MCTP or evaluating MCTP-over-USB. For ordinary Linux systems without MCTP exposure, urgency is lower despite the high CVSS score. Require owners to confirm applicability and vendor-fixed versions rather than assuming every listed Linux release is equally exposed.
Technical view
MCTP reassembly could attach a shared frag_list to another packet. With cloned SKBs, fragments could be reassembled incorrectly and circular references involving skb_shared_info could retain memory. The kernel fix unshares packets during reassembly and adds a KUnit regression test.
Likely exposure
Exposure requires Linux MCTP use plus a driver or processing path that clones SKBs. The source specifically identifies the upcoming MCTP-over-USB driver as capable of triggering the issue and says other MCTP drivers do not share SKBs. Confirm distribution-specific version status because the supplied version mapping is ambiguous.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. No public exploit evidence is provided. The adjacent-network CVSS vector suggests an attacker would need access to the relevant MCTP communication path; exact practical impact remains insufficiently documented.
Researcher notes
The record attributes confidentiality, integrity, and availability impact, but its narrative directly documents incorrect reassembly and a memory leak only. It provides no CWE, exploit primitive, or demonstrated code-execution path. Treat broader impact claims as CVSS-based until additional technical evidence emerges.
Mitigation direction
Apply the appropriate stable Linux kernel update containing the referenced reassembly fix.
Confirm fixed package versions with the operating-system or appliance vendor.
Restrict untrusted access to MCTP communication paths until remediation is complete.
Review MCTP-over-USB adoption before enabling affected or experimental drivers.
Validation and detection
Inventory Linux systems and appliances that enable or use MCTP.
Identify kernel versions and map them against vendor security advisories.
Determine whether any MCTP path clones SKBs, particularly MCTP-over-USB implementations.
Verify the deployed kernel includes the referenced unsharing fix.
Run vendor-provided regression testing, including the added KUnit test where appropriate.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21972 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.