<?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 03:31:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37887 — pds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-37887</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;pds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result&lt;/p&gt;
&lt;p&gt;If the FW doesn&amp;#39;t support the PDS_CORE_CMD_FW_CONTROL command
the driver might at the least print garbage and at the worst
crash when the user runs the &amp;#34;devlink dev info&amp;#34; devlink command.&lt;/p&gt;
&lt;p&gt;This happens because the stack variable fw_list is not 0
initialized which results in fw_list.num_fw_slots being a
garbage value from the stack.  Then the driver tries to access
fw_list.fw_names[i] with i &amp;gt;= ARRAY_SIZE and runs off the end
of the array.&lt;/p&gt;
&lt;p&gt;Fix this by initializing the fw_list and by not failing
completely if the devcmd fails because other useful information
is printed via devlink dev info even if the devcmd fails.&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;pds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result&lt;/p&gt;
&lt;p&gt;If the FW doesn&amp;#39;t support the PDS_CORE_CMD_FW_CONTROL command
the driver might at the least print garbage and at the worst
crash when the user runs the &amp;#34;devlink dev info&amp;#34; devlink command.&lt;/p&gt;
&lt;p&gt;This happens because the stack variable fw_list is not 0
initialized which results in fw_list.num_fw_slots being a
garbage value from the stack.  Then the driver tries to access
fw_list.fw_names[i] with i &amp;gt;= ARRAY_SIZE and runs off the end
of the array.&lt;/p&gt;
&lt;p&gt;Fix this by initializing the fw_list and by not failing
completely if the devcmd fails because other useful information
is printed via devlink dev info even if the devcmd fails.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-37887</guid>
    </item>
  </channel>
</rss>
