| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-53133: drm/amd/display: Handle dml allocation failure to avoid crash |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| drm/amd/display: Handle dml allocation failure to avoid crash |
| |
| [Why] |
| In the case where a dml allocation fails for any reason, the |
| current state's dml contexts would no longer be valid. Then |
| subsequent calls dc_state_copy_internal would shallow copy |
| invalid memory and if the new state was released, a double |
| free would occur. |
| |
| [How] |
| Reset dml pointers in new_state to NULL and avoid invalid |
| pointer |
| |
| (cherry picked from commit bcafdc61529a48f6f06355d78eb41b3aeda5296c) |
| |
| The Linux kernel CVE team has assigned CVE-2024-53133 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 6.11.10 with commit 874ff59cde8fc525112dda26b501a1bac17dde9f |
| Fixed in 6.12 with commit 6825cb07b79ffeb1d90ffaa7a1227462cdca34ae |
| |
| 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-53133 |
| 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/amd/display/dc/core/dc_state.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/874ff59cde8fc525112dda26b501a1bac17dde9f |
| https://git.kernel.org/stable/c/6825cb07b79ffeb1d90ffaa7a1227462cdca34ae |
