| 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-49908: drm/amd/display: Add null check for 'afb' in amdgpu_dm_update_cursor (v2) |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| drm/amd/display: Add null check for 'afb' in amdgpu_dm_update_cursor (v2) |
| |
| This commit adds a null check for the 'afb' variable in the |
| amdgpu_dm_update_cursor function. Previously, 'afb' was assumed to be |
| null at line 8388, but was used later in the code without a null check. |
| This could potentially lead to a null pointer dereference. |
| |
| Changes since v1: |
| - Moved the null check for 'afb' to the line where 'afb' is used. (Alex) |
| |
| Fixes the below: |
| drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:8433 amdgpu_dm_update_cursor() |
| error: we previously assumed 'afb' could be null (see line 8388) |
| |
| The Linux kernel CVE team has assigned CVE-2024-49908 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 6.11.3 with commit a742168b6a39ead257da53bcbe472384d6e14a1b |
| Fixed in 6.12 with commit 0fe20258b4989b9112b5e9470df33a0939403fd4 |
| |
| 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-49908 |
| 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/amdgpu_dm/amdgpu_dm.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/a742168b6a39ead257da53bcbe472384d6e14a1b |
| https://git.kernel.org/stable/c/0fe20258b4989b9112b5e9470df33a0939403fd4 |
