<?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>Wed, 30 Sep 2026 06:44:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93097 — cxl/mbox: Break poison list loop on an empty payload</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93097</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;cxl/mbox: Break poison list loop on an empty payload&lt;/p&gt;
&lt;p&gt;A device that returns count == 0 with CXL_POISON_FLAG_MORE set on every
iteration never advances nr_records, so the max_errors guard never
trips and the do/while loops forever while holding poison.mutex. That
hangs the sysfs-triggered scan thread and blocks all subsequent poison
operations on the device. The existing &amp;#34;Protect against an uncleared
_FLAG_MORE&amp;#34; guard was intended to bound a misbehaving device but does
not cover the count == 0 case.&lt;/p&gt;
&lt;p&gt;Stop the loop on an empty payload so a malfunctioning or malicious
device cannot wedge the poison scan.&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;cxl/mbox: Break poison list loop on an empty payload&lt;/p&gt;
&lt;p&gt;A device that returns count == 0 with CXL_POISON_FLAG_MORE set on every
iteration never advances nr_records, so the max_errors guard never
trips and the do/while loops forever while holding poison.mutex. That
hangs the sysfs-triggered scan thread and blocks all subsequent poison
operations on the device. The existing &amp;#34;Protect against an uncleared
_FLAG_MORE&amp;#34; guard was intended to bound a misbehaving device but does
not cover the count == 0 case.&lt;/p&gt;
&lt;p&gt;Stop the loop on an empty payload so a malfunctioning or malicious
device cannot wedge the poison scan.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93097</guid>
    </item>
  </channel>
</rss>
