NULL pointer dereference in Linux
CVE-2025-21635
In the Linux kernel, the following vulnerability has been resolved:
rds: sysctl: rds_tcp_{rcv,snd}buf: 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 per-netns structure can be obtained from the table->data using
container_of(), then the 'net' one can be retrieved from the listen
socket (if available).
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.003, 17.3th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Linux — versions c6a58ffed53612be86b758df1cdb0b0f4305e9cb, 4.6, 0
- Linux Kernel — versions 6.13
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (fkie-cad/nvd-json-data-feeds, oogasawa/Utility-security). These reference the CVE in a list, notes or a scanner and are not exploit code for it.