| 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-50101: iommu/vt-d: Fix incorrect pci_for_each_dma_alias() for non-PCI devices |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| iommu/vt-d: Fix incorrect pci_for_each_dma_alias() for non-PCI devices |
| |
| Previously, the domain_context_clear() function incorrectly called |
| pci_for_each_dma_alias() to set up context entries for non-PCI devices. |
| This could lead to kernel hangs or other unexpected behavior. |
| |
| Add a check to only call pci_for_each_dma_alias() for PCI devices. For |
| non-PCI devices, domain_context_clear_one() is called directly. |
| |
| The Linux kernel CVE team has assigned CVE-2024-50101 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.15.142 with commit 9807860f6ad446459d0446550cf4a2dc23bbee6c and fixed in 5.15.169 with commit 0bd9a30c22afb5da203386b811ec31429d2caa78 |
| Issue introduced in 6.1.66 with commit 59862b869275c27beb25cda2054b59a8b5d04970 and fixed in 6.1.114 with commit cbfa3a83eba05240ce37839ed48280a05e8e8f6c |
| Issue introduced in 6.6.5 with commit 48f2183a4f9d3540fc5cfc8f8451621ee92c09f8 and fixed in 6.6.58 with commit fe2e0b6cd00abea3efac66de1da22d844364c1b0 |
| Issue introduced in 6.7 with commit 9a16ab9d640274b20813d2d17475e18d3e99d834 and fixed in 6.11.5 with commit 04d6826ba7ba81213422276e96c90c6565169e1c |
| Issue introduced in 6.7 with commit 9a16ab9d640274b20813d2d17475e18d3e99d834 and fixed in 6.12 with commit 6e02a277f1db24fa039e23783c8921c7b0e5b1b3 |
| |
| 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-50101 |
| 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/iommu/intel/iommu.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/0bd9a30c22afb5da203386b811ec31429d2caa78 |
| https://git.kernel.org/stable/c/cbfa3a83eba05240ce37839ed48280a05e8e8f6c |
| https://git.kernel.org/stable/c/fe2e0b6cd00abea3efac66de1da22d844364c1b0 |
| https://git.kernel.org/stable/c/04d6826ba7ba81213422276e96c90c6565169e1c |
| https://git.kernel.org/stable/c/6e02a277f1db24fa039e23783c8921c7b0e5b1b3 |
