<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T05:35:33.380764+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98362</id>
    <title>fkie_cve-2026-98362</title>
    <updated>2026-10-07T05:35:33.384987+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate</p>
<p>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-&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.</p>
<p>Treat indexes &gt;= opp count as invalid and return 0, same as idx &lt; 0.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-98362"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-q57h-9f6r-c5h9</id>
    <title>GHSA-q57h-9f6r-c5h9</title>
    <updated>2026-10-07T05:35:33.385113+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate</p>
<p>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-&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.</p>
<p>Treat indexes &gt;= opp count as invalid and return 0, same as idx &lt; 0.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-q57h-9f6r-c5h9"/>
  </entry>
</feed>
