<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Nov 2026 23:39:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99082 — KVM: x86: Use active memslots for the per-vCPU MMIO cache</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99082</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: x86: Use active memslots for the per-vCPU MMIO cache&lt;/p&gt;
&lt;p&gt;KVM tags the per-vCPU MMIO cache with a memslot generation so that a
memslot update invalidates cached MMIO information.  Both the fill and
validation paths use kvm_memslots(), which unconditionally selects address
space 0, even when the vCPU is running in SMM and using address space 1.&lt;/p&gt;
&lt;p&gt;Commit 56f17dd3fbc4 (&amp;#34;kvm: x86: fix stale mmio cache bug&amp;#34;) added the
memslot generation to the cache key so that a memslot update could not
leave a stale entry valid.  When commit 699023e23965 (&amp;#34;KVM: x86: add SMM
to the MMU role, support SMRAM address space&amp;#34;) added the SMM address space,
these helpers were not converted to use the active memslots.&lt;/p&gt;
&lt;p&gt;Consequently, an update to the SMM memslots can leave an entry from the old
SMM address space apparently valid after the vCPU returns to the normal
address space.  A guest can then cause an access to valid RAM at the same
GFN to be returned to userspace as KVM_EXIT_MMIO.&lt;/p&gt;
&lt;p&gt;Completing that exit through the VMM&amp;#39;s RAM address space writes the backing
page without going through KVM&amp;#39;s write-tracking path.  If the page backs a
nested EPT table, KVM can continue using shadow translations derived from
the old contents.  The WARN_ON_ONCE() in kvm_mmu_write_protect_fault()
catches this invalid cache and memslot combination.&lt;/p&gt;
&lt;p&gt;Use the vCPU&amp;#39;s active memslots when caching and validating the entry.
Memslot generations are unique across a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: x86: Use active memslots for the per-vCPU MMIO cache&lt;/p&gt;
&lt;p&gt;KVM tags the per-vCPU MMIO cache with a memslot generation so that a
memslot update invalidates cached MMIO information.  Both the fill and
validation paths use kvm_memslots(), which unconditionally selects address
space 0, even when the vCPU is running in SMM and using address space 1.&lt;/p&gt;
&lt;p&gt;Commit 56f17dd3fbc4 (&amp;#34;kvm: x86: fix stale mmio cache bug&amp;#34;) added the
memslot generation to the cache key so that a memslot update could not
leave a stale entry valid.  When commit 699023e23965 (&amp;#34;KVM: x86: add SMM
to the MMU role, support SMRAM address space&amp;#34;) added the SMM address space,
these helpers were not converted to use the active memslots.&lt;/p&gt;
&lt;p&gt;Consequently, an update to the SMM memslots can leave an entry from the old
SMM address space apparently valid after the vCPU returns to the normal
address space.  A guest can then cause an access to valid RAM at the same
GFN to be returned to userspace as KVM_EXIT_MMIO.&lt;/p&gt;
&lt;p&gt;Completing that exit through the VMM&amp;#39;s RAM address space writes the backing
page without going through KVM&amp;#39;s write-tracking path.  If the page backs a
nested EPT table, KVM can continue using shadow translations derived from
the old contents.  The WARN_ON_ONCE() in kvm_mmu_write_protect_fault()
catches this invalid cache and memslot combination.&lt;/p&gt;
&lt;p&gt;Use the vCPU&amp;#39;s active memslots when caching and validating the entry.
Memslot generations are unique across a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99082</guid>
    </item>
    <item>
      <title>USN-9166-1 — linux, linux-aws, linux-gcp, linux-gcp-7.0, linux-gke, linux-ibm, linux-oem-7.0, linux-vmware vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-9166-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-vmware&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - FireWire subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - I2C subsystem;
  - Multiple devices driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Power supply drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - TCM subsystem;
  - UFS subsystem;
  - File systems infrastructure;
  - Ext4 file system;
  - File system notification infrastructure;
  - NTFS3 file system;
  - OCFS2 file system;
  - SMB network file system;
  - Tracing file system;
  - XFS file system;
  - Kernel futex primitives;
  - Key management;
  - Key Management;
  - VMware vSockets driver;
  - io_uring subsystem;
  - IPC subsystem;
  - Perf events;
  - Kernel exit() syscall;
  - PID namespace;
  - printk logging mechanism;
  - Scheduler infrastructure;
  - Tracing infrastructure;
  - Watch queue notification mechanism;
  - Workqueue subsystem;
  - Ethernet bridge;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - IUCV driver;
  - IEEE 802.15.4 subsystem;
  - Netfilter;
  - Netlink;
  - RDS protocol;
  - Network traffic control;
  - SCTP protocol;
  - TIPC protocol;
  - SELinux security module;
  - SOF drivers;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-vmware&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - FireWire subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - I2C subsystem;
  - Multiple devices driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Power supply drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - TCM subsystem;
  - UFS subsystem;
  - File systems infrastructure;
  - Ext4 file system;
  - File system notification infrastructure;
  - NTFS3 file system;
  - OCFS2 file system;
  - SMB network file system;
  - Tracing file system;
  - XFS file system;
  - Kernel futex primitives;
  - Key management;
  - Key Management;
  - VMware vSockets driver;
  - io_uring subsystem;
  - IPC subsystem;
  - Perf events;
  - Kernel exit() syscall;
  - PID namespace;
  - printk logging mechanism;
  - Scheduler infrastructure;
  - Tracing infrastructure;
  - Watch queue notification mechanism;
  - Workqueue subsystem;
  - Ethernet bridge;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - IUCV driver;
  - IEEE 802.15.4 subsystem;
  - Netfilter;
  - Netlink;
  - RDS protocol;
  - Network traffic control;
  - SCTP protocol;
  - TIPC protocol;
  - SELinux security module;
  - SOF drivers;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-9166-1</guid>
    </item>
  </channel>
</rss>
