From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154022; b=qLLvp6tJQPNut8WuwruGDB1OdQr36vJHQc7XF3ju2Yg/B8r2/CJCqRSwpjhU25Wf9RuT txvHjX/TC5lrP7fOQe+xGGMEhAmdK8TQH29j2kPzX6lsB0qH/OGwAyYFRYVt8fmQIeu1E /BWUsl9Ubb3ZnPndkByt87CjCcT/GDxOpNMuqIp9PeiUyQcAWyTkSZFIjAU16cZedcQp5 C85ibW+9TbMroDwfF5jbrbXdI4L6zw27OGu1nsvk0/D4jbsJ2m7qOC+4kYrGFORzUbs09 UXjtrG7oLLzisiqamZvA9v1IvHzEL0QeHpfs1lO1zwQliPF2t4yVANt3OmEG6Chzfdw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154022; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=9pVzNcO7e7G6koZCsAPKZfeMyMIYdWNXY+8HdU4FDAY=; b=oQShuucEAOm2jX4CbAnyR8b5ovyRvlYGZ6BvfEDJHwyHEr2EZXHZiwMXlEfCbdzR+U9o HgQ9ZHE73EV5tXXXfp6F9DrqWN0zevHVy7eX88fFNBPxqUWrGWwXZEG7YjPEmA9JCfLyV PbU/M+vEdLA1pk2S0vXP69u78NCmPLPWNKui5BS/icFmbRAZEZ/AmXDZCeWMj0f1eTgIa m5YAW6xAutDaOF7N/AIfmS+I45LU0gcIQKRu53knKe1Vm1EkcFTnuZdiHoKDwlJ79ws1s prRIh/J3ylN2ipFOB9GKPCQKIapESrW2bkJr2/lRjUwCUTGq56zzrMk7BWlYchVOj2w== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=T3LZywWn; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1ADB9606A320 for ; Fri, 20 Nov 2026 05:53:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=T3LZywWn Received: by smtp.kernel.org (Postfix) with ESMTPSA id 67A2F1F000C4; Fri, 20 Nov 2026 05:53:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154022; bh=9pVzNcO7e7G6koZCsAPKZfeMyMIYdWNXY+8HdU4FDAY=; h=From:To:Cc:Subject:Date:Reply-To; b=T3LZywWnbQ2WkCv72CmI//SwFyKeIZjDGho/90yVmp5zBW5LAlDSdayKb5EncOoH/ eGg1gb9rId6FdnoxYrH38afkJrFEinFRsuV4Jbs8SNRYPsiK+9CcdSx7o4SOX3Pj3H 1p/1JTrfh2S3n0b0AnV9He9A/3gr9ijyhhB86hlA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99573: KVM: arm64: vgic: Stop the target vcpu when disabling LPIs Date: Fri, 20 Nov 2026 06:49:19 +0100 Message-ID: <2026112016-CVE-2026-99573-3a2c@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2676; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=FrORqmtqp0Yq2Gdt/z/rwsm1yaDCDWITZbYo/pnWbZk=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/78dsj17qbGAUvTZjmZTKPOGOc6bN0/92+gWzmHnd2 m/hfcSoI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACZy0Yhhwd4bkXPX1+7y3bRG bK96+Hl9p8VvHzDM9/rmfX+5+2/5KUZ2C2aFbhGtW/7oDAA= 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: Stop the target vcpu when disabling LPIs Disabling LPIs is pretty nasty, as it directly messes with the AP list of the affected CPU, which could be running... This has the potential to lead to really bad behaviours, and we should not be doing that. Take example on the way the Active state is handled and simply pause the the vcpu so that we are sure it is in a quiescent state, and the state be safely manipulated. Nobody has any expectation of performance for this anyway. The Linux kernel CVE team has assigned CVE-2026-99573 to this issue. Affected and fixed versions =========================== Issue introduced in 5.1 with commit 96085b949672dca19773495813b577eb3bedf06e and fixed in 6.12.118 with commit b5d4692948f2fc6cf6f1b7223bd10c3d1c3bb104 Issue introduced in 5.1 with commit 96085b949672dca19773495813b577eb3bedf06e and fixed in 6.18.64 with commit 9b12da785bd0af7f0976ec24332f33634f7ee924 Issue introduced in 5.1 with commit 96085b949672dca19773495813b577eb3bedf06e and fixed in 7.3.5 with commit 8f431c3829f38bacbf69447cbffda6968b260f5d Issue introduced in 5.1 with commit 96085b949672dca19773495813b577eb3bedf06e and fixed in 7.4-rc1 with commit a1b4bd2c2c262b8094c86afb99364d16ac08cb66 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-99573 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-mmio-v3.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/b5d4692948f2fc6cf6f1b7223bd10c3d1c3bb104 https://git.kernel.org/stable/c/9b12da785bd0af7f0976ec24332f33634f7ee924 https://git.kernel.org/stable/c/8f431c3829f38bacbf69447cbffda6968b260f5d https://git.kernel.org/stable/c/a1b4bd2c2c262b8094c86afb99364d16ac08cb66