| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025011944-CVE-2025-21638-35a8@gregkh> Date: Sun, 19 Jan 2025 11:17:47 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2025-21638: sctp: sysctl: auth_enable: avoid using current->nsproxy Description =========== 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. The Linux kernel CVE team has assigned CVE-2025-21638 to this issue. Affected and fixed versions =========================== Issue introduced in 3.15 with commit b14878ccb7fac0242db82720b784ab62c467c0dc and fixed in 6.1.125 with commit 1b67030d39f2b00f94ac1f0af11ba6657589e4d3 Issue introduced in 3.15 with commit b14878ccb7fac0242db82720b784ab62c467c0dc and fixed in 6.6.72 with commit 7ec30c54f339c640aa7e49d7e9f7bbed6bd42bf6 Issue introduced in 3.15 with commit b14878ccb7fac0242db82720b784ab62c467c0dc and fixed in 6.12.10 with commit c184bc621e3cef03ac9ba81a50dda2dae6a21d36 Issue introduced in 3.15 with commit b14878ccb7fac0242db82720b784ab62c467c0dc and fixed in 6.13-rc7 with commit 15649fd5415eda664ef35780c2013adeb5d9c695 Issue introduced in 3.10.41 with commit e5eae4a0511241959498b180fa0df0d4f1b11b9c Issue introduced in 3.12.21 with commit 88830f227a1f96e44d82ddfcb0cc81d517ec6dd8 Issue introduced in 3.14.5 with commit 3938b0336a93fa5faa242dc9e5823ac69df9e066 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-21638 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: net/sctp/sysctl.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/1b67030d39f2b00f94ac1f0af11ba6657589e4d3 https://git.kernel.org/stable/c/7ec30c54f339c640aa7e49d7e9f7bbed6bd42bf6 https://git.kernel.org/stable/c/c184bc621e3cef03ac9ba81a50dda2dae6a21d36 https://git.kernel.org/stable/c/15649fd5415eda664ef35780c2013adeb5d9c695
Powered by blists - more mailing lists