Subject KVM: x86: Fix off-by-one in max_vcpu_ids bounds checks
Author dmaluka@chromium.org
Date 2026-07-30 18:24:23 +0000 UTC
Version
Cc aashish@aashishsharma.net chuanxiao.dong@intel.com dave.hansen@linux.intel.com dmaluka@chromium.org jaszczyk@chromium.org kvm@vger.kernel.org linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org minipli@grsecurity.net pbonzini@redhat.com seanjc@google.com vineeth@bitbyteword.org
Patches (3)
Name Content [All]
[PATCH 1/3] KVM: selftests: Fix treating KVM_CAP_MAX_VCPU_ID as inclusive [Body]
[PATCH 2/3] KVM: x86: Fix off-by-one in max_vcpu_ids bounds checks [Body]
[PATCH 3/3] Documentation: KVM: Clarify that KVM_CAP_MAX_VCPU_ID is exclusive [Body]
Series Summary
Passed
✓ All tests passed. No findings.
Sessions
Session 2026-07-30
Passed
ID (for dev) 1c20b4d7-2cd2-490d-8dbd-2ed2adb1035f
Status finished
Triaged OK [Log] [Trajectory]
Execution Log [Link]
Test Base Patched Verdict
[KASAN] Build Base a2cf4ef33184df0ae9e1a2b05b550133dde1698c [Config] passed [Log]
[KASAN] Boot test: Base a2cf4ef33184df0ae9e1a2b05b550133dde1698c [Config] passed [Log]
[KASAN] Build Patched a2cf4ef33184df0ae9e1a2b05b550133dde1698c [Config] [patched] passed [Log]
[KASAN] Boot test: Patched a2cf4ef33184df0ae9e1a2b05b550133dde1698c [Config] [patched] passed [Log]
[KASAN] Fuzz a2cf4ef33184df0ae9e1a2b05b550133dde1698c [Config] a2cf4ef33184df0ae9e1a2b05b550133dde1698c [Config] [patched] passed [Log] [Artifacts]