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: <2025050128-CVE-2025-23152-1eae@gregkh> Date: Thu, 1 May 2025 14:56:32 +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-23152: arm64/crc-t10dif: fix use of out-of-scope array in crc_t10dif_arch() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: arm64/crc-t10dif: fix use of out-of-scope array in crc_t10dif_arch() Fix a silly bug where an array was used outside of its scope. The Linux kernel CVE team has assigned CVE-2025-23152 to this issue. Affected and fixed versions =========================== Issue introduced in 6.14 with commit 2051da858534a73589cdb27af914fe1c03b9ee98 and fixed in 6.14.3 with commit bd9e1a03e579a01dfa66dbaa53d0219c33cbc463 Issue introduced in 6.14 with commit 2051da858534a73589cdb27af914fe1c03b9ee98 and fixed in 6.15-rc1 with commit d48b663f410f8b35b8ba9bd597bafaa00f53293b 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-23152 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: arch/arm64/lib/crc-t10dif-glue.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/bd9e1a03e579a01dfa66dbaa53d0219c33cbc463 https://git.kernel.org/stable/c/d48b663f410f8b35b8ba9bd597bafaa00f53293b
Powered by blists - more mailing lists