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: <2025011145-CVE-2024-54455-0e8e@gregkh> Date: Sat, 11 Jan 2025 13:35:53 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2024-54455: accel/ivpu: Fix general protection fault in ivpu_bo_list() Description =========== In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix general protection fault in ivpu_bo_list() Check if ctx is not NULL before accessing its fields. The Linux kernel CVE team has assigned CVE-2024-54455 to this issue. Affected and fixed versions =========================== Issue introduced in 6.8 with commit 37dee2a2f4330a030abc5674bcec25ccc4addbcc and fixed in 6.12.7 with commit a1e597ee5920a6aabdf4dfc3bf76e55e1b115e23 Issue introduced in 6.8 with commit 37dee2a2f4330a030abc5674bcec25ccc4addbcc and fixed in 6.13-rc4 with commit 4b2efb9db0c22a130bbd1275e489b42c02d08050 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-2024-54455 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/accel/ivpu/ivpu_gem.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/a1e597ee5920a6aabdf4dfc3bf76e55e1b115e23 https://git.kernel.org/stable/c/4b2efb9db0c22a130bbd1275e489b42c02d08050
Powered by blists - more mailing lists