| 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: <2025120942-CVE-2023-53799-8397@gregkh> Date: Tue, 9 Dec 2025 09:02:20 +0900 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-53799: crypto: api - Use work queue in crypto_destroy_instance From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: crypto: api - Use work queue in crypto_destroy_instance The function crypto_drop_spawn expects to be called in process context. However, when an instance is unregistered while it still has active users, the last user may cause the instance to be freed in atomic context. Fix this by delaying the freeing to a work queue. The Linux kernel CVE team has assigned CVE-2023-53799 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.19 with commit 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and fixed in 5.10.195 with commit 625bf86bf53eb7a8ee60fb9dc45b272b77e5ce1c Issue introduced in 2.6.19 with commit 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and fixed in 5.15.132 with commit 048545d9fc6424b0a11e7e8771225bb9afe09422 Issue introduced in 2.6.19 with commit 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and fixed in 6.1.53 with commit c4cb61c5f976183c07d16b0071f0c60bc212ef1f Issue introduced in 2.6.19 with commit 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and fixed in 6.4.16 with commit 867a146690960ac7b89ce40f4ee60dd32eeb1682 Issue introduced in 2.6.19 with commit 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and fixed in 6.5.3 with commit c0dbcebc7f390ec7dbe010dcc22c60f0c6bfc26d Issue introduced in 2.6.19 with commit 6bfd48096ff8ecabf955958b51ddfa7988eb0a14 and fixed in 6.6 with commit 9ae4577bc077a7e32c3c7d442c95bc76865c0f17 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-2023-53799 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: crypto/algapi.c include/crypto/algapi.h 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/625bf86bf53eb7a8ee60fb9dc45b272b77e5ce1c https://git.kernel.org/stable/c/048545d9fc6424b0a11e7e8771225bb9afe09422 https://git.kernel.org/stable/c/c4cb61c5f976183c07d16b0071f0c60bc212ef1f https://git.kernel.org/stable/c/867a146690960ac7b89ce40f4ee60dd32eeb1682 https://git.kernel.org/stable/c/c0dbcebc7f390ec7dbe010dcc22c60f0c6bfc26d https://git.kernel.org/stable/c/9ae4577bc077a7e32c3c7d442c95bc76865c0f17
Powered by blists - more mailing lists