CVE-2026-99745: x86/bugs: Select the BHI mitigation based on the attack vector properly
In the Linux kernel, the following vulnerability has been resolved:
x86/bugs: Select the BHI mitigation based on the attack vector properly
The BHI mitigation selection is inconsistent with the documentation (attackvectorcontrols.rst), which lists BHI under both the user->kernel and guest->host attack vectors. bhiselectmitigation() only enables it when CPUMITIGATEGUESTHOST is set; otherwise it selects BHIMITIGATIONOFF, even if CPUMITIGATEUSERKERNEL is set.
As a result, a kernel compiled with KVM disabled gets BHI automatically disabled, since CPUMITIGATEGUESTHOST defaults to off without KVM. This is a bug, given that CPUMITIGATEUSERKERNEL still needs it: on affected Intel CPUs these kernels lose BHIDISS or the BHB clearing loop by default. Booting with mitigations=auto,noguesthost has the same effect.
Select BHIMITIGATIONON whenever user->kernel is mitigated, and keep BHIMITIGATIONVMEXITONLY for the guest->host-only case.
[ bp: Clarify commit title. ]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1 - Configuration
Select BHI_MITIGATION_ON whenever user->kernel is mitigated, and retain BHI_MITIGATION_VMEXIT_ONLY for the guest->host-only case.
Linux kernel BHI mitigation BHI mitigation selection = BHI_MITIGATION_ON when user->kernel is mitigated; BHI_MITIGATION_VMEXIT_ONLY for the guest->host-only case
Event History
Frequently Asked Questions
Which systems are exposed to the incorrect mitigation selection?
Affected Intel systems running a Linux kernel configured without KVM can have BHI mitigation automatically disabled despite user-to-kernel mitigation being required. Systems booted with mitigations=auto,no_guest_host are also affected.
What attack paths are left insufficiently mitigated?
The issue affects the user-to-kernel BHI attack vector when the kernel selects BHI_MITIGATION_OFF based solely on guest-to-host mitigation settings. On affected Intel CPUs, this can leave BHI_DIS_S or the BHB clearing loop disabled by default.
How should mitigation selection behave after the fix?
BHI_MITIGATION_ON should be selected whenever the user-to-kernel vector is mitigated. BHI_MITIGATION_VMEXIT_ONLY remains appropriate when only the guest-to-host attack vector is mitigated.