CVE-2022-50558
BaseFortify
Publication date: 2025-10-22
Last updated on: 2025-10-22
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the regmap-irq subsystem where a recent code change introduced a new property called num_config_regs to replace an older property num_type_reg. However, the function regmap_add_irq_chip_fwnode was not updated to use the new property. Later, when the old property was removed from a driver, this caused a null pointer dereference because the related buffer was never allocated. This leads to a kernel crash when the system tries to access this null pointer.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a null pointer dereference, leading to a denial of service. Systems using the affected regmap-irq code and drivers may become unstable or unresponsive when the issue is triggered.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for null pointer dereference errors related to regmap_irq_set_type. You can check the kernel log messages using commands like 'dmesg | grep regmap_irq_set_type' or 'journalctl -k | grep regmap_irq_set_type' to identify the specific error messages indicating the issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the regmap_add_irq_chip_fwnode function uses the num_config_regs property correctly instead of the deprecated num_type_reg. This update prevents the null pointer dereference. If updating is not immediately possible, monitoring for the error and avoiding use of affected drivers like WCD9335 may reduce risk.