Lockdep reports an unsafe lock ordering between the domain lock and the xa lock during AMD IOMMU domain allocation and flush operations. The warning indicates a HARDIRQ‑safe lock being held while a HARDIRQ‑unsafe lock is requested, which could create a lock dependency that might result in a kernel deadlock. The supplied description does not explicitly state the operational impact, but the warning implies a possible integrity issue within the IOMMU subsystem.

All variants of the Linux kernel that enable AMD IOMMU domain support are affected. The CVE description references commit identifiers that were applied after the issue was discovered, so kernels built before those commits could be vulnerable. No explicit release range is listed, but any kernel that includes AMD IOMMU support prior to the fix may be at risk.

Lockdep is active only when the kernel is compiled with debugging enabled, and the warning will be logged during runtime. No evidence of active exploitation or privilege escalation is present. The CVSS score of 4.7 and EPSS score of < 1% indicate a low‑to‑moderate severity and low likelihood of exploitation, and the vulnerability is not listed in CISA's KEV catalog, so no known active exploitation exists. Consequently the risk is low to moderate, limited to a potential kernel deadlock in a debug or development environment. The likely attack vector is local or privileged, as it requires triggering IOMMU allocation or flush operations.