Skip to main content
VulnerabilityPublished Updated

CVE-2026-98716: Linux kernel · KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2, 55865b3ae03705aa39198783b9cb1f8b96eb44e4, 318ef696fa3c712e46bb62a1a828c3cd62f390c3 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=3.16.57 <3.17
  • >=4.4.168 <4.5
Fixed in
  • 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2
  • 55865b3ae03705aa39198783b9cb1f8b96eb44e4
  • 318ef696fa3c712e46bb62a1a828c3cd62f390c3
  • 84da7a0e92207444d9cbfe69965e17db29008f27
  • 9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85
  • 4.5
  • 3.17
LinuxLinuxAffected
  • =4.16
Fixed in–

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.

References

Community reviews

Loading reviews…