<?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, 06 Oct 2026 19:22:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-31143 — double unlock in x86 guest IRQ handling</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-31143</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Xen&lt;/p&gt;
&lt;p&gt;An optional feature of PCI MSI called &amp;#34;Multiple Message&amp;#34; allows a
device to use multiple consecutive interrupt vectors.  Unlike for MSI-X,
the setting up of these consecutive vectors needs to happen all in one
go.  In this handling an error path could be taken in different
situations, with or without a particular lock held.  This error path
wrongly releases the lock even when it is not currently held.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Xen&lt;/p&gt;
&lt;p&gt;An optional feature of PCI MSI called &amp;#34;Multiple Message&amp;#34; allows a
device to use multiple consecutive interrupt vectors.  Unlike for MSI-X,
the setting up of these consecutive vectors needs to happen all in one
go.  In this handling an error path could be taken in different
situations, with or without a particular lock held.  This error path
wrongly releases the lock even when it is not currently held.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-31143</guid>
    </item>
  </channel>
</rss>
