CVE-2025-40300

x86/vmscape: Add conditional IBPB mitigation

MEDIUM
5.5
CVSS Score
Published: September 11, 2025 at 04:49 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
6 products affected across 3 vendorsLinux KernelDebian LinuxSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: x86/vmscape: Add conditional IBPB mitigation VMSCAPE is a vulnerability that exploits insufficient branch predictor isolation between a guest and a userspace hypervisor (like QEMU). Existing mitigations already protect kernel/KVM from a malicious guest. Userspace can additionally be protected by flushing the branch predictors after a VMexit. Since it is the userspace that consumes the poisoned branch predictors, conditionally issue an IBPB after a VMexit and before returning to userspace. Workloads that frequently switch between hypervisor and userspace will incur the most overhead from the new IBPB. This new IBPB is not integrated with the existing IBPB sites. For instance, a task can use the existing speculation control prctl() to get an IBPB at context switch time. With this implementation, the IBPB is doubled up: one at context switch and another before running userspace. The intent is to integrate and optimize these cases post-embargo. [ dhansen: elaborate on suboptimal IBPB solution ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.16.57 ≤ v < 3.174.16 ≤ v < 5.10.2444.4.168 ≤ v < 4.55.11 ≤ v < 5.15.1935.16 ≤ v < 6.1.1526.13 ≤ v < 6.16.76.2 ≤ v < 6.6.1066.7 ≤ v < 6.12.4715d45071523d89b3fb7372e2135fbd72f6af95063.16.574.4.1684b3870c343a82cd2df7192cc5149c87205dcc6116.176.17 rc16.17 rc26.17 rc36.17 rc46.17 rc5c51f1e5f57cca88d8d5894b6fad1638f643a99d0
Vendor states this is fixed in 15006289e5c38b2a830e1fba221977a27598176c (fixed)
Vendor states this is fixed in 2f4f2f8f860cb4c3336a7435ebe8dcfded0c9c6e (fixed)
Vendor states this is fixed in 2f8f173413f1cbf52660d04df92d0069c4306d25 (fixed)
Vendor states this is fixed in 34e5667041050711a947e260fc9ebebe08bddee5 (fixed)
Vendor states this is fixed in 459274c77b37ac63b78c928b4b4e748d1f9d05c8 (fixed)
Vendor states this is fixed in 510603f504796c3535f67f55fb0b124a303b44c8 (fixed)
Vendor states this is fixed in 893387c18612bb452336a5881da0d015a7e8f4a2 (fixed)
Vendor states this is fixed in 9c23a90648e831d611152ac08dbcd1283d405e7f (fixed)
Vendor states this is fixed in ac60717f9a8d21c58617d0b34274babf24135835 (fixed)
Vendor states this is fixed in c08192b5d6730a914dee6175bc71092ee6a65f14 (fixed)
Vendor states this is fixed in d5490dfa35427a2967e00a4c7a1b95fdbc8ede34 (fixed)
Vendor states this is fixed in d7ddc93392e4a7ffcccc86edf6ef3e64c778db52 (fixed)
Vendor states this is fixed in f866eef8d1c65504d30923c3f14082ad294d0e6d (fixed)
Affected range stops below 3.17, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.16 (unaffected)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.244 (unaffected)
Vendor states this is fixed in 5.15.193 (unaffected)
Vendor states this is fixed in 6.1.152 (unaffected)
Vendor states this is fixed in 6.12.47 (unaffected)
Vendor states this is fixed in 6.16.7 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.6.106 (unaffected)
v < V5.0
Affected range stops below V5.0, so it looks safe — our inference, not a vendor statement

References (23)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/15006289e5c38b2a830e1fba221977a27598176c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2f4f2f8f860cb4c3336a7435ebe8dcfded0c9c6e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2f8f173413f1cbf52660d04df92d0069c4306d25
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/34e5667041050711a947e260fc9ebebe08bddee5
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/459274c77b37ac63b78c928b4b4e748d1f9d05c8
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/510603f504796c3535f67f55fb0b124a303b44c8
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/893387c18612bb452336a5881da0d015a7e8f4a2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9c23a90648e831d611152ac08dbcd1283d405e7f

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card