Description
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 products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
c6a58ffed53612be86b758df1cdb0b0f4305e9cb to < 6f353c2230c199f343406c08482940ec5d8ba89caffectedc6a58ffed53612be86b758df1cdb0b0f4305e9cb to < 33b3e09a489a31b30342b77cc55290f025d95c7eaffectedc6a58ffed53612be86b758df1cdb0b0f4305e9cb to < de8d6de0ee27be4b2b1e5b06f04aeacbabbba492affectedc6a58ffed53612be86b758df1cdb0b0f4305e9cb to < 7f5611cbc4871c7fb1ad36c2e5a9edad63dca95caffected
Linux Linux
Default version status: affected
4.6affected0 to < 4.6unaffected6.1.191 to ≤ 6.1.*unaffected6.6.160 to ≤ 6.6.*unaffected6.12.10 to ≤ 6.12.*unaffected6.13 to ≤ *unaffected