CVE-2025-21637: sctp: sysctl: udp_port: avoid using current->nsproxy
In the Linux kernel, the following vulnerability has been resolved:
sctp: sysctl: udp_port: 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, but that would
increase the size of this fix, while 'sctp.ctl_sock' still needs to be
retrieved from 'net' structure.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can crash the kernel when SCTP UDP-port settings are accessed while a task is exiting. Successful local exploitation could disrupt systems or alter system behavior, but the supplied evidence indicates no confidentiality impact.
Executive priority
Prioritize remediation during the next urgent kernel-maintenance window, especially on shared Linux hosts. Accelerate internet-facing multi-user or workload-dense systems where local code execution is plausible. Treat exposure as unconfirmed until vendor package and backport checks are complete.
Technical view
The SCTP sysctl udp_port handler could dereference current->nsproxy after it becomes NULL, causing a kernel null-pointer dereference. The correction obtains the relevant network namespace from table->data instead of the current task. CVSS 3.1 is 7.1, requiring local access with low privileges and indicating high integrity and availability impact.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or branches without the referenced backports. Systems permitting untrusted local users or workloads deserve greater priority. The supplied version data is ambiguous, so distribution package status and exact backport history must determine exposure.
Exploitation context
The supplied bundle reports a syzbot-triggered kernel Oops involving an exiting task and acct(2). It does not establish malicious exploitation. The CVE is not listed as KEV, and no supplied source reports active exploitation or a public weaponized exploit.
Researcher notes
The failure is CWE-476 in SCTP sysctl handling. The unsafe dependency on current->nsproxy creates namespace inconsistency and a NULL-dereference window during task exit. The fix derives struct net through container_of() from table->data. Supplied evidence supports crash and integrity/availability risk, but not a demonstrated exploitation primitive.
Mitigation direction
Apply the appropriate vendor kernel update containing the referenced upstream or stable fix.
Consult Linux distribution guidance because patched package versions may differ from upstream kernel numbers.
Reboot into the updated kernel after installation.
Restrict unnecessary untrusted local access until affected systems are updated.
Validation and detection
Inventory running kernel versions, not only installed kernel packages.
Compare each distribution package against its vendor advisory and backport status.
Confirm the active kernel contains the applicable referenced fix.
Verify systems rebooted successfully into the patched kernel.
Regression-test SCTP sysctl and network-namespace operations where operationally relevant.
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.