{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50558 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-50558 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2022-50558 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50558/ (Markdown: https://insights.sbomify.com/CVE-2022-50558/index.md)","id":"CVE-2022-50558","markdown":"https://insights.sbomify.com/CVE-2022-50558/index.md","name":"CVE-2022-50558","record":{"aliases":["DEBIAN-CVE-2022-50558","GHSA-w4hx-49mv-6qvv","UBUNTU-CVE-2022-50558"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A null pointer dereference in the Linux kernel regmap-irq subsystem can cause a system crash when configuring IRQ types on specific hardware.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nregmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode\n\nCommit faa87ce9196d (\"regmap-irq: Introduce config registers for irq\ntypes\") added the num_config_regs, then commit 9edd4f5aee84 (\"regmap-irq:\nDeprecate type registers and virtual registers\") suggested to replace\nnum_type_reg with it. However, regmap_add_irq_chip_fwnode wasn't modified\nto use the new property. Later on, commit 255a03bb1bb3 (\"ASoC: wcd9335:\nConvert irq chip to config regs\") removed the old num_type_reg property\nfrom the WCD9335 driver's struct regmap_irq_chip, causing a null pointer\ndereference in regmap_irq_set_type when it tried to index d-\u003etype_buf as\nit was never allocated in regmap_add_irq_chip_fwnode:\n\n[   39.199374] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n\n[   39.200006] Call trace:\n[   39.200014]  regmap_irq_set_type+0x84/0x1c0\n[   39.200026]  __irq_set_trigger+0x60/0x1c0\n[   39.200040]  __setup_irq+0x2f4/0x78c\n[   39.200051]  request_threaded_irq+0xe8/0x1a0\n\nUse num_config_regs in regmap_add_irq_chip_fwnode instead of num_type_reg,\nand fall back to it if num_config_regs isn't defined to maintain backward\ncompatibility.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode","id":"CVE-2022-50558","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"clk: imx: scu: fix memleak on platform_device_add() fails","id":"CVE-2022-50559"},"packages":[],"prev":{"headline":"pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()","id":"CVE-2022-50557"},"products":["Linux"],"published":"2025-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel regmap-irq subsystem can cause a system crash when configuring IRQ types on specific hardware.","url":"https://insights.sbomify.com/CVE-2022-50558/"}