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 C1B7E30C16D for ; Wed, 24 Jun 2026 16:32:55 +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=1782318776; cv=none; b=gldjnZE8wR44dStJ36sn4SyshVPUL7N7S+pa9EH3SJ3+E8oxERA8crGLfWugo4cRBnCXbwWoUTpfC5nBzs89Fj4iSw46f0B4RR3lQo39IvwtXa3BCXEH15rYqei1oobSN9oaMHaPxIr6qVDZUUXqeiiAbeHb1u+XNhbDY4HtVFk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782318776; c=relaxed/simple; bh=2leaWIn3T+nLD/o8HQlCN+A5Loc9/kbKIwUghZIuAPE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=e/6Sw7H2u4hwlowy5TI4xip4xU2oeGJyWfaBIUq0i118joNvG/4xVpw3315AH09Hy83AlUcWMjwcB31m0vZMPKzaRbtZOdn11BwnwqlpxR1AT9KbgRbfyp33IB6bXNWt63U4aLG3LhbdeKY5jGJk0zuyQyXcRMoqSRb/e0FyCG4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=AvKd5SQB; 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="AvKd5SQB" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 125231F000E9; Wed, 24 Jun 2026 16:32:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1782318775; bh=B3WhR1SaKO0KG8ORewj2ljHnJHCJmQzeU+Ru+QH8jDA=; h=From:To:Cc:Subject:Date:Reply-To; b=AvKd5SQBFubB72gmX6qZmBPpVQQ0LCS9E996ioNkB6WcnkbWVMw+reUfr7xrWPHO5 7bGFtOyh/0+bJjGt3YDlcZkBl89VQxmiZw5Llr/TboE4j/R9r/pzxFNOgeuKAvkvGQ WCgeGe1CMBFMWIygFf4k2uqBx0CjLwLQHyommuM0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-52953: iommu/vt-d: Fix oops due to out of scope access Date: Wed, 24 Jun 2026 17:29:37 +0100 Message-ID: <2026062434-CVE-2026-52953-69a6@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=3143; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=YEsNQxXxfrcpvmZyVmZj7lzJM5gbrKHfdUIQwFxfj1g=; b=owGbwMvMwCRo6H6F97bub03G02pJDFk2rO86d9hPiC12XXclw3HRuvyWtQvUZAI7tnVNv+bV6 TxX/2dDRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEwkbgbD/DqO6nlNmZXPvwst sVrQEOJ4M/86F8P8rDtWrmkvAtMXzLjRWyMoGZr0NYEVAA== 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/vt-d: Fix oops due to out of scope access Below oops triggers when kill QEMU process: Oops: general protection fault, probably for non-canonical address 0x7fffffff844eaaa7: 0000 [#1] SMP NOPTI Call Trace: do_raw_spin_lock+0xaa/0xc0 _raw_spin_lock_irqsave+0x21/0x40 domain_remove_dev_pasid+0x52/0x160 intel_nested_set_dev_pasid+0x1b9/0x1e0 __iommu_set_group_pasid+0x56/0x120 pci_dev_reset_iommu_done+0xe3/0x180 pcie_flr+0x65/0x160 __pci_reset_function_locked+0x5b/0x120 vfio_pci_core_close_device+0x63/0xe0 [vfio_pci_core] vfio_df_close+0x4f/0xa0 vfio_df_unbind_iommufd+0x2d/0x60 vfio_device_fops_release+0x3e/0x40 __fput+0xe5/0x2c0 task_work_run+0x58/0xa0 do_exit+0x2c8/0x600 do_group_exit+0x2f/0xa0 get_signal+0x863/0x8c0 arch_do_signal_or_restart+0x24/0x100 exit_to_user_mode_loop+0x87/0x380 do_syscall_64+0x2ff/0x11e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The global static blocked domain is a dummy domain without corresponding dmar_domain structure, accessing beyond iommu_domain structure triggers oops easily. Fix it by return early in domain_remove_dev_pasid() like identity domain. The Linux kernel CVE team has assigned CVE-2026-52953 to this issue. Affected and fixed versions =========================== Issue introduced in 6.6 with commit 7d0c9da6c1509664d96488042bacc02308ca33b2 and fixed in 6.18.33 with commit 88397fad7914ee74a7880fa5ce01f9eb6bfe0743 Issue introduced in 6.6 with commit 7d0c9da6c1509664d96488042bacc02308ca33b2 and fixed in 7.0.10 with commit 1e659db468476733d217c1314c1e0d9244356d6c Issue introduced in 6.6 with commit 7d0c9da6c1509664d96488042bacc02308ca33b2 and fixed in 7.1 with commit a6dea58d8625c06b9654c0555f101742481335c3 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-52953 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/intel/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/88397fad7914ee74a7880fa5ce01f9eb6bfe0743 https://git.kernel.org/stable/c/1e659db468476733d217c1314c1e0d9244356d6c https://git.kernel.org/stable/c/a6dea58d8625c06b9654c0555f101742481335c3