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: <2025011144-CVE-2024-54193-9ce6@gregkh> Date: Sat, 11 Jan 2025 13:35:52 +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-54193: accel/ivpu: Fix WARN in ivpu_ipc_send_receive_internal() Description =========== In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix WARN in ivpu_ipc_send_receive_internal() Move pm_runtime_set_active() to ivpu_pm_init() so when ivpu_ipc_send_receive_internal() is executed before ivpu_pm_enable() it already has correct runtime state, even if last resume was not successful. The Linux kernel CVE team has assigned CVE-2024-54193 to this issue. Affected and fixed versions =========================== Issue introduced in 6.7 with commit 8ed520ff4682aaaef7d124bd9c0950092fddb9c1 and fixed in 6.12.7 with commit 578874b2bb947e047708f4df286e4ff1ba6be3ad Issue introduced in 6.7 with commit 8ed520ff4682aaaef7d124bd9c0950092fddb9c1 and fixed in 6.13-rc4 with commit 0f6482caa6acdfdfc744db7430771fe7e6c4e787 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-54193 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_pm.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/578874b2bb947e047708f4df286e4ff1ba6be3ad https://git.kernel.org/stable/c/0f6482caa6acdfdfc744db7430771fe7e6c4e787
Powered by blists - more mailing lists