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: <2025030624-CVE-2024-58086-080c@gregkh> Date: Thu, 6 Mar 2025 17:28:25 +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-58086: drm/v3d: Stop active perfmon if it is being destroyed Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Stop active perfmon if it is being destroyed If the active performance monitor (`v3d->active_perfmon`) is being destroyed, stop it first. Currently, the active perfmon is not stopped during destruction, leaving the `v3d->active_perfmon` pointer stale. This can lead to undefined behavior and instability. This patch ensures that the active perfmon is stopped before being destroyed, aligning with the behavior introduced in commit 7d1fd3638ee3 ("drm/v3d: Stop the active perfmon before being destroyed"). The Linux kernel CVE team has assigned CVE-2024-58086 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit 26a4dc29b74a137f45665089f6d3d633fcc9b662 and fixed in 6.1.129 with commit 95036d4c01167568166108d42c2b0e9f8dbd7d2b Issue introduced in 5.15 with commit 26a4dc29b74a137f45665089f6d3d633fcc9b662 and fixed in 6.6.79 with commit eb0e0eca0eab93f310c6c37b8564049366704691 Issue introduced in 5.15 with commit 26a4dc29b74a137f45665089f6d3d633fcc9b662 and fixed in 6.12.16 with commit 1c5673a2c8926adbb61f340c779b28e18188a8cd Issue introduced in 5.15 with commit 26a4dc29b74a137f45665089f6d3d633fcc9b662 and fixed in 6.13.4 with commit f8805b12f477bd964e2820a87921c7b58cc2dee3 Issue introduced in 5.15 with commit 26a4dc29b74a137f45665089f6d3d633fcc9b662 and fixed in 6.14-rc1 with commit 21f1435b1e6b012a07c42f36b206d2b66fc8f13b 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-58086 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/gpu/drm/v3d/v3d_perfmon.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/95036d4c01167568166108d42c2b0e9f8dbd7d2b https://git.kernel.org/stable/c/eb0e0eca0eab93f310c6c37b8564049366704691 https://git.kernel.org/stable/c/1c5673a2c8926adbb61f340c779b28e18188a8cd https://git.kernel.org/stable/c/f8805b12f477bd964e2820a87921c7b58cc2dee3 https://git.kernel.org/stable/c/21f1435b1e6b012a07c42f36b206d2b66fc8f13b
Powered by blists - more mailing lists