linux-kernel - Re: [PATCH] KVM: SVM: Check vCPU ID against max x2AVIC ID if and only if x2AVIC is enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <176849720857.705106.9881442086637980436.b4-ty@google.com>
Date: Thu, 15 Jan 2026 10:03:21 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Naveen N Rao <naveen@...nel.org>, Suravee Suthikulpanit <suravee.suthikulpanit@....com>
Subject: Re: [PATCH] KVM: SVM: Check vCPU ID against max x2AVIC ID if and only
 if x2AVIC is enabled

On Mon, 12 Jan 2026 15:28:05 -0800, Sean Christopherson wrote:
> When allocating the AVIC backing page, only check one of the max AVIC vs.
> x2AVIC ID based on whether or not x2AVIC is enabled.  Doing so fixes a bug
> where KVM incorrectly inhibits AVIC if x2AVIC is _disabled_ and any vCPU
> with a non-zero APIC ID is created, as x2avic_max_physical_id is left '0'
> when x2AVIC is disabled.
> 
> 
> [...]

Applied to kvm-x86 fixes, thanks!

[1/1] KVM: SVM: Check vCPU ID against max x2AVIC ID if and only if x2AVIC is enabled
      https://github.com/kvm-x86/linux/commit/cfbe371194d1

--
https://github.com/kvm-x86/linux/tree/next