CVE-2025-21638

In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: auth_enable: 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 'net' structure can be obtained from the table->data using container_of(). Note that table->data could also be used directly, but that would increase the size of this fix, while 'sctp.ctl_sock' still needs to be retrieved from 'net' structure.

• linux linux kernel (>= 3.10.41 < 3.11) • linux linux kernel (>= 3.12.20 < 3.13) • linux linux kernel (>= 3.14.5 < 5.4.290) • linux linux kernel (>= 5.5 < 5.10.234) • linux linux kernel (>= 5.11 < 5.15.177) • linux linux kernel (>= 5.16 < 6.1.125) • linux linux kernel (>= 6.2 < 6.6.72) • linux linux kernel (>= 6.7 < 6.12.10) • linux linux kernel 6.13