The fault in iommu/amd causes the kernel to hold a spinlock while busy‑waiting for a semaphore, keeping interrupts disabled and the lock held for an extended period. This behavior, identified as a concurrency mis‑management flaw (CWE‑413) and critical resource contention (CWE‑667), can lead to soft lock‑ups under high load or repeated wait conditions, making the system unresponsive. No code execution or privileged access is required for the issue to manifest.

The vulnerability resides in the Linux kernel; it affects any Linux distribution that includes the legacy iommu implementation and has not yet applied the patch. The vendor is Linux and the product is the Linux kernel. No specific version range is listed, so any kernel build containing the unpatched iommu code is potentially vulnerable.

The CVSS score is 7.5, with an EPSS score of < 1%, and it is not listed in the CISA KEV catalog. The likely attack vector involves generating or processing IOMMU requests that trigger the waiting path while iommu.strict=1 is set, which could be achieved by a local process or an attacker with the ability to manipulate IOMMU operations at kernel level. While the bug does not provide arbitrary code execution, it offers a straightforward denial‑of‑service path that can be exploited in environments with stressed hardware or repeated device reassignment.