<?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, 06 Oct 2026 05:06:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50558 — regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50558</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: Use the new num_config_regs property in regmap_add_irq_chip_fwnode&lt;/p&gt;
&lt;p&gt;Commit faa87ce9196d (&amp;#34;regmap-irq: Introduce config registers for irq
types&amp;#34;) added the num_config_regs, then commit 9edd4f5aee84 (&amp;#34;regmap-irq:
Deprecate type registers and virtual registers&amp;#34;) suggested to replace
num_type_reg with it. However, regmap_add_irq_chip_fwnode wasn&amp;#39;t modified
to use the new property. Later on, commit 255a03bb1bb3 (&amp;#34;ASoC: wcd9335:
Convert irq chip to config regs&amp;#34;) removed the old num_type_reg property
from the WCD9335 driver&amp;#39;s struct regmap_irq_chip, causing a null pointer
dereference in regmap_irq_set_type when it tried to index d-&amp;gt;type_buf as
it was never allocated in regmap_add_irq_chip_fwnode:&lt;/p&gt;
&lt;p&gt;[   39.199374] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000&lt;/p&gt;
&lt;p&gt;[   39.200006] Call trace:
[   39.200014]  regmap_irq_set_type+0x84/0x1c0
[   39.200026]  __irq_set_trigger+0x60/0x1c0
[   39.200040]  __setup_irq+0x2f4/0x78c
[   39.200051]  request_threaded_irq+0xe8/0x1a0&lt;/p&gt;
&lt;p&gt;Use num_config_regs in regmap_add_irq_chip_fwnode instead of num_type_reg,
and fall back to it if num_config_regs isn&amp;#39;t defined to maintain backward
compatibility.&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: Use the new num_config_regs property in regmap_add_irq_chip_fwnode&lt;/p&gt;
&lt;p&gt;Commit faa87ce9196d (&amp;#34;regmap-irq: Introduce config registers for irq
types&amp;#34;) added the num_config_regs, then commit 9edd4f5aee84 (&amp;#34;regmap-irq:
Deprecate type registers and virtual registers&amp;#34;) suggested to replace
num_type_reg with it. However, regmap_add_irq_chip_fwnode wasn&amp;#39;t modified
to use the new property. Later on, commit 255a03bb1bb3 (&amp;#34;ASoC: wcd9335:
Convert irq chip to config regs&amp;#34;) removed the old num_type_reg property
from the WCD9335 driver&amp;#39;s struct regmap_irq_chip, causing a null pointer
dereference in regmap_irq_set_type when it tried to index d-&amp;gt;type_buf as
it was never allocated in regmap_add_irq_chip_fwnode:&lt;/p&gt;
&lt;p&gt;[   39.199374] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000&lt;/p&gt;
&lt;p&gt;[   39.200006] Call trace:
[   39.200014]  regmap_irq_set_type+0x84/0x1c0
[   39.200026]  __irq_set_trigger+0x60/0x1c0
[   39.200040]  __setup_irq+0x2f4/0x78c
[   39.200051]  request_threaded_irq+0xe8/0x1a0&lt;/p&gt;
&lt;p&gt;Use num_config_regs in regmap_add_irq_chip_fwnode instead of num_type_reg,
and fall back to it if num_config_regs isn&amp;#39;t defined to maintain backward
compatibility.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50558</guid>
    </item>
  </channel>
</rss>
