<?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:40:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89727 — KVM: arm64: GICv2: Don't WARN on out-of-range GICV_DIR INTID</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89727</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: arm64: GICv2: Don&amp;#39;t WARN on out-of-range GICV_DIR INTID&lt;/p&gt;
&lt;p&gt;vgic_v2_deactivate() passes the INTID a guest wrote to GICV_DIR straight
to vgic_get_vcpu_irq(), and treats a failed lookup as a &amp;#34;can&amp;#39;t happen&amp;#34;
condition with WARN_ON_ONCE().&lt;/p&gt;
&lt;p&gt;The guest can make it happen at will, though: for any INTID outside of
the implemented SGI, PPI and SPI ranges the lookup returns NULL, since
GICv2 has no LPIs. A guest running with EOImode==1 writing such an INTID
to GICV_DIR triggers the WARN, and panics hosts running with
panic_on_warn.&lt;/p&gt;
&lt;p&gt;Drop the WARN and ignore failed lookups.&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: arm64: GICv2: Don&amp;#39;t WARN on out-of-range GICV_DIR INTID&lt;/p&gt;
&lt;p&gt;vgic_v2_deactivate() passes the INTID a guest wrote to GICV_DIR straight
to vgic_get_vcpu_irq(), and treats a failed lookup as a &amp;#34;can&amp;#39;t happen&amp;#34;
condition with WARN_ON_ONCE().&lt;/p&gt;
&lt;p&gt;The guest can make it happen at will, though: for any INTID outside of
the implemented SGI, PPI and SPI ranges the lookup returns NULL, since
GICv2 has no LPIs. A guest running with EOImode==1 writing such an INTID
to GICV_DIR triggers the WARN, and panics hosts running with
panic_on_warn.&lt;/p&gt;
&lt;p&gt;Drop the WARN and ignore failed lookups.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89727</guid>
    </item>
  </channel>
</rss>
