From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B381B30C16D for ; Wed, 24 Jun 2026 16:32:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782318773; cv=none; b=D/+KtVu2eow/LUzZw2Vg3sckpSxdCDuliHaO/utU0tHzbny2ra0k6oXfQONbnnEcnM21RwIO+5k6Z+thlX89mUWjob02lm7iIsz+d8a4b08pwgN3t4gBc/3Cs3W2tjUWTgZx+vFAXbI9h7llzuIV+UsYuShpmkJPteAbNhs1bds= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782318773; c=relaxed/simple; bh=sPyzR/v7ROPGoW/FNublNUQSP/WAZ+bBpeEZKckEK1Y=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=FKM61nkPWtD/GudlqvHLr2eaV3lOjsYUFEvtUuFi7C/fBnb1r+56reCc3KU31xxO4aSZVWQwuJ2T2zD2+kX+cvcxiYPScj81HUZ2oVWLVKhAAAorlCn3DUL/VgUDvh9wvKSkm8ic4AFPBFWOzTqkQBKkSMj5aQIWM4HToxtAE0Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=xOnLLEkg; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="xOnLLEkg" Received: by smtp.kernel.org (Postfix) with ESMTPSA id BAAE71F000E9; Wed, 24 Jun 2026 16:32:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1782318772; bh=IaoeiF9HTXZvDduoEQGrrmY8mE0hl6p7ETlyKFIvjsk=; h=From:To:Cc:Subject:Date:Reply-To; b=xOnLLEkgS7FOiqHY7I7ff5zUpbuY2YFbvs3dVEHcAl6Z7egwgVMYmjuofWKfOFcy+ PyINWM6VymnpAzcWQrSSQNKDgVx+kFSRe7qltSpPzg2ofPNpE/oCb1sZiISdMG9+vb NB0kNmC+TdtSvMnl8OQkU45KfU6Xc3G5o4qbUEk8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-52952: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset Date: Wed, 24 Jun 2026 17:29:36 +0100 Message-ID: <2026062434-CVE-2026-52952-0cff@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2733; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=7KvZQnIqAfgb5XMtk4SbC2niOViSA9wEBcN9nEJ2cSo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFk2rO8MxM4lB/x20uHSvhArc6lBp3Oicu8engyV/e5V5 5rt1Us7YlkYBJkYZMUUWb5s4zm6v+KQopeh7WmYOaxMIEMYuDgFYCLlGgwLOvPi5Fjmvk7+7Djx p1KAslVd8P4/DPNM2i0796mqz+j3yfu+3DRuDm9i1E4A X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== 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. The Linux kernel CVE team has assigned CVE-2026-52952 to this issue. Affected and fixed versions =========================== Issue introduced in 7.0 with commit c279e83953d937470f8a6e69b69f62608714f13f and fixed in 7.0.10 with commit 8fc289e809f3eb7e36cadc4684ab6fad747a5a93 Issue introduced in 7.0 with commit c279e83953d937470f8a6e69b69f62608714f13f and fixed in 7.1 with commit 5474e6e17a262db45c60575c73f70210f5c7001f Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-52952 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/iommu/iommu.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/8fc289e809f3eb7e36cadc4684ab6fad747a5a93 https://git.kernel.org/stable/c/5474e6e17a262db45c60575c73f70210f5c7001f