NULL pointer dereference in Linux
CVE-2025-21641
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().
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.5 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.002, 7.4th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Linux — versions 27069e7cb3d1cea9377069266acf19b9cc5ad0ae, 6.12, 0
- Linux Kernel — versions 6.13
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (fkie-cad/nvd-json-data-feeds). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- git.kernel.org/stable/c/4c74fbdc5ab95b13945be01e6065940b68222db7 (Patch, Mailing List)
- git.kernel.org/stable/c/92cf7a51bdae24a32c592adcdd59a773ae149289 (Patch, Mailing List)