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 WARN_ON in __iommu_group_set_domain_nofail() due to reset In __iommu_group_set_domain_internal(), 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 WARN_ON in __iommu_group_set_domain_nofail(). Other IOMMU_SET_DOMAIN_MUST_SUCCEED callers in detach/teardown paths, such as __iommu_group_set_core_domain and __iommu_release_dma_ownership, should not be rejected, as the domain would be freed anyway in these nofail paths while group->domain is still pointing to it. So pci_dev_reset_iommu_done() could trigger a UAF when re-attaching group->domain. Honor the IOMMU_SET_DOMAIN_MUST_SUCCEED flag, allowing the callers through the group->recovery_cnt 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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 7.0.10
- CVEs
- CVE-2026-52952
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 12:43 UTC · Revision 1
Source evidence
iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset
core-osv · Original sourcePublished 24 Jun 2026, 16:28 UTC
In the Linux kernel, the following vulnerability has been resolved: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset In __iommu_group_set_domain_internal(), 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 WARN_ON in __iommu_group_set_domain_nofail(). Other IOMMU_SET_DOMAIN_MUST_SUCCEED callers in detach/teardown paths, such as __iommu_group_set_core_domain and __iommu_release_dma_ownership, should not be rejected, as the domain would be freed anyway in these nofail paths while group->domain is still pointing to it. So pci_dev_reset_iommu_done() could trigger a UAF when re-attaching group->domain. Honor the IOMMU_SET_DOMAIN_MUST_SUCCEED flag, allowing the callers through the group->recovery_cnt 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.
osv:CVE-2026-52952
Kernel
Fixed versions: 7.0.10
Complete source record
{
"id": "c8f7eef03f651f79955ac39eba44c8e189d113850b2dec26cbea5d6892907b53",
"url": "https://osv.dev/vulnerability/CVE-2026-52952",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset",
"summary": "In the Linux kernel, the following vulnerability has been resolved: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset In __iommu_group_set_domain_internal(), 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 WARN_ON in __iommu_group_set_domain_nofail(). Other IOMMU_SET_DOMAIN_MUST_SUCCEED callers in detach/teardown paths, such as __iommu_group_set_core_domain and __iommu_release_dma_ownership, should not be rejected, as the domain would be freed anyway in these nofail paths while group->domain is still pointing to it. So pci_dev_reset_iommu_done() could trigger a UAF when re-attaching group->domain. Honor the IOMMU_SET_DOMAIN_MUST_SUCCEED flag, allowing the callers through the group->recovery_cnt 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.",
"evidence": "osv:CVE-2026-52952",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.0.10",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-52952",
"aliases": [
"CVE-2026-52952"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "c279e83953d937470f8a6e69b69f62608714f13f"
},
{
"fixed": "8fc289e809f3eb7e36cadc4684ab6fad747a5a93"
},
{
"fixed": "5474e6e17a262db45c60575c73f70210f5c7001f"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-52952.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "7.0.0"
},
{
"fixed": "7.0.10"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-52952.json"
}
}
],
"modified": "2026-10-28T02:30:28.965174563Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/5474e6e17a262db45c60575c73f70210f5c7001f",
"https://git.kernel.org/stable/c/8fc289e809f3eb7e36cadc4684ab6fad747a5a93",
"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52952.json",
"https://access.redhat.com/security/cve/CVE-2026-52952",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/52xxx/CVE-2026-52952.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-52952",
"https://bugzilla.redhat.com/show_bug.cgi?id=2492422",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/52xxx/CVE-2026-52952.json"
}
},
"related_cves": [
{
"value": "CVE-2026-52952",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 495521,
"published_at": "2026-06-24T16:28:35.247+00:00"
}