Strix
73.1K

CVE-2026-98716

UnknownEPSS 0.17%

Last modified

CVE-2026-98716 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12. Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12. Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.

Metrics

EPSS Probability
0.17%

6.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= b2ac58f90540e39324e7a29a7ad471407ae0bf48, < 001c78bc64389cabe4f9015ab3942ec9c3592caa; >= b2ac58f90540e39324e7a29a7ad471407ae0bf48, < 552a110c403f1a61eba0bf71519c6585d9d4242d; >= b2ac58f90540e39324e7a29a7ad471407ae0bf48, < 0e79ebf6f92a7d15187aede44204fa04b93e474c; >= b2ac58f90540e39324e7a29a7ad471407ae0bf48, < 84da7a0e92207444d9cbfe69965e17db29008f27; >= b2ac58f90540e39324e7a29a7ad471407ae0bf48, < 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2; >= b2ac58f90540e39324e7a29a7ad471407ae0bf48, < 318ef696fa3c712e46bb62a1a828c3cd62f390c3; >= b2ac58f90540e39324e7a29a7ad471407ae0bf48, < 55865b3ae03705aa39198783b9cb1f8b96eb44e4; >= b2ac58f90540e39324e7a29a7ad471407ae0bf48, < 9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85; f54d0bb8487d2f016fbc4f0e38ef9098f8eb8bd4; 89be8950bab799ddb9cc3777345e3c21bcb32dba; >= 3.16.57, < 3.17; >= 4.4.168, < 4.5
LinuxLinux4.16

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98716?
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12. Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.
How severe is CVE-2026-98716?
Severity scoring for CVE-2026-98716 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-98716?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-98716?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST