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

Published Dec 9, 2025
·
Updated

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

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

If deviceregister() fails, it has two issues: 1. The name allocated by devsetname() is leaked. 2. The parent of device is not NULL, deviceunregister() is called in zynqmpipifreemboxes(), it will lead a kernel crash because of removing not added device.

Call putdevice() to give up the reference, so the name is freed in kobjectcleanup(). Add device registered check in zynqmpipifreemboxes() to avoid null-ptr-deref.

Affected Software

151 affected componentsFixes available
linux/kernel
debian/linux<6.1.4-1
6.1.4-1
debian/linux<6.1.4-1
6.1.4-1
debian/linux<6.1.4-1
6.1.4-1
ubuntu/linux-hwe-edge*
ubuntu/linux-aws-5.4<5.4.0-1097.105~18.04.1
5.4.0-1097.105~18.04.1
ubuntu/linux-azure-5.4<5.4.0-1104.110~18.04.1
5.4.0-1104.110~18.04.1
ubuntu/linux-gcp-5.4<5.4.0-1101.110~18.04.1
5.4.0-1101.110~18.04.1
ubuntu/linux-hwe-5.4<5.4.0-144.161~18.04.1
5.4.0-144.161~18.04.1
ubuntu/linux-ibm-5.4<5.4.0-1045.50~18.04.1
5.4.0-1045.50~18.04.1
ubuntu/linux-oracle-5.4<5.4.0-1094.103~18.04.1
5.4.0-1094.103~18.04.1
ubuntu/linux-raspi-5.4<5.4.0-1081.92~18.04.1
5.4.0-1081.92~18.04.1
ubuntu/linux-aws-5.0*
ubuntu/linux-aws-5.3*
ubuntu/linux-azure*
ubuntu/linux-azure-5.3*
ubuntu/linux-azure-edge*
ubuntu/linux-gcp*
ubuntu/linux-gcp-5.3*
ubuntu/linux-gke-4.15*
ubuntu/linux-gke-5.4*
ubuntu/linux-gkeop-5.4*
ubuntu/linux-hwe*
ubuntu/linux-hwe-edge*
ubuntu/linux-oem*
ubuntu/linux-oracle-5.0*
ubuntu/linux-oracle-5.3*
ubuntu/linux<5.4.0-144.161
5.4.0-144.161
ubuntu/linux-aws<5.4.0-1097.105
5.4.0-1097.105
ubuntu/linux-aws-5.15<5.15.0-1033.37~20.04.1
5.15.0-1033.37~20.04.1
ubuntu/linux-azure<5.4.0-1104.110
5.4.0-1104.110
ubuntu/linux-azure-5.15<5.15.0-1035.42~20.04.1
5.15.0-1035.42~20.04.1
ubuntu/linux-bluefield<5.4.0-1059.65
5.4.0-1059.65
ubuntu/linux-gcp<5.4.0-1101.110
5.4.0-1101.110
ubuntu/linux-gcp-5.15<5.15.0-1031.38~20.04.1
5.15.0-1031.38~20.04.1
ubuntu/linux-hwe-5.15<5.15.0-69.76~20.04.1
5.15.0-69.76~20.04.1
ubuntu/linux-ibm<5.4.0-1045.50
5.4.0-1045.50
ubuntu/linux-intel-iotg-5.15<5.15.0-1027.32~20.04.1
5.15.0-1027.32~20.04.1
ubuntu/linux-iot<5.4.0-1013.15
5.4.0-1013.15
ubuntu/linux-kvm<5.4.0-1087.93
5.4.0-1087.93
ubuntu/linux-lowlatency-hwe-5.15<5.15.0-69.76~20.04.1
5.15.0-69.76~20.04.1
ubuntu/linux-nvidia-tegra-5.15<5.15.0-1014.14~20.04.1
5.15.0-1014.14~20.04.1
ubuntu/linux-oracle<5.4.0-1094.103
5.4.0-1094.103
ubuntu/linux-oracle-5.15<5.15.0-1032.38~20.04.1
5.15.0-1032.38~20.04.1
ubuntu/linux-raspi<5.4.0-1081.92
5.4.0-1081.92
ubuntu/linux-riscv-5.15<5.15.0-1030.34~20.04.1
5.15.0-1030.34~20.04.1
ubuntu/linux-xilinx-zynqmp<5.4.0-1022.26
5.4.0-1022.26
ubuntu/linux-aws-5.11*
ubuntu/linux-aws-5.13*
ubuntu/linux-aws-5.8*
ubuntu/linux-azure-5.11*
ubuntu/linux-azure-5.13*
ubuntu/linux-azure-5.8*
ubuntu/linux-azure-fde*
ubuntu/linux-gcp-5.11*
ubuntu/linux-gcp-5.13*
ubuntu/linux-gcp-5.8*
ubuntu/linux-gke*
ubuntu/linux-gke-5.15*
ubuntu/linux-gkeop*
ubuntu/linux-gkeop-5.15*
ubuntu/linux-hwe-5.11*
ubuntu/linux-hwe-5.13*
ubuntu/linux-hwe-5.8*
ubuntu/linux-intel-5.13*
ubuntu/linux-oem-5.10*
ubuntu/linux-oem-5.13*
ubuntu/linux-oem-5.6*
ubuntu/linux-oracle-5.11*
ubuntu/linux-oracle-5.13*
ubuntu/linux-oracle-5.8*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
ubuntu/linux-riscv-5.11*
ubuntu/linux-riscv-5.8*
ubuntu/linux-aws-fips<5.4.0-1099.107+fips1
5.4.0-1099.107+fips1
ubuntu/linux-azure-fips<5.4.0-1104.110+fips1
5.4.0-1104.110+fips1
ubuntu/linux-fips<5.4.0-1073.82
5.4.0-1073.82
ubuntu/linux-gcp-fips<5.4.0-1101.110+fips1
5.4.0-1101.110+fips1
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux<5.15.0-69.76
5.15.0-69.76
ubuntu/linux-allwinner-5.19*
ubuntu/linux-aws<5.15.0-1033.37
5.15.0-1033.37
ubuntu/linux-aws-5.19*
ubuntu/linux-aws-6.2*
ubuntu/linux-aws-6.5*
ubuntu/linux-azure<5.15.0-1035.42
5.15.0-1035.42
ubuntu/linux-azure-5.19*
ubuntu/linux-azure-6.2*
ubuntu/linux-azure-6.5*
ubuntu/linux-azure-fde<5.15.0-1035.42.1
5.15.0-1035.42.1
ubuntu/linux-azure-fde-5.19*
ubuntu/linux-azure-fde-6.2*
ubuntu/linux-gcp<5.15.0-1031.38
5.15.0-1031.38
ubuntu/linux-gcp-5.19*
ubuntu/linux-gcp-6.2*
ubuntu/linux-gcp-6.5*
ubuntu/linux-gke<5.15.0-1030.35
5.15.0-1030.35
ubuntu/linux-gkeop<5.15.0-1017.22
5.15.0-1017.22
ubuntu/linux-hwe-5.19*
ubuntu/linux-hwe-6.2*
ubuntu/linux-hwe-6.5*
ubuntu/linux-ibm<5.15.0-1027.30
5.15.0-1027.30
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-intel-iotg<5.15.0-1027.32
5.15.0-1027.32
ubuntu/linux-kvm<5.15.0-1030.35
5.15.0-1030.35
ubuntu/linux-lowlatency<5.15.0-69.76
5.15.0-69.76
ubuntu/linux-lowlatency-hwe-5.19*
ubuntu/linux-lowlatency-hwe-6.2*
ubuntu/linux-lowlatency-hwe-6.5*
ubuntu/linux-nvidia<5.15.0-1023.23
5.15.0-1023.23
ubuntu/linux-nvidia-6.2*
ubuntu/linux-nvidia-6.5*
ubuntu/linux-oem-5.17*
ubuntu/linux-oem-6.0*
ubuntu/linux-oem-6.1*
ubuntu/linux-oem-6.5*
ubuntu/linux-oracle<5.15.0-1032.38
5.15.0-1032.38
ubuntu/linux-oracle-6.5*
ubuntu/linux-raspi<5.15.0-1026.28
5.15.0-1026.28
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-riscv-5.19*
ubuntu/linux-riscv-6.5*
ubuntu/linux-starfive-5.19*
ubuntu/linux-starfive-6.2*
ubuntu/linux-starfive-6.5*
ubuntu/linux-bluefield<5.15.0-1015.17
5.15.0-1015.17
ubuntu/linux-intel-iot-realtime<5.15.0-1023.28
5.15.0-1023.28
ubuntu/linux-realtime<5.15.0-1034.37
5.15.0-1034.37
ubuntu/linux-azure-6.11*
ubuntu/linux-gcp-6.11*
ubuntu/linux-hwe-6.11*
ubuntu/linux-lowlatency-hwe-6.11*
ubuntu/linux-nvidia-6.11*
ubuntu/linux-oem-6.11*
ubuntu/linux-oem-6.8*
ubuntu/linux-raspi-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-riscv-6.14*
ubuntu/linux-vmware*
linux/kernel>=5.1.0<5.4.229
5.4.229
linux/kernel>=5.5.0<5.10.163
5.10.163
linux/kernel>=5.11.0<5.15.86
5.15.86
linux/kernel>=5.16.0<6.0.16
6.0.16
linux/kernel>=6.1.0<6.1.2
6.1.2
debian/linux
6.1.176-16.1.190-16.12.107-16.12.116-17.2.15-17.3.4-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.4-1
  2. Upgrade

    Upgrade ubuntu/linux-aws-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1097.105~18.04.1
  3. Upgrade

    Upgrade ubuntu/linux-azure-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1104.110~18.04.1
  4. Upgrade

    Upgrade ubuntu/linux-gcp-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1101.110~18.04.1
  5. Upgrade

    Upgrade ubuntu/linux-hwe-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-144.161~18.04.1
  6. Upgrade

    Upgrade ubuntu/linux-ibm-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1045.50~18.04.1
  7. Upgrade

    Upgrade ubuntu/linux-oracle-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1094.103~18.04.1
  8. Upgrade

    Upgrade ubuntu/linux-raspi-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1081.92~18.04.1
  9. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 5.4.0-144.161
  10. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 5.4.0-1097.105
  11. Upgrade

    Upgrade ubuntu/linux-aws-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1033.37~20.04.1
  12. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 5.4.0-1104.110
  13. Upgrade

    Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1035.42~20.04.1
  14. Upgrade

    Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.

    Fixed in 5.4.0-1059.65
  15. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 5.4.0-1101.110
  16. Upgrade

    Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1031.38~20.04.1
  17. Upgrade

    Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-69.76~20.04.1
  18. Upgrade

    Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.

    Fixed in 5.4.0-1045.50
  19. Upgrade

    Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1027.32~20.04.1
  20. Upgrade

    Upgrade ubuntu/linux-iot to a version that resolves this vulnerability.

    Fixed in 5.4.0-1013.15
  21. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 5.4.0-1087.93
  22. Upgrade

    Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-69.76~20.04.1
  23. Upgrade

    Upgrade ubuntu/linux-nvidia-tegra-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1014.14~20.04.1
  24. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 5.4.0-1094.103
  25. Upgrade

    Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1032.38~20.04.1
  26. Upgrade

    Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.

    Fixed in 5.4.0-1081.92
  27. Upgrade

    Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1030.34~20.04.1
  28. Upgrade

    Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.

    Fixed in 5.4.0-1022.26
  29. Upgrade

    Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.

    Fixed in 5.4.0-1099.107+fips1
  30. Upgrade

    Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.

    Fixed in 5.4.0-1104.110+fips1
  31. Upgrade

    Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.

    Fixed in 5.4.0-1073.82
  32. Upgrade

    Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.

    Fixed in 5.4.0-1101.110+fips1
  33. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 5.15.0-69.76
  34. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 5.15.0-1033.37
  35. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 5.15.0-1035.42
  36. Upgrade

    Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.

    Fixed in 5.15.0-1035.42.1
  37. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 5.15.0-1031.38
  38. Upgrade

    Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.

    Fixed in 5.15.0-1030.35
  39. Upgrade

    Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.

    Fixed in 5.15.0-1017.22
  40. Upgrade

    Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.

    Fixed in 5.15.0-1027.30
  41. Upgrade

    Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.

    Fixed in 5.15.0-1027.32
  42. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 5.15.0-1030.35
  43. Upgrade

    Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.15.0-69.76
  44. Upgrade

    Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.

    Fixed in 5.15.0-1023.23
  45. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 5.15.0-1032.38
  46. Upgrade

    Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.

    Fixed in 5.15.0-1026.28
  47. Upgrade

    Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.

    Fixed in 5.15.0-1015.17
  48. Upgrade

    Upgrade ubuntu/linux-intel-iot-realtime to a version that resolves this vulnerability.

    Fixed in 5.15.0-1023.28
  49. Upgrade

    Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.

    Fixed in 5.15.0-1034.37
  50. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.4.229
  51. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.10.163
  52. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.15.86
  53. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.0.16
  54. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.1.2
  55. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.116-1Fixed in 7.2.15-1Fixed in 7.3.4-1
  56. Compensating control

    In zynqmp_ipi_free_mboxes(), check whether the device is registered before calling device_unregister() to avoid a null-pointer dereference, and call put_device() after device_register() failure so the name is freed during kobject_cleanup().

Event History

Dec 9, 2025
CVE Published
via MITRE·01:29 AM
Data Sourced
via MITRE·01:29 AM
Description
Data Sourced
via OSV·01:29 AM
DescriptionAffected Software
Data Sourced
via NVD·04:17 PM
Description
Nov 11, 2026
Data Sourced
via OSV·09:37 AM
Severity

Frequently Asked Questions

1

What is the severity of CVE-2022-50672?

CVE-2022-50672 has a low severity rating due to issues in error handling during device registration in the Linux kernel.

2

How do I fix CVE-2022-50672?

To fix CVE-2022-50672, update your Linux kernel to a version that includes the patch addressing the error handling issues.

3

What software is affected by CVE-2022-50672?

CVE-2022-50672 affects versions of the Linux kernel that utilize the mailbox subsystem with device registration.

4

What are the implications of CVE-2022-50672?

The implications of CVE-2022-50672 include potential resource leaks and improper handling of device parent relationships in the Linux kernel.

5

Is CVE-2022-50672 exploitable?

CVE-2022-50672 is not considered directly exploitable but could lead to unintended behavior due to improper error handling.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203