<?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>Thu, 08 Oct 2026 04:41:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-53192 — clk: clk-loongson2: Fix potential buffer overflow in flexible-array member access</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-53192</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;clk: clk-loongson2: Fix potential buffer overflow in flexible-array member access&lt;/p&gt;
&lt;p&gt;Flexible-array member `hws` in `struct clk_hw_onecell_data` is annotated
with the `counted_by()` attribute. This means that when memory is
allocated for this array, the _counter_, which in this case is member
`num` in the flexible structure, should be set to the maximum number of
elements the flexible array can contain, or fewer.&lt;/p&gt;
&lt;p&gt;In this case, the total number of elements for the flexible array is
determined by variable `clks_num` when allocating heap space via
`devm_kzalloc()`, as shown below:&lt;/p&gt;
&lt;p&gt;289         struct loongson2_clk_provider *clp;
	...
296         for (p = data; p-&amp;gt;name; p++)
297                 clks_num++;
298
299         clp = devm_kzalloc(dev, struct_size(clp, clk_data.hws, clks_num),
300                            GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;So, `clp-&amp;gt;clk_data.num` should be set to `clks_num` or less, and not
exceed `clks_num`, as is currently the case. Otherwise, if data is
written into `clp-&amp;gt;clk_data.hws[clks_num]`, the instrumentation
provided by the compiler won&amp;#39;t detect the overflow, leading to a
memory corruption bug at runtime.&lt;/p&gt;
&lt;p&gt;Fix this issue by setting `clp-&amp;gt;clk_data.num` to `clks_num`.&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;clk: clk-loongson2: Fix potential buffer overflow in flexible-array member access&lt;/p&gt;
&lt;p&gt;Flexible-array member `hws` in `struct clk_hw_onecell_data` is annotated
with the `counted_by()` attribute. This means that when memory is
allocated for this array, the _counter_, which in this case is member
`num` in the flexible structure, should be set to the maximum number of
elements the flexible array can contain, or fewer.&lt;/p&gt;
&lt;p&gt;In this case, the total number of elements for the flexible array is
determined by variable `clks_num` when allocating heap space via
`devm_kzalloc()`, as shown below:&lt;/p&gt;
&lt;p&gt;289         struct loongson2_clk_provider *clp;
	...
296         for (p = data; p-&amp;gt;name; p++)
297                 clks_num++;
298
299         clp = devm_kzalloc(dev, struct_size(clp, clk_data.hws, clks_num),
300                            GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;So, `clp-&amp;gt;clk_data.num` should be set to `clks_num` or less, and not
exceed `clks_num`, as is currently the case. Otherwise, if data is
written into `clp-&amp;gt;clk_data.hws[clks_num]`, the instrumentation
provided by the compiler won&amp;#39;t detect the overflow, leading to a
memory corruption bug at runtime.&lt;/p&gt;
&lt;p&gt;Fix this issue by setting `clp-&amp;gt;clk_data.num` to `clks_num`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-53192</guid>
    </item>
  </channel>
</rss>
