# CVE-2022-50672: mailbox: zynq-ipi: fix error handling while device_register() fails

> A null pointer dereference in the Zynq IPI mailbox driver can cause a kernel crash if device registration fails, leading to denial of service.

- **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:** 9 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50672, GHSA-fc53-63px-vp2j, UBUNTU-CVE-2022-50672

## What is CVE-2022-50672?

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.

### Official 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.

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


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

Apply the vendor's patch.

## Is CVE-2022-50672 being exploited?

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

## Fix prompt for AI coding agents

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

What 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.
Exploitation: There is no known exploitation of CVE-2022-50672 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-50672/ (Markdown: https://insights.sbomify.com/CVE-2022-50672/index.md)
```

## Sources

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

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