<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 10:09:15 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99082</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99082</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-99082</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1473 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</link>
      <description>certfr-2026-avi-1473</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</guid>
    </item>
    <item>
      <title>EUVD-2026-396164</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396164</link>
      <description>EUVD-2026-396164</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396164</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99082</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99082</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-99082</guid>
    </item>
    <item>
      <title>GHSA-58r9-ch9w-px7w</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-58r9-ch9w-px7w</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-58r9-ch9w-px7w</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99082 — KVM: x86: Use active memslots for the per-vCPU MMIO cache</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99082</link>
      <description>msrc_CVE-2026-99082</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99082</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99082</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99082</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 257 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use active memslots for the per-vCPU MMIO cache 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. 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. 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. 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. Use the vCPU&amp;#39;s active memslots when caching and validating the entry. Memslot generations are unique across address…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 257 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use active memslots for the per-vCPU MMIO cache 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. 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. 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. 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. Use the vCPU&amp;#39;s active memslots when caching and validating the entry. Memslot generations are unique across address…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99082</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
