Answer in brief
CVE-2026-98716 records a Unknown severity vulnerability in KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b2ac58f90540e39324e7a29a7ad471407ae0bf48 <74836ae4785b9754bb36d0b18fcc1dec4e5e98d2 || >=b2ac58f90540e39324e7a29a7ad471407ae0bf48 <318ef696fa3c712e46bb62a1a828c3cd62f390c3 || >=b2ac58f90540e39324e7a29a7ad471407ae0bf48 <55865b3ae03705aa39198783b9cb1f8b96eb44e4 || >=b2ac58f90540e39324e7a29a7ad471407ae0bf48 <9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85 || f54d0bb8487d2f016fbc4f0e38ef9098f8eb8bd4 || 89be8950bab799ddb9cc3777345e3c21bcb32dba || >=3.16.57 <3.17 || >=4.4.168 <4.5 | 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2, 318ef696fa3c712e46bb62a1a828c3cd62f390c3, 55865b3ae03705aa39198783b9cb1f8b96eb44e4, 9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85, 3.17, 4.5 |
| Linux/Linuxgeneric | 4.16 | Not reported |
| Linux/Linuxgeneric | >=b2ac58f90540e39324e7a29a7ad471407ae0bf48 <84da7a0e92207444d9cbfe69965e17db29008f27 || >=b2ac58f90540e39324e7a29a7ad471407ae0bf48 <74836ae4785b9754bb36d0b18fcc1dec4e5e98d2 || >=b2ac58f90540e39324e7a29a7ad471407ae0bf48 <318ef696fa3c712e46bb62a1a828c3cd62f390c3 || >=b2ac58f90540e39324e7a29a7ad471407ae0bf48 <55865b3ae03705aa39198783b9cb1f8b96eb44e4 || >=b2ac58f90540e39324e7a29a7ad471407ae0bf48 <9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85 || f54d0bb8487d2f016fbc4f0e38ef9098f8eb8bd4 || 89be8950bab799ddb9cc3777345e3c21bcb32dba || >=3.16.57 <3.17 || >=4.4.168 <4.5 | 84da7a0e92207444d9cbfe69965e17db29008f27, 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2, 318ef696fa3c712e46bb62a1a828c3cd62f390c3, 55865b3ae03705aa39198783b9cb1f8b96eb44e4, 9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85, 3.17, 4.5 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.