https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 01 Nov 2026 23:40:29 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1375 certfr-2026-avi-1375 https://db.gcve.eu/vuln/certfr-2026-avi-1375 https://db.gcve.eu/vuln/fkie_cve-2026-98716 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SVM: Use the active VMCB&#39;s MSR bitmap when checking if MSR is intercepted</p> <p>Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02&#39;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.</p> <p>Don&#39;t bother tracking the virtual address of the bitmap that&#39;s being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SVM: Use the active VMCB&#39;s MSR bitmap when checking if MSR is intercepted</p> <p>Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02&#39;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.</p> <p>Don&#39;t bother tracking the virtual address of the bitmap that&#39;s being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98716 https://db.gcve.eu/vuln/ghsa-hpgm-5w85-35mm <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SVM: Use the active VMCB&#39;s MSR bitmap when checking if MSR is intercepted</p> <p>Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02&#39;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.</p> <p>Don&#39;t bother tracking the virtual address of the bitmap that&#39;s being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SVM: Use the active VMCB&#39;s MSR bitmap when checking if MSR is intercepted</p> <p>Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02&#39;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.</p> <p>Don&#39;t bother tracking the virtual address of the bitmap that&#39;s being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.</p> https://db.gcve.eu/vuln/ghsa-hpgm-5w85-35mm https://db.gcve.eu/vuln/msrc_cve-2026-98716 msrc_CVE-2026-98716 https://db.gcve.eu/vuln/msrc_cve-2026-98716 https://db.gcve.eu/vuln/ubuntu-cve-2026-98716 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-kvm, Ubuntu:Pro:FIPS-updates:16.04:LTS: linux-fips, Ubuntu:Pro:FIPS:16.04:LTS: linux-fips, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 226 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Use the active VMCB&#39;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&#39;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&#39;t bother tracking the virtual address of the bitmap that&#39;s being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-kvm, Ubuntu:Pro:FIPS-updates:16.04:LTS: linux-fips, Ubuntu:Pro:FIPS:16.04:LTS: linux-fips, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 226 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Use the active VMCB&#39;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&#39;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&#39;t bother tracking the virtual address of the bitmap that&#39;s being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98716