CVE-2026-98716KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 12 days later
· 12 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b2ac58f90540e39324e7a29a7ad471407ae0bf48 – < 001c78bc64389cabe4f9015ab3942ec9c3592caa
- affected b2ac58f90540e39324e7a29a7ad471407ae0bf48 – < 552a110c403f1a61eba0bf71519c6585d9d4242d
- affected b2ac58f90540e39324e7a29a7ad471407ae0bf48 – < 0e79ebf6f92a7d15187aede44204fa04b93e474c
- affected b2ac58f90540e39324e7a29a7ad471407ae0bf48 – < 84da7a0e92207444d9cbfe69965e17db29008f27
- affected b2ac58f90540e39324e7a29a7ad471407ae0bf48 – < 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2
- affected b2ac58f90540e39324e7a29a7ad471407ae0bf48 – < 318ef696fa3c712e46bb62a1a828c3cd62f390c3
- affected b2ac58f90540e39324e7a29a7ad471407ae0bf48 – < 55865b3ae03705aa39198783b9cb1f8b96eb44e4
- affected b2ac58f90540e39324e7a29a7ad471407ae0bf48 – < 9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85
- affected f54d0bb8487d2f016fbc4f0e38ef9098f8eb8bd4
- affected 89be8950bab799ddb9cc3777345e3c21bcb32dba
- affected 3.16.57 – < 3.17
- affected 4.4.168 – < 4.5
- affected 4.16
- unaffected < 4.16
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.56 – ≤ 6.18.*
- unaffected 7.2.10 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/001c78bc64389cabe4f9015ab3942ec9c3592caa (opens in a new tab)
- https://git.kernel.org/stable/c/552a110c403f1a61eba0bf71519c6585d9d4242d (opens in a new tab)
- https://git.kernel.org/stable/c/0e79ebf6f92a7d15187aede44204fa04b93e474c (opens in a new tab)
- https://git.kernel.org/stable/c/84da7a0e92207444d9cbfe69965e17db29008f27 (opens in a new tab)
- https://git.kernel.org/stable/c/74836ae4785b9754bb36d0b18fcc1dec4e5e98d2 (opens in a new tab)
- https://git.kernel.org/stable/c/318ef696fa3c712e46bb62a1a828c3cd62f390c3 (opens in a new tab)
- https://git.kernel.org/stable/c/55865b3ae03705aa39198783b9cb1f8b96eb44e4 (opens in a new tab)
- https://git.kernel.org/stable/c/9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103970 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98716)Record last updated .