https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 12 Nov 2026 06:37:27 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1469 certfr-2026-avi-1469 https://db.gcve.eu/vuln/certfr-2026-avi-1469 https://db.gcve.eu/vuln/fkie_cve-2026-98472 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV</p> <p>Unconditionally free SEV&#39;s &#34;have run CPUs&#34; cpumask in the VM destroy path, i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV VM if its state is intra-host migrated. Alternatively, the mask could be freed in sev_migrate_from() when &#34;converting&#34; the source VM, but that gets annoying because ideally KVM would nullify the mask to guard against UAF, and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y.</p> <p>Freeing the mask during sev_migrate_from() is also not robust against other KVM bugs, though that&#39;s kind of a moot point since any such bugs would show up even if sev-&gt;active is never set. I.e. KVM must get that side of things correct. But, that&#39;s not a great reason to add more code just to make things marginally less robust.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV</p> <p>Unconditionally free SEV&#39;s &#34;have run CPUs&#34; cpumask in the VM destroy path, i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV VM if its state is intra-host migrated. Alternatively, the mask could be freed in sev_migrate_from() when &#34;converting&#34; the source VM, but that gets annoying because ideally KVM would nullify the mask to guard against UAF, and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y.</p> <p>Freeing the mask during sev_migrate_from() is also not robust against other KVM bugs, though that&#39;s kind of a moot point since any such bugs would show up even if sev-&gt;active is never set. I.e. KVM must get that side of things correct. But, that&#39;s not a great reason to add more code just to make things marginally less robust.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98472 https://db.gcve.eu/vuln/ghsa-qccv-gmm4-2g2g <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV</p> <p>Unconditionally free SEV&#39;s &#34;have run CPUs&#34; cpumask in the VM destroy path, i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV VM if its state is intra-host migrated. Alternatively, the mask could be freed in sev_migrate_from() when &#34;converting&#34; the source VM, but that gets annoying because ideally KVM would nullify the mask to guard against UAF, and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y.</p> <p>Freeing the mask during sev_migrate_from() is also not robust against other KVM bugs, though that&#39;s kind of a moot point since any such bugs would show up even if sev-&gt;active is never set. I.e. KVM must get that side of things correct. But, that&#39;s not a great reason to add more code just to make things marginally less robust.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV</p> <p>Unconditionally free SEV&#39;s &#34;have run CPUs&#34; cpumask in the VM destroy path, i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV VM if its state is intra-host migrated. Alternatively, the mask could be freed in sev_migrate_from() when &#34;converting&#34; the source VM, but that gets annoying because ideally KVM would nullify the mask to guard against UAF, and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y.</p> <p>Freeing the mask during sev_migrate_from() is also not robust against other KVM bugs, though that&#39;s kind of a moot point since any such bugs would show up even if sev-&gt;active is never set. I.e. KVM must get that side of things correct. But, that&#39;s not a great reason to add more code just to make things marginally less robust.</p> https://db.gcve.eu/vuln/ghsa-qccv-gmm4-2g2g https://db.gcve.eu/vuln/msrc_cve-2026-98472 msrc_CVE-2026-98472 https://db.gcve.eu/vuln/msrc_cve-2026-98472 https://db.gcve.eu/vuln/ubuntu-cve-2026-98472 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 121 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV Unconditionally free SEV&#39;s &#34;have run CPUs&#34; cpumask in the VM destroy path, i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV VM if its state is intra-host migrated. Alternatively, the mask could be freed in sev_migrate_from() when &#34;converting&#34; the source VM, but that gets annoying because ideally KVM would nullify the mask to guard against UAF, and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y. Freeing the mask during sev_migrate_from() is also not robust against other KVM bugs, though that&#39;s kind of a moot point since any such bugs would show up even if sev-&gt;active is never set. I.e. KVM must get that side of things correct. But, that&#39;s not a great reason to add more code just to make things marginally less robust.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 121 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV Unconditionally free SEV&#39;s &#34;have run CPUs&#34; cpumask in the VM destroy path, i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV VM if its state is intra-host migrated. Alternatively, the mask could be freed in sev_migrate_from() when &#34;converting&#34; the source VM, but that gets annoying because ideally KVM would nullify the mask to guard against UAF, and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y. Freeing the mask during sev_migrate_from() is also not robust against other KVM bugs, though that&#39;s kind of a moot point since any such bugs would show up even if sev-&gt;active is never set. I.e. KVM must get that side of things correct. But, that&#39;s not a great reason to add more code just to make things marginally less robust.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98472