{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50672 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50672 is a vulnerability in Linux, published on 9 Dec 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-50672 and fix it if it is affected.\n\nWhat it is: CVE-2022-50672 is a vulnerability in Linux, published on 9 Dec 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-50672 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-50672/ (Markdown: https://insights.sbomify.com/CVE-2022-50672/index.md)","id":"CVE-2022-50672","markdown":"https://insights.sbomify.com/CVE-2022-50672/index.md","name":"CVE-2022-50672","record":{"aliases":["DEBIAN-CVE-2022-50672","GHSA-fc53-63px-vp2j","UBUNTU-CVE-2022-50672"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A null pointer dereference in the Zynq IPI mailbox driver can cause a kernel crash if device registration fails, leading to denial of service.","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\nmailbox: zynq-ipi: fix error handling while device_register() fails\n\nIf device_register() fails, it has two issues:\n1. The name allocated by dev_set_name() is leaked.\n2. The parent of device is not NULL, device_unregister() is called\n   in zynqmp_ipi_free_mboxes(), it will lead a kernel crash because\n   of removing not added device.\n\nCall put_device() to give up the reference, so the name is freed in\nkobject_cleanup(). Add device registered check in zynqmp_ipi_free_mboxes()\nto avoid null-ptr-deref.","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":"mailbox: zynq-ipi: fix error handling while device_register() fails","id":"CVE-2022-50672","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":6,"next":{"headline":"ext4: fix use-after-free in ext4_orphan_cleanup","id":"CVE-2022-50673"},"packages":[],"prev":{"headline":"RDMA/rxe: Fix \"kernel NULL pointer dereference\" error","id":"CVE-2022-50671"},"products":["Linux"],"published":"2025-12-09","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 Zynq IPI mailbox driver can cause a kernel crash if device registration fails, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2022-50672/"}