CVE-2025-21641: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
In the Linux kernel, the following vulnerability has been resolved:
mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
As mentioned in the previous commit, using the 'net' structure via
'current' is not recommended for different reasons:
- Inconsistency: getting info from the reader's/writer's netns vs only
from the opener's netns.
- current->nsproxy can be NULL in some cases, resulting in an 'Oops'
(null-ptr-deref), e.g. when the current task is exiting, as spotted by
syzbot [1] using acct(2).
The 'pernet' structure can be obtained from the table->data using
container_of().
Security readout for executives and security teams
Plain-English summary
CVE-2025-21641 is a Linux kernel flaw that can crash affected systems under local conditions. The issue is in MPTCP sysctl handling and can cause a null pointer dereference, creating an availability risk rather than data theft or tampering.
Executive priority
Treat this as a normal-priority kernel availability patch. It is not presented as remotely exploitable or actively exploited, but shared Linux systems should be updated promptly to reduce crash risk.
Technical view
The kernel used current->nsproxy to derive network namespace context for the MPTCP blackhole timeout sysctl. In some cases, including task exit, current->nsproxy can be NULL, causing an Oops. The fix obtains the per-network structure from table->data instead.
Likely exposure
Exposure is most likely on Linux systems running affected 6.12 or 6.13 kernels, especially where local users or workloads can interact with relevant kernel paths. The sources do not identify specific distributions or appliances.
Exploitation context
The CVSS vector is local, low complexity, low privilege, no user interaction, with high availability impact. The bundle marks CISA KEV as false, and the provided sources do not claim active exploitation.
Researcher notes
Evidence points to CWE-476 in Linux MPTCP sysctl namespace handling. The source bundle identifies syzbot discovery context and stable kernel commits, but does not provide distribution mappings, proof of exploitation, or operational mitigations beyond updating guidance.
Mitigation direction
Apply a vendor kernel update that includes the referenced stable fixes.
Check Linux distribution advisories for CVE-2025-21641 package status.
Prioritize multi-user, container, and shared compute hosts for patching.
If patching is delayed, follow vendor guidance for MPTCP/sysctl exposure.
Validation and detection
Inventory running kernel versions across Linux hosts.
Confirm downstream kernel changelogs reference CVE-2025-21641 or the stable commits.
Check whether deployed kernels include MPTCP support.
Review kernel logs for Oops or null pointer dereference events.
Monitor vendor advisories and KEV status for changes.
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.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.