<?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 19:25:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-38592 — drm/mediatek: Init `ddp_comp` with devm_kcalloc()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-38592</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;drm/mediatek: Init `ddp_comp` with devm_kcalloc()&lt;/p&gt;
&lt;p&gt;In the case where `conn_routes` is true we allocate an extra slot in
the `ddp_comp` array but mtk_drm_crtc_create() never seemed to
initialize it in the test case I ran. For me, this caused a later
crash when we looped through the array in mtk_drm_crtc_mode_valid().
This showed up for me when I booted with `slub_debug=FZPUA` which
poisons the memory initially. Without `slub_debug` I couldn&amp;#39;t
reproduce, presumably because the later code handles the value being
NULL and in most cases (not guaranteed in all cases) the memory the
allocator returned started out as 0.&lt;/p&gt;
&lt;p&gt;It really doesn&amp;#39;t hurt to initialize the array with devm_kcalloc()
since the array is small and the overhead of initting a handful of
elements to 0 is small. In general initting memory to zero is a safer
practice and usually it&amp;#39;s suggested to only use the non-initting alloc
functions if you really need to.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s switch the function to use an allocation function that zeros the
memory. For me, this avoids the crash.&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;drm/mediatek: Init `ddp_comp` with devm_kcalloc()&lt;/p&gt;
&lt;p&gt;In the case where `conn_routes` is true we allocate an extra slot in
the `ddp_comp` array but mtk_drm_crtc_create() never seemed to
initialize it in the test case I ran. For me, this caused a later
crash when we looped through the array in mtk_drm_crtc_mode_valid().
This showed up for me when I booted with `slub_debug=FZPUA` which
poisons the memory initially. Without `slub_debug` I couldn&amp;#39;t
reproduce, presumably because the later code handles the value being
NULL and in most cases (not guaranteed in all cases) the memory the
allocator returned started out as 0.&lt;/p&gt;
&lt;p&gt;It really doesn&amp;#39;t hurt to initialize the array with devm_kcalloc()
since the array is small and the overhead of initting a handful of
elements to 0 is small. In general initting memory to zero is a safer
practice and usually it&amp;#39;s suggested to only use the non-initting alloc
functions if you really need to.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s switch the function to use an allocation function that zeros the
memory. For me, this avoids the crash.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-38592</guid>
    </item>
  </channel>
</rss>
