CVE-2026-52952: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset
In the Linux kernel, the following vulnerability has been resolved:
iommu: Fix WARNON in iommugroupsetdomainnofail() due to reset
In iommugroupsetdomaininternal(), concurrent domain attachments are rejected when any device in the group is recovering. This is necessary to fence concurrent attachments to a multi-device group where devices might share the same RID due to PCI DMA alias quirks, but triggers the WARNON in iommugroupsetdomainnofail().
Other IOMMUSETDOMAINMUSTSUCCEED callers in detach/teardown paths, such as iommugroupsetcoredomain and iommureleasedmaownership, should not be rejected, as the domain would be freed anyway in these nofail paths while group->domain is still pointing to it. So pcidevresetiommudone() could trigger a UAF when re-attaching group->domain.
Honor the IOMMUSETDOMAINMUSTSUCCEED flag, allowing the callers through the group->recoverycnt fence, so as to update the group->domain pointer. Instead add a gdev->blocked check in the device iteration loop, to prevent any concurrent per-device detachment.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-52952?
CVE-2026-52952 has a risk rating of 47.
How do I fix CVE-2026-52952?
To resolve CVE-2026-52952, update to the latest version of the Linux kernel that includes the fix.
What component is affected by CVE-2026-52952?
CVE-2026-52952 affects the IOMMU subsystem in the Linux kernel.
Is CVE-2026-52952 a critical vulnerability?
While CVE-2026-52952 has a moderate risk rating, it is important to apply the fix to avoid potential issues.
What systems are vulnerable to CVE-2026-52952?
Any system running the affected versions of the Linux kernel is vulnerable to CVE-2026-52952.