| 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-56667: drm/i915: Fix NULL pointer dereference in capture_engine |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| drm/i915: Fix NULL pointer dereference in capture_engine |
| |
| When the intel_context structure contains NULL, |
| it raises a NULL pointer dereference error in drm_info(). |
| |
| (cherry picked from commit 754302a5bc1bd8fd3b7d85c168b0a1af6d4bba4d) |
| |
| The Linux kernel CVE team has assigned CVE-2024-56667 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.3 with commit e8a3319c31a14aa9925418bc7813c2866903b2c6 and fixed in 6.6.67 with commit e07f9c92bd127f8835ac669d83b5e7ff59bbb40f |
| Issue introduced in 6.3 with commit e8a3319c31a14aa9925418bc7813c2866903b2c6 and fixed in 6.12.6 with commit e6ebe4f14a267bc431d0eebab4f335c0ebd45977 |
| Issue introduced in 6.3 with commit e8a3319c31a14aa9925418bc7813c2866903b2c6 and fixed in 6.13 with commit da0b986256ae9a78b0215214ff44f271bfe237c1 |
| |
| 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-56667 |
| 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/i915/i915_gpu_error.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/e07f9c92bd127f8835ac669d83b5e7ff59bbb40f |
| https://git.kernel.org/stable/c/e6ebe4f14a267bc431d0eebab4f335c0ebd45977 |
| https://git.kernel.org/stable/c/da0b986256ae9a78b0215214ff44f271bfe237c1 |
