<?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://vulnerability.circl.lu</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, 29 Sep 2026 13:11:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53277 — KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53277</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation&lt;/p&gt;
&lt;p&gt;walk_s1() and kvm_walk_nested_s2() expect to be called while holding
kvm-&amp;gt;srcu to guard against memslot changes. While this is generally
the case, __kvm_at_s12() and __kvm_find_s1_desc_level() call into the
respective walkers without taking kvm-&amp;gt;srcu.&lt;/p&gt;
&lt;p&gt;Fix by acquiring kvm-&amp;gt;srcu prior to the table walk in both instances.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation&lt;/p&gt;
&lt;p&gt;walk_s1() and kvm_walk_nested_s2() expect to be called while holding
kvm-&amp;gt;srcu to guard against memslot changes. While this is generally
the case, __kvm_at_s12() and __kvm_find_s1_desc_level() call into the
respective walkers without taking kvm-&amp;gt;srcu.&lt;/p&gt;
&lt;p&gt;Fix by acquiring kvm-&amp;gt;srcu prior to the table walk in both instances.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53277</guid>
    </item>
  </channel>
</rss>
