| 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: <2026011452-CVE-2025-71131-c844@gregkh> Date: Wed, 14 Jan 2026 16:07:55 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-71131: crypto: seqiv - Do not use req->iv after crypto_aead_encrypt From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Do not use req->iv after crypto_aead_encrypt As soon as crypto_aead_encrypt is called, the underlying request may be freed by an asynchronous completion. Thus dereferencing req->iv after it returns is invalid. Instead of checking req->iv against info, create a new variable unaligned_info and use it for that purpose instead. The Linux kernel CVE team has assigned CVE-2025-71131 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 6.1.160 with commit 50f196d2bbaee4ab2494bb1b0d294deba292951a Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 6.6.120 with commit 0279978adec6f1296af66b642cce641c6580be46 Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 6.12.64 with commit ccbb96434d88e32358894c879457b33f7508e798 Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 6.18.4 with commit 5476f7f8a311236604b78fcc5b2a63b3a61b0169 Issue introduced in 2.6.25 with commit 0a270321dbf948963aeb0e8382fe17d2c2eb3771 and fixed in 6.19-rc4 with commit 50fdb78b7c0bcc550910ef69c0984e751cac72fa 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-71131 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/seqiv.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/50f196d2bbaee4ab2494bb1b0d294deba292951a https://git.kernel.org/stable/c/0279978adec6f1296af66b642cce641c6580be46 https://git.kernel.org/stable/c/ccbb96434d88e32358894c879457b33f7508e798 https://git.kernel.org/stable/c/5476f7f8a311236604b78fcc5b2a63b3a61b0169 https://git.kernel.org/stable/c/50fdb78b7c0bcc550910ef69c0984e751cac72fa
Powered by blists - more mailing lists