<?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 16:40:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53768 — regmap-irq: Fix out-of-bounds access when allocating config buffers</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53768</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;regmap-irq: Fix out-of-bounds access when allocating config buffers&lt;/p&gt;
&lt;p&gt;When allocating the 2D array for handling IRQ type registers in
regmap_add_irq_chip_fwnode(), the intent is to allocate a matrix
with num_config_bases rows and num_config_regs columns.&lt;/p&gt;
&lt;p&gt;This is currently handled by allocating a buffer to hold a pointer for
each row (i.e. num_config_bases). After that, the logic attempts to
allocate the memory required to hold the register configuration for
each row. However, instead of doing this allocation for each row
(i.e. num_config_bases allocations), the logic erroneously does this
allocation num_config_regs number of times.&lt;/p&gt;
&lt;p&gt;This scenario can lead to out-of-bounds accesses when num_config_regs
is greater than num_config_bases. Fix this by updating the terminating
condition of the loop that allocates the memory for holding the register
configuration to allocate memory only for each row in the matrix.&lt;/p&gt;
&lt;p&gt;Amit Pundir reported a crash that was occurring on his db845c device
due to memory corruption (see &amp;#34;Closes&amp;#34; tag for Amit&amp;#39;s report). The KASAN
report below helped narrow it down to this issue:&lt;/p&gt;
&lt;p&gt;[   14.033877][    T1] ==================================================================
[   14.042507][    T1] BUG: KASAN: invalid-access in regmap_add_irq_chip_fwnode+0x594/0x1364
[   14.050796][    T1] Write of size 8 at addr 06ffff8081021850 by task init/1&lt;/p&gt;
&lt;p&gt;[   14.242004][    T1] The buggy address belongs to…&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;regmap-irq: Fix out-of-bounds access when allocating config buffers&lt;/p&gt;
&lt;p&gt;When allocating the 2D array for handling IRQ type registers in
regmap_add_irq_chip_fwnode(), the intent is to allocate a matrix
with num_config_bases rows and num_config_regs columns.&lt;/p&gt;
&lt;p&gt;This is currently handled by allocating a buffer to hold a pointer for
each row (i.e. num_config_bases). After that, the logic attempts to
allocate the memory required to hold the register configuration for
each row. However, instead of doing this allocation for each row
(i.e. num_config_bases allocations), the logic erroneously does this
allocation num_config_regs number of times.&lt;/p&gt;
&lt;p&gt;This scenario can lead to out-of-bounds accesses when num_config_regs
is greater than num_config_bases. Fix this by updating the terminating
condition of the loop that allocates the memory for holding the register
configuration to allocate memory only for each row in the matrix.&lt;/p&gt;
&lt;p&gt;Amit Pundir reported a crash that was occurring on his db845c device
due to memory corruption (see &amp;#34;Closes&amp;#34; tag for Amit&amp;#39;s report). The KASAN
report below helped narrow it down to this issue:&lt;/p&gt;
&lt;p&gt;[   14.033877][    T1] ==================================================================
[   14.042507][    T1] BUG: KASAN: invalid-access in regmap_add_irq_chip_fwnode+0x594/0x1364
[   14.050796][    T1] Write of size 8 at addr 06ffff8081021850 by task init/1&lt;/p&gt;
&lt;p&gt;[   14.242004][    T1] The buggy address belongs to…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53768</guid>
    </item>
  </channel>
</rss>
