CVE-2026-99745: x86/bugs: Select the BHI mitigation based on the attack vector properly

Published Nov 20, 2026
·
Updated

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

4 affected componentsFixes available
linux/kernel>=6.17.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux<=7.3.4-1
6.1.176-16.1.192-26.12.107-16.12.117-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  3. Upgrade

    Upgrade debian/linux to 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
  4. 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

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

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.

2

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.

3

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203