cbcvebase.
CVE-2025-21635
published 2025-01-19

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…

PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.18%
7.6th percentile
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).

Affected

9 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.12.10-1 (forky)linux 6.12.10-1 (forky)
linuxlinux
linuxlinux>= c6a58ffed53612be86b758df1cdb0b0f4305e9cb < de8d6de0ee27be4b2b1e5b06f04aeacbabbba492de8d6de0ee27be4b2b1e5b06f04aeacbabbba492
linuxlinux>= c6a58ffed53612be86b758df1cdb0b0f4305e9cb < 7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c
linuxlinux_kernel
linuxlinux_kernel>= 0 < 6.12.10-16.12.10-1
linuxlinux_kernel>= 0 < 6.12.10-16.12.10-1
linuxlinux_kernel>= 0 < 6.8.0-60.636.8.0-60.63
linuxlinux_kernel>= 4.6 < 6.12.106.12.10

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv7.8HIGH
vendor_ubuntu7.8HIGH
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.