| 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: <2025061841-CVE-2025-38079-7fa5@gregkh> Date: Wed, 18 Jun 2025 11:34:14 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38079: crypto: algif_hash - fix double free in hash_accept From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: crypto: algif_hash - fix double free in hash_accept If accept(2) is called on socket type algif_hash with MSG_MORE flag set and crypto_ahash_import fails, sk2 is freed. However, it is also freed in af_alg_release, leading to slab-use-after-free error. The Linux kernel CVE team has assigned CVE-2025-38079 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.38 with commit fe869cdb89c95d060c77eea20204d6c91f233b53 and fixed in 5.4.294 with commit 5bff312b59b3f2a54ff504e4f4e47272b64f3633 Issue introduced in 2.6.38 with commit fe869cdb89c95d060c77eea20204d6c91f233b53 and fixed in 5.10.238 with commit bf7bba75b91539e93615f560893a599c1e1c98bf Issue introduced in 2.6.38 with commit fe869cdb89c95d060c77eea20204d6c91f233b53 and fixed in 5.15.185 with commit c3059d58f79fdfb2201249c2741514e34562b547 Issue introduced in 2.6.38 with commit fe869cdb89c95d060c77eea20204d6c91f233b53 and fixed in 6.1.141 with commit f0f3d09f53534ea385d55ced408f2b67059b16e4 Issue introduced in 2.6.38 with commit fe869cdb89c95d060c77eea20204d6c91f233b53 and fixed in 6.6.93 with commit 134daaba93193df9e988524b5cd2f52d15eb1993 Issue introduced in 2.6.38 with commit fe869cdb89c95d060c77eea20204d6c91f233b53 and fixed in 6.12.31 with commit 2f45a8d64fb4ed4830a4b3273834ecd6ca504896 Issue introduced in 2.6.38 with commit fe869cdb89c95d060c77eea20204d6c91f233b53 and fixed in 6.14.9 with commit 0346f4b742345d1c733c977f3a7aef5a6419a967 Issue introduced in 2.6.38 with commit fe869cdb89c95d060c77eea20204d6c91f233b53 and fixed in 6.15 with commit b2df03ed4052e97126267e8c13ad4204ea6ba9b6 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-38079 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/algif_hash.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/5bff312b59b3f2a54ff504e4f4e47272b64f3633 https://git.kernel.org/stable/c/bf7bba75b91539e93615f560893a599c1e1c98bf https://git.kernel.org/stable/c/c3059d58f79fdfb2201249c2741514e34562b547 https://git.kernel.org/stable/c/f0f3d09f53534ea385d55ced408f2b67059b16e4 https://git.kernel.org/stable/c/134daaba93193df9e988524b5cd2f52d15eb1993 https://git.kernel.org/stable/c/2f45a8d64fb4ed4830a4b3273834ecd6ca504896 https://git.kernel.org/stable/c/0346f4b742345d1c733c977f3a7aef5a6419a967 https://git.kernel.org/stable/c/b2df03ed4052e97126267e8c13ad4204ea6ba9b6
Powered by blists - more mailing lists