Menu

Star on GitHub · 3.2k

CVE-2022-50672

In the Linux kernel, the following vulnerability has been resolved: mailbox: zynq-ipi: fix error handling while device_register() fails If device_register() fails, it has two issues: 1.

Published Dec 9, 2025EPSS 0.24%

Overview

CVE-2022-50672 is a known-severity vulnerability. It was published on December 9, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

mailbox: zynq-ipi: fix error handling while device_register() fails

If device_register() fails, it has two issues:

1. The name allocated by dev_set_name() is leaked.

2. The parent of device is not NULL, device_unregister() is called

in zynqmp_ipi_free_mboxes(), it will lead a kernel crash because

of removing not added device.

Call put_device() to give up the reference, so the name is freed in

kobject_cleanup(). Add device registered check in zynqmp_ipi_free_mboxes()

to avoid null-ptr-deref.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50672?

CVE-2022-50672 is a known-severity vulnerability. It was published on December 9, 2025.

How severe is CVE-2022-50672?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2022-50672?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50672?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50672 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.