# CVE-2022-50558: regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode

> A null pointer dereference in the Linux kernel regmap-irq subsystem can cause a system crash when configuring IRQ types on specific hardware.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Oct 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50558, GHSA-w4hx-49mv-6qvv, UBUNTU-CVE-2022-50558

## What is CVE-2022-50558?

CVE-2022-50558 is a vulnerability in Linux, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 ("regmap-irq: Introduce config registers for irq
types") added the num_config_regs, then commit 9edd4f5aee84 ("regmap-irq:
Deprecate type registers and virtual registers") suggested to replace
num_type_reg with it. However, regmap_add_irq_chip_fwnode wasn't modified
to use the new property. Later on, commit 255a03bb1bb3 ("ASoC: wcd9335:
Convert irq chip to config regs") removed the old num_type_reg property
from the WCD9335 driver's struct regmap_irq_chip, causing a null pointer
dereference in regmap_irq_set_type when it tried to index d->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't defined to maintain backward
compatibility.

## Which versions are affected by CVE-2022-50558?


## How do I fix CVE-2022-50558?

Apply the vendor's patch.

## Is CVE-2022-50558 being exploited?

There is no known exploitation of CVE-2022-50558 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50558 and fix it if it is affected.

What it is: CVE-2022-50558 is a vulnerability in Linux, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50558 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50558/ (Markdown: https://insights.sbomify.com/CVE-2022-50558/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50558
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50558
- OSV: https://osv.dev/vulnerability/CVE-2022-50558

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50558/
Summaries are generated and may contain mistakes; the official description above is the record.