| 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: <2025022628-CVE-2022-49258-0dd7@gregkh> Date: Wed, 26 Feb 2025 02:57:43 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49258: crypto: ccree - Fix use after free in cc_cipher_exit() Description =========== In the Linux kernel, the following vulnerability has been resolved: crypto: ccree - Fix use after free in cc_cipher_exit() kfree_sensitive(ctx_p->user.key) will free the ctx_p->user.key. But ctx_p->user.key is still used in the next line, which will lead to a use after free. We can call kfree_sensitive() after dev_dbg() to avoid the uaf. The Linux kernel CVE team has assigned CVE-2022-49258 to this issue. Affected and fixed versions =========================== Issue introduced in 4.17 with commit 63ee04c8b491ee148489347e7da9fbfd982ca2bb and fixed in 5.10.110 with commit c93017c8d5ebf55a4e453ac7c84cc84cf92ab570 Issue introduced in 4.17 with commit 63ee04c8b491ee148489347e7da9fbfd982ca2bb and fixed in 5.15.33 with commit 335bf1fc74f775a8255257aa3e33763f2257b676 Issue introduced in 4.17 with commit 63ee04c8b491ee148489347e7da9fbfd982ca2bb and fixed in 5.16.19 with commit 25c358efee5153dfd240d4e0d3169d5bebe9cacd Issue introduced in 4.17 with commit 63ee04c8b491ee148489347e7da9fbfd982ca2bb and fixed in 5.17.2 with commit cffb5382bd8d3cf21b874ab5b84bf7618932286b Issue introduced in 4.17 with commit 63ee04c8b491ee148489347e7da9fbfd982ca2bb and fixed in 5.18 with commit 3d950c34074ed74d2713c3856ba01264523289e6 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-2022-49258 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: drivers/crypto/ccree/cc_cipher.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/c93017c8d5ebf55a4e453ac7c84cc84cf92ab570 https://git.kernel.org/stable/c/335bf1fc74f775a8255257aa3e33763f2257b676 https://git.kernel.org/stable/c/25c358efee5153dfd240d4e0d3169d5bebe9cacd https://git.kernel.org/stable/c/cffb5382bd8d3cf21b874ab5b84bf7618932286b https://git.kernel.org/stable/c/3d950c34074ed74d2713c3856ba01264523289e6
Powered by blists - more mailing lists