CVE-2026-98716: KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 001c78bc64389cabe4f9015ab3942ec9c3592caa, 0e79ebf6f92a7d15187aede44204fa04b93e474c, 3.17; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
Low priority for now. Upgrade to Linux Linux 001c78bc64389cabe4f9015ab3942ec9c3592caa, 0e79ebf6f92a7d15187aede44204fa04b93e474c, 3.17; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- f54d0bb8487d2f016fbc4f0e38ef9098f8eb8bd4, 89be8950bab799ddb9cc3777345e3c21bcb32dba, 4.16affected
- b2ac58f90540e39324e7a29a7ad471407ae0bf48 and later · before 001c78bc64389cabe4f9015ab3942ec9c3592caaaffected · git
- b2ac58f90540e39324e7a29a7ad471407ae0bf48 and later · before 552a110c403f1a61eba0bf71519c6585d9d4242daffected · git
- b2ac58f90540e39324e7a29a7ad471407ae0bf48 and later · before 0e79ebf6f92a7d15187aede44204fa04b93e474caffected · git
- b2ac58f90540e39324e7a29a7ad471407ae0bf48 and later · before 84da7a0e92207444d9cbfe69965e17db29008f27affected · git
- b2ac58f90540e39324e7a29a7ad471407ae0bf48 and later · before 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2affected · git
- b2ac58f90540e39324e7a29a7ad471407ae0bf48 and later · before 318ef696fa3c712e46bb62a1a828c3cd62f390c3affected · git
- b2ac58f90540e39324e7a29a7ad471407ae0bf48 and later · before 55865b3ae03705aa39198783b9cb1f8b96eb44e4affected · git
- b2ac58f90540e39324e7a29a7ad471407ae0bf48 and later · before 9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85affected · git
- 3.16.57 and later · before 3.17affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98714Oct 18, 2026 · KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded0Monitor
- ← EarlierCVE-2026-98715Oct 18, 2026 · KVM: SVM: Preserve TLB control (i.e. pending TLB flush) on failed VMRUN0Monitor
- Later →CVE-2026-98717Oct 18, 2026 · KVM: x86/mmu: Bail from shadow walks if the root is invalid or a dummy0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 001c78bc64389cabe4f9015ab3942ec9c3592caa | Vendor (CNA) |
| Linux Linux | 0e79ebf6f92a7d15187aede44204fa04b93e474c | Vendor (CNA) |
| Linux Linux | 3.17 | Vendor (CNA) |
| Linux Linux | 318ef696fa3c712e46bb62a1a828c3cd62f390c3 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 552a110c403f1a61eba0bf71519c6585d9d4242d | Vendor (CNA) |
| Linux Linux | 55865b3ae03705aa39198783b9cb1f8b96eb44e4 | Vendor (CNA) |
| Linux Linux | 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2 | Vendor (CNA) |
| Linux Linux | 84da7a0e92207444d9cbfe69965e17db29008f27 | Vendor (CNA) |
| Linux Linux | 9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+20 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/0e79ebf6f92a7d15187aede44204fa04b93e474c
- git.kernel.org/stable/c/318ef696fa3c712e46bb62a1a828c3cd62f390c3
- git.kernel.org/stable/c/552a110c403f1a61eba0bf71519c6585d9d4242d
- git.kernel.org/stable/c/55865b3ae03705aa39198783b9cb1f8b96eb44e4
- git.kernel.org/stable/c/74836ae4785b9754bb36d0b18fcc1dec4e5e98d2
- git.kernel.org/stable/c/84da7a0e92207444d9cbfe69965e17db29008f27
- git.kernel.org/stable/c/9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85
Vendor advisories and official records. Exploit/PoC links are deliberately left out.