CVE-2024-50101: iommu/vt-d: Fix incorrect pci_for_each_dma_alias() for non-PCI devices
In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: Fix incorrect pciforeachdmaalias() for non-PCI devices
Previously, the domaincontextclear() function incorrectly called pciforeachdmaalias() 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 pciforeachdmaalias() for PCI devices. For non-PCI devices, domaincontextclearone() is called directly.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50101?
CVE-2024-50101 has been classified with a moderate severity level due to its potential impact on non-PCI devices during context entry setup.
How do I fix CVE-2024-50101?
To fix CVE-2024-50101, update the Linux kernel to the latest version available that addresses this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-50101?
CVE-2024-50101 affects Linux kernel versions from 5.15.142 to 5.15.169, 5.16 to 6.1.114, 6.2 to 6.6.58, 6.7 to 6.11.5, and specific release candidates 6.12-rc1 to 6.12-rc3.
What are the implications of CVE-2024-50101 on system security?
CVE-2024-50101 may allow incorrect handling of non-PCI device contexts, potentially leading to security vulnerabilities on systems running affected kernel versions.
Is there a workaround for CVE-2024-50101 before applying a patch?
Currently, there are no effective workarounds for CVE-2024-50101, so timely updating of the kernel is recommended.