<?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>Thu, 08 Oct 2026 19:14:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64561 — KVM: x86: Check for invalid/obsolete root *after* making MMU pages available</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-64561</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: Check for invalid/obsolete root *after* making MMU pages available&lt;/p&gt;
&lt;p&gt;Check for a &amp;#34;stale&amp;#34; page fault, i.e. for an invalid and/or obsolete root,
after making MMU pages available for the shadow MMU.  If reclaiming shadow
pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to
map memory into an invalid root.  On its own, populating an invalid root is
&amp;#34;fine&amp;#34;, but because child shadow pages inherit their parent&amp;#39;s role, any
children created during the map/fetch will be created as invalid pages,
thus violating KVM&amp;#39;s invariant that invalid pages are never on the list of
active MMU pages.&lt;/p&gt;
&lt;p&gt;Note, the underlying flaw has existed since KVM first started tracking
invalid roots in 2008 (commit 2e53d63acba7, &amp;#34;KVM: MMU: ignore zapped root
pagetables&amp;#34;), but the true badness only came along in 2020 (Linux 5.9)
with the invariant that invalid shadow pages can&amp;#39;t be on the list of
active pages.&lt;/p&gt;
&lt;p&gt;Note #2, inheriting role.invalid when creating child shadow pages is also
far from ideal; that flaw will be addressed separately.&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: Check for invalid/obsolete root *after* making MMU pages available&lt;/p&gt;
&lt;p&gt;Check for a &amp;#34;stale&amp;#34; page fault, i.e. for an invalid and/or obsolete root,
after making MMU pages available for the shadow MMU.  If reclaiming shadow
pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to
map memory into an invalid root.  On its own, populating an invalid root is
&amp;#34;fine&amp;#34;, but because child shadow pages inherit their parent&amp;#39;s role, any
children created during the map/fetch will be created as invalid pages,
thus violating KVM&amp;#39;s invariant that invalid pages are never on the list of
active MMU pages.&lt;/p&gt;
&lt;p&gt;Note, the underlying flaw has existed since KVM first started tracking
invalid roots in 2008 (commit 2e53d63acba7, &amp;#34;KVM: MMU: ignore zapped root
pagetables&amp;#34;), but the true badness only came along in 2020 (Linux 5.9)
with the invariant that invalid shadow pages can&amp;#39;t be on the list of
active pages.&lt;/p&gt;
&lt;p&gt;Note #2, inheriting role.invalid when creating child shadow pages is also
far from ideal; that flaw will be addressed separately.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-64561</guid>
    </item>
    <item>
      <title>RHSA-2026:45114 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:45114</link>
      <description>&lt;p&gt;kernel: fs/notify: call exportfs_encode_fid with s_umount kernel: scsi: core: Wake up the error handler when final completions race against each other kernel: rtnetlink: add missing netlink_ns_capable() check for peer netns kernel: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels kernel: futex: Drop CLONE_THREAD requirement for private default hash alloc kernel: dm log: fix out-of-bounds write due to region_count overflow kernel: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: fs/notify: call exportfs_encode_fid with s_umount kernel: scsi: core: Wake up the error handler when final completions race against each other kernel: rtnetlink: add missing netlink_ns_capable() check for peer netns kernel: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels kernel: futex: Drop CLONE_THREAD requirement for private default hash alloc kernel: dm log: fix out-of-bounds write due to region_count overflow kernel: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:45114</guid>
    </item>
    <item>
      <title>RHSA-2026:45116 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:45116</link>
      <description>&lt;p&gt;kernel: KVM: x86: Don&amp;#39;t (re)check L1 intercepts when completing userspace I/O kernel: tipc: fix double-free in tipc_buf_append() kernel: dm log: fix out-of-bounds write due to region_count overflow kernel: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: KVM: x86: Don&amp;#39;t (re)check L1 intercepts when completing userspace I/O kernel: tipc: fix double-free in tipc_buf_append() kernel: dm log: fix out-of-bounds write due to region_count overflow kernel: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:45116</guid>
    </item>
  </channel>
</rss>
