CVE-2022-50672
Published Dec 9, 2025
Modified Apr 15, 2026
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.
Is your site exposed to CVE-2022-50672?
Run a free security scan — no signup, results in seconds.
References
Other References
https://git.kernel.org/stable/c/3fcf079958c00d83c51e4f250abf2c77fe9cc1b9
https://git.kernel.org/stable/c/4f05d8e2fb3ab702c2633a74571e1b31cb579985
https://git.kernel.org/stable/c/a39b4de0804f9fe0ae911b359ffd4afe7d9d933b
https://git.kernel.org/stable/c/a6792a0cdef0b1c2d77920246283a72537e60e94
https://git.kernel.org/stable/c/b3a5c76f61e2b380e29dfc6705854ca1ee85501d
https://git.kernel.org/stable/c/f2d63cefc012cafe1b7651bbf3302f8bcd8bea4a
Frequently Asked Questions
What is 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. 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.
How do I check if I'm vulnerable to CVE-2022-50672? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.