<?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 15:46:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38297 — PM: EM: Fix potential division-by-zero error in em_compute_costs()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38297</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;PM: EM: Fix potential division-by-zero error in em_compute_costs()&lt;/p&gt;
&lt;p&gt;When the device is of a non-CPU type, table[i].performance won&amp;#39;t be
initialized in the previous em_init_performance(), resulting in division
by zero when calculating costs in em_compute_costs().&lt;/p&gt;
&lt;p&gt;Since the &amp;#39;cost&amp;#39; algorithm is only used for EAS energy efficiency
calculations and is currently not utilized by other device drivers, we
should add the _is_cpu_device(dev) check to prevent this division-by-zero
issue.&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;PM: EM: Fix potential division-by-zero error in em_compute_costs()&lt;/p&gt;
&lt;p&gt;When the device is of a non-CPU type, table[i].performance won&amp;#39;t be
initialized in the previous em_init_performance(), resulting in division
by zero when calculating costs in em_compute_costs().&lt;/p&gt;
&lt;p&gt;Since the &amp;#39;cost&amp;#39; algorithm is only used for EAS energy efficiency
calculations and is currently not utilized by other device drivers, we
should add the _is_cpu_device(dev) check to prevent this division-by-zero
issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38297</guid>
    </item>
  </channel>
</rss>
