| 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-58073: drm/msm/dpu: check dpu_plane_atomic_print_state() for valid sspp |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| drm/msm/dpu: check dpu_plane_atomic_print_state() for valid sspp |
| |
| Similar to the r_pipe sspp protect, add a check to protect |
| the pipe state prints to avoid NULL ptr dereference for cases when |
| the state is dumped without a corresponding atomic_check() where the |
| pipe->sspp is assigned. |
| |
| Patchwork: https://patchwork.freedesktop.org/patch/628404/ |
| |
| The Linux kernel CVE team has assigned CVE-2024-58073 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.13 with commit 31f7148fd3704e0981b4eb6c6d13cf584da606c4 and fixed in 6.13.2 with commit 008af2074e4b91d34440102501b710c235a3b245 |
| Issue introduced in 6.13 with commit 31f7148fd3704e0981b4eb6c6d13cf584da606c4 and fixed in 6.14 with commit 789384eb1437aed94155dc0eac8a8a6ba1baf578 |
| |
| 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-58073 |
| 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/msm/disp/dpu1/dpu_plane.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/008af2074e4b91d34440102501b710c235a3b245 |
| https://git.kernel.org/stable/c/789384eb1437aed94155dc0eac8a8a6ba1baf578 |
