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).
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://git.kernel.org/stable/c/7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c Patch
- https://git.kernel.org/stable/c/de8d6de0ee27be4b2b1e5b06f04aeacbabbba492 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 5
- CwesCWE-476NVD modified 2026-10-21 13:17
- Cpes+7 CPE criteria (now 7)NVD modified 2026-10-21 13:17
- StatusPublished → ModifiedNVD modified 2026-10-21 13:17
- CVSS5.5 (v3.1, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)NVD modified 2026-10-21 13:17
- First seenunscored · linuxNVD modified 2026-10-21 12:35
Affected (CPE criteria) 7
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:*