| 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-46698: video/aperture: optionally match the device in sysfb_disable() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| video/aperture: optionally match the device in sysfb_disable() |
| |
| In aperture_remove_conflicting_pci_devices(), we currently only |
| call sysfb_disable() on vga class devices. This leads to the |
| following problem when the pimary device is not VGA compatible: |
| |
| 1. A PCI device with a non-VGA class is the boot display |
| 2. That device is probed first and it is not a VGA device so |
| sysfb_disable() is not called, but the device resources |
| are freed by aperture_detach_platform_device() |
| 3. Non-primary GPU has a VGA class and it ends up calling sysfb_disable() |
| 4. NULL pointer dereference via sysfb_disable() since the resources |
| have already been freed by aperture_detach_platform_device() when |
| it was called by the other device. |
| |
| Fix this by passing a device pointer to sysfb_disable() and checking |
| the device to determine if we should execute it or not. |
| |
| v2: Fix build when CONFIG_SCREEN_INFO is not set |
| v3: Move device check into the mutex |
| Drop primary variable in aperture_remove_conflicting_pci_devices() |
| Drop __init on pci sysfb_pci_dev_is_enabled() |
| |
| The Linux kernel CVE team has assigned CVE-2024-46698 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.5 with commit 5ae3716cfdcd286268133867f67d0803847acefc and fixed in 6.10.8 with commit 17e78f43de0c6da34204cc858b4cc05671ea9acf |
| Issue introduced in 6.5 with commit 5ae3716cfdcd286268133867f67d0803847acefc and fixed in 6.11 with commit b49420d6a1aeb399e5b107fc6eb8584d0860fbd7 |
| Issue introduced in 6.1.47 with commit 485ec8f8e1d8ae12aa1daa5ad345ba8940ad2db7 |
| |
| 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-46698 |
| 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/firmware/sysfb.c |
| drivers/of/platform.c |
| drivers/video/aperture.c |
| include/linux/sysfb.h |
| |
| |
| 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/17e78f43de0c6da34204cc858b4cc05671ea9acf |
| https://git.kernel.org/stable/c/b49420d6a1aeb399e5b107fc6eb8584d0860fbd7 |
