CVE-2024-50101
Description
From CVE.org
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.
Statement
A flaw of Low impact was found in the Linux kernel's Intel VT-d IOMMU implementation. The domain_context_clear() function incorrectly called pci_for_each_dma_alias() for non-PCI devices when handling context entries, which could lead to kernel hangs or other unexpected behavior. On systems using Intel VT-d, a local user with the privileges required to reach this device handling path could use this flaw to cause a denial of service; confidentiality and integrity are not affected. For this reason Red Hat's severity (CVSS 5.5, local attack vector requiring privileges, availability impact only) is lower than the upstream CVE.org score of 7.8, which assumes combined confidentiality, integrity, and availability impact. In Red Hat Enterprise Linux 9, the kernel and kernel-rt components are affected: a fix is being pursued for RHEL 9.6, while the fix for the RHEL 9.5.z update stream was deferred given the low impact of the issue, leaving a residual risk of a local denial of service on Intel VT-d systems with non-PCI devices. Red Hat Enterprise Linux 6, 7, and 8 update streams (kernel and kernel-rt) and the Hosted OpenShift (ARO and OSD) offerings are not affected; the Fedora community kernel is affected.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | 5.5 | 5.5 |
| Attack Vector | Local | Local | Local |
| Attack Complexity | Low | Low | Low |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | None | None | None |
| Integrity Impact | None | None | None |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Confidentiality,Integrity
Technical Impact: Read Application Data; Modify Application Data; Read Files or Directories; Modify Files or Directories
An attacker could gain access to or modify sensitive data or system resources. This could allow access to protected files or directories including configuration files and files containing sensitive information.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.