<?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>Sun, 04 Oct 2026 13:13:55 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03905</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-03905</link>
      <description>bdu:2026-03905</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-03905</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50558</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2022-50558</link>
      <description>&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;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/fkie_cve-2022-50558</guid>
    </item>
    <item>
      <title>GHSA-w4hx-49mv-6qvv</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-w4hx-49mv-6qvv</link>
      <description>&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;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/ghsa-w4hx-49mv-6qvv</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — security update for kernel</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;security update for kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;security update for kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50558</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50558</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode 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: [   39.199374] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [   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 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode 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: [   39.199374] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [   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 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/ubuntu-cve-2022-50558</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2394 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2394</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2394</guid>
    </item>
  </channel>
</rss>
