<?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, 07 Oct 2026 05:35:34 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98362</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98362</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate&lt;/p&gt;
&lt;p&gt;dvfs_get_idx() may return an out-of-range index if the SCP firmware is
buggy or returns a stale value. Only negative indexes were rejected, so a
large index walked past info-&amp;gt;opps and could treat garbage as a clock rate
(KASAN OOB / wrong frequency to consumers). The missing upper bound dates
back to the original SCPI clock driver.&lt;/p&gt;
&lt;p&gt;Treat indexes &amp;gt;= opp count as invalid and return 0, same as idx &amp;lt; 0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate&lt;/p&gt;
&lt;p&gt;dvfs_get_idx() may return an out-of-range index if the SCP firmware is
buggy or returns a stale value. Only negative indexes were rejected, so a
large index walked past info-&amp;gt;opps and could treat garbage as a clock rate
(KASAN OOB / wrong frequency to consumers). The missing upper bound dates
back to the original SCPI clock driver.&lt;/p&gt;
&lt;p&gt;Treat indexes &amp;gt;= opp count as invalid and return 0, same as idx &amp;lt; 0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98362</guid>
    </item>
    <item>
      <title>GHSA-q57h-9f6r-c5h9</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-q57h-9f6r-c5h9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate&lt;/p&gt;
&lt;p&gt;dvfs_get_idx() may return an out-of-range index if the SCP firmware is
buggy or returns a stale value. Only negative indexes were rejected, so a
large index walked past info-&amp;gt;opps and could treat garbage as a clock rate
(KASAN OOB / wrong frequency to consumers). The missing upper bound dates
back to the original SCPI clock driver.&lt;/p&gt;
&lt;p&gt;Treat indexes &amp;gt;= opp count as invalid and return 0, same as idx &amp;lt; 0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate&lt;/p&gt;
&lt;p&gt;dvfs_get_idx() may return an out-of-range index if the SCP firmware is
buggy or returns a stale value. Only negative indexes were rejected, so a
large index walked past info-&amp;gt;opps and could treat garbage as a clock rate
(KASAN OOB / wrong frequency to consumers). The missing upper bound dates
back to the original SCPI clock driver.&lt;/p&gt;
&lt;p&gt;Treat indexes &amp;gt;= opp count as invalid and return 0, same as idx &amp;lt; 0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-q57h-9f6r-c5h9</guid>
    </item>
  </channel>
</rss>
