{"api_version":"1","generated_at":"2026-11-20T07:29:57+00:00","cve":"CVE-2026-99745","urls":{"html":"https://cve.report/CVE-2026-99745","api":"https://cve.report/api/cve/CVE-2026-99745.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99745","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99745"},"summary":{"title":"x86/bugs: Select the BHI mitigation based on the attack vector properly","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nx86/bugs: Select the BHI mitigation based on the attack vector properly\n\nThe BHI mitigation selection is inconsistent with the documentation\n(attack_vector_controls.rst), which lists BHI under both the\nuser->kernel and guest->host attack vectors. bhi_select_mitigation()\nonly enables it when CPU_MITIGATE_GUEST_HOST is set; otherwise it\nselects BHI_MITIGATION_OFF, even if CPU_MITIGATE_USER_KERNEL is set.\n\nAs a result, a kernel compiled with KVM disabled gets BHI automatically\ndisabled, since CPU_MITIGATE_GUEST_HOST defaults to off without KVM.\nThis is a bug, given that CPU_MITIGATE_USER_KERNEL still needs it: on\naffected Intel CPUs these kernels lose BHI_DIS_S or the BHB clearing\nloop by default. Booting with mitigations=auto,no_guest_host has the\nsame effect.\n\nSelect BHI_MITIGATION_ON whenever user->kernel is mitigated, and keep\nBHI_MITIGATION_VMEXIT_ONLY for the guest->host-only case.\n\n  [ bp: Clarify commit title. ]","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:12","updated_at":"2026-11-20 06:18:12"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/3457b3bcd344005af894876cab4e634cabdcbb62","name":"https://git.kernel.org/stable/c/3457b3bcd344005af894876cab4e634cabdcbb62","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5bc572befb2990cb2ad83ca447f64e6654a9889f","name":"https://git.kernel.org/stable/c/5bc572befb2990cb2ad83ca447f64e6654a9889f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f9f2a155078cf7b10dd8b1ffdacf0a3aeb8baeb5","name":"https://git.kernel.org/stable/c/f9f2a155078cf7b10dd8b1ffdacf0a3aeb8baeb5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99745","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99745","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ddcd4d3cb37c8ad60cdbaaffe93f85e15e2babb5 f9f2a155078cf7b10dd8b1ffdacf0a3aeb8baeb5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ddcd4d3cb37c8ad60cdbaaffe93f85e15e2babb5 5bc572befb2990cb2ad83ca447f64e6654a9889f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ddcd4d3cb37c8ad60cdbaaffe93f85e15e2babb5 3457b3bcd344005af894876cab4e634cabdcbb62 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.17","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.17 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.64 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["arch/x86/kernel/cpu/bugs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"f9f2a155078cf7b10dd8b1ffdacf0a3aeb8baeb5","status":"affected","version":"ddcd4d3cb37c8ad60cdbaaffe93f85e15e2babb5","versionType":"git"},{"lessThan":"5bc572befb2990cb2ad83ca447f64e6654a9889f","status":"affected","version":"ddcd4d3cb37c8ad60cdbaaffe93f85e15e2babb5","versionType":"git"},{"lessThan":"3457b3bcd344005af894876cab4e634cabdcbb62","status":"affected","version":"ddcd4d3cb37c8ad60cdbaaffe93f85e15e2babb5","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/x86/kernel/cpu/bugs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.17"},{"lessThan":"6.17","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.64","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"6.17","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"6.17","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"6.17","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nx86/bugs: Select the BHI mitigation based on the attack vector properly\n\nThe BHI mitigation selection is inconsistent with the documentation\n(attack_vector_controls.rst), which lists BHI under both the\nuser->kernel and guest->host attack vectors. bhi_select_mitigation()\nonly enables it when CPU_MITIGATE_GUEST_HOST is set; otherwise it\nselects BHI_MITIGATION_OFF, even if CPU_MITIGATE_USER_KERNEL is set.\n\nAs a result, a kernel compiled with KVM disabled gets BHI automatically\ndisabled, since CPU_MITIGATE_GUEST_HOST defaults to off without KVM.\nThis is a bug, given that CPU_MITIGATE_USER_KERNEL still needs it: on\naffected Intel CPUs these kernels lose BHI_DIS_S or the BHB clearing\nloop by default. Booting with mitigations=auto,no_guest_host has the\nsame effect.\n\nSelect BHI_MITIGATION_ON whenever user->kernel is mitigated, and keep\nBHI_MITIGATION_VMEXIT_ONLY for the guest->host-only case.\n\n  [ bp: Clarify commit title. ]"}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:16.811Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/f9f2a155078cf7b10dd8b1ffdacf0a3aeb8baeb5"},{"url":"https://git.kernel.org/stable/c/5bc572befb2990cb2ad83ca447f64e6654a9889f"},{"url":"https://git.kernel.org/stable/c/3457b3bcd344005af894876cab4e634cabdcbb62"}],"title":"x86/bugs: Select the BHI mitigation based on the attack vector properly","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99745","datePublished":"2026-11-20T05:51:16.811Z","dateReserved":"2026-09-25T10:25:14.432Z","dateUpdated":"2026-11-20T05:51:16.811Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:12","lastModifiedDate":"2026-11-20 06:18:12","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99745","Ordinal":"1","Title":"x86/bugs: Select the BHI mitigation based on the attack vector p","CVE":"CVE-2026-99745","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99745","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nx86/bugs: Select the BHI mitigation based on the attack vector properly\n\nThe BHI mitigation selection is inconsistent with the documentation\n(attack_vector_controls.rst), which lists BHI under both the\nuser->kernel and guest->host attack vectors. bhi_select_mitigation()\nonly enables it when CPU_MITIGATE_GUEST_HOST is set; otherwise it\nselects BHI_MITIGATION_OFF, even if CPU_MITIGATE_USER_KERNEL is set.\n\nAs a result, a kernel compiled with KVM disabled gets BHI automatically\ndisabled, since CPU_MITIGATE_GUEST_HOST defaults to off without KVM.\nThis is a bug, given that CPU_MITIGATE_USER_KERNEL still needs it: on\naffected Intel CPUs these kernels lose BHI_DIS_S or the BHB clearing\nloop by default. Booting with mitigations=auto,no_guest_host has the\nsame effect.\n\nSelect BHI_MITIGATION_ON whenever user->kernel is mitigated, and keep\nBHI_MITIGATION_VMEXIT_ONLY for the guest->host-only case.\n\n  [ bp: Clarify commit title. ]","Type":"Description","Title":"x86/bugs: Select the BHI mitigation based on the attack vector p"}]}}}