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 1B70936A369 for ; Sat, 15 Aug 2026 06:20:41 +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=1786774843; cv=none; b=JLUDCAi31CVYKlgHi1VCJfB3OpG0qTj2IL5kbgGLufRjyXakz3FUxnZFSQrAFhqqLthUbtIy5h4Yfy9GouxVasLYmKOOdj7qgHxdx1ZhHIKk1ZudpAf/whhkp6QQAaBXFRGH8j5CK+8pQ2CONCauv+ZVX3Mx31X8NsA7yBq/YEg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786774843; c=relaxed/simple; bh=TIG1ZIsCkpn67vHQrl/9y6iU9OqB8lYslV+DzKNjurM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=iQ2sZIb3D3J6bvQhtwXYP3CD0teLJBp2uMnQRajmhmX1HKjBbxkLMBTi1B/XXeoiOv0b/KvKfdga+qPz4Exc8dtQHWXdJWyzN01pHnlqwHz/9WgSKSBH5uMuYnMOkCdx3WoWfK+0jBwxyJdcLqnGbovW0eB9r9eqrz2eERUs6YA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=I+nOfzTp; 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="I+nOfzTp" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3A4AE1F000E9; Sat, 15 Aug 2026 06:20:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786774841; bh=38v/bPTZQMLLCi2odd6KD1a4GyqO+YrLr+uCyl1FaOY=; h=From:To:Cc:Subject:Date:Reply-To; b=I+nOfzTppms8dHpMb1RYsQ+dfcSLqX9Xa+w9SrpyM3wM4uNeUA6DRH29zDgg4DEL3 Jlh2X3YsXIqRJOScncvHSfBQr6dqvKxQlBusC66CO0PkernBAgRTkCIkA0qfzwEQcu i7t2AoUKLxQSRUDIC82ZPLKrEqk7ecbv4cu1FoTk= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-72288: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling Date: Sat, 15 Aug 2026 15:06:07 +0900 Message-ID: <2026081500-CVE-2026-72288-371b@gregkh> X-Mailer: git-send-email 2.55.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=2831; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=8t8qFcGBQQNpDoWPYKo/It8n7SwIK5Wo44YavLf32Uk=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNDDdOm3gsFL3TwFlgICx0bOprxZn2m1XfHTvOb2U+7 cRip2dtHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRcycZ5pe1l8u3NV/iWVRx 7JLuy4NrH6x74Myw4LD4oreuJz3+rf7I2GV+tEFnleCyNgA= 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: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling Hyunwoo Kim reports some really bad races should the following situation occur: - LPI-I is pending in vcpu-B's AP list - vcpu-A writes to vcpu-B's RD to disable its LPIs - vcpu-C moves I from B to C If the last two race nicely enough, vgic_prune_ap_list() can drop the irq and AP list locks, reacquire them, and in the interval the irq has been freed. UAF follows. The fix is two-fold: - Before dropping the irq and ap_list locks, take a reference on the irq - Do not try to handle migration of the pending bit: there is no expectation that this state is retained, as per the architecture With that, we're sure that the interrupt is still around, and we safely remove it from the AP list as it has no target at this stage (unless another interrupt fires, but that's another story). The Linux kernel CVE team has assigned CVE-2026-72288 to this issue. Affected and fixed versions =========================== Issue introduced in 4.8 with commit 5dd4b924e390af426e424d5e52c1b4d1566af817 and fixed in 6.18.40 with commit d19dca8194ebed371e624331c6be2cb73b562caf Issue introduced in 4.8 with commit 5dd4b924e390af426e424d5e52c1b4d1566af817 and fixed in 7.1.5 with commit b1a89d12d35a8256d2b170ced0b1c86851f3def2 Issue introduced in 4.8 with commit 5dd4b924e390af426e424d5e52c1b4d1566af817 and fixed in 7.2-rc4 with commit 7258770e5814f15e8308ebda82ac9acf6964ba8e 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-72288 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: arch/arm64/kvm/vgic/vgic.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/d19dca8194ebed371e624331c6be2cb73b562caf https://git.kernel.org/stable/c/b1a89d12d35a8256d2b170ced0b1c86851f3def2 https://git.kernel.org/stable/c/7258770e5814f15e8308ebda82ac9acf6964ba8e