CVE-2025-21636: sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy
In the Linux kernel, the following vulnerability has been resolved:
sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy
As mentioned in a previous commit of this series, 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 'net' structure can be obtained from the table->data using
container_of().
Note that table->data could also be used directly, as this is the only
member needed from the 'net' structure, but that would increase the size
of this fix, to use '*data' everywhere 'net->sctp.probe_interval' is
used.
Security readout for executives and security teams
Plain-English summary
CVE-2025-21636 is a Linux kernel bug that can crash the system when SCTP sysctl handling reads network namespace state from the current task during edge-case task exit conditions. The business impact is availability: a local low-privileged actor could cause a denial of service on affected kernels.
Executive priority
Patch during the next normal kernel maintenance cycle, faster for shared or multi-tenant systems. This is a credible availability bug, but sources do not show remote exploitation, data theft, privilege escalation, or active exploitation.
Technical view
The flaw is a CWE-476 null pointer dereference in SCTP plpmtud_probe_interval sysctl handling. Kernel code used current->nsproxy to find the net namespace, which can be NULL in some cases. The fix obtains the net structure from table->data instead. CVSS is 5.5: local, low complexity, low privileges, availability impact only.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds. Risk is most relevant where untrusted local users, hosted workloads, or containerized processes can reach the vulnerable kernel path. The provided sources do not identify a remote attack path.
Exploitation context
The CVE is not marked KEV, and the provided sources do not report active exploitation. The issue was found by syzbot under a task-exit edge case. Treat it as a local denial-of-service risk, not a confidentiality or integrity compromise based on available evidence.
Researcher notes
Focus validation on affected Linux kernel branches and whether the SCTP sysctl fix is present. The root issue is namespace lookup through current->nsproxy during sysctl access. Evidence supports local denial of service only; do not infer remote reachability without vendor-specific proof.
Mitigation direction
Apply vendor kernel updates containing the referenced stable fixes.
Prioritize multi-user servers, shared hosting, and container hosts.
Check Linux distribution advisories for exact package versions.
Use standard change windows if availability risk is manageable.
Avoid direct wrangler or deployment assumptions; this is kernel remediation.
Validation and detection
Inventory Linux kernel versions across servers and appliances.
Compare installed kernels with vendor advisories and fixed stable commits.
Confirm distribution packages include the CVE-2025-21636 fix.
Review whether untrusted local workloads run on affected hosts.
After patching, verify hosts boot into the updated kernel.
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.