LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50672 is a Linux kernel bug in the zynq-ipi mailbox driver. If device registration fails, cleanup can leak memory and may crash the kernel through a null-pointer dereference. Business impact is likely availability-related on systems using this driver, but public severity and exploit evidence are not provided.

Executive priority

Treat as a targeted kernel availability issue, not an internet-wide emergency. Patch during normal kernel maintenance, with higher priority for embedded Linux systems using the zynq-ipi mailbox driver or environments where unexpected kernel crashes create operational risk.

Technical view

The flaw is in Linux kernel mailbox zynq-ipi error handling after device_register() failure. The fix calls put_device() so dev_set_name() allocations are released, and adds a registration check in zynqmp_ipi_free_mboxes() to avoid unregistering a device that was not added, preventing a crash path.

Likely exposure

Exposure appears limited to Linux systems running affected kernel code with the zynq-ipi mailbox driver relevant. The source lists Linux as affected, but provides no CVSS, CPEs, or distribution-specific package mapping. Prioritize embedded or hardware-specific Linux environments where this driver is enabled.

Exploitation context

No cited source states active exploitation, and the CVE is not marked KEV. The described trigger is an internal device registration failure path, suggesting denial-of-service risk rather than direct remote compromise based on available evidence. Exploitability conditions are not fully documented in the provided sources.

Researcher notes

The public record lacks CVSS, CWE, CPEs, and detailed exploit prerequisites. The vulnerability description is precise about the faulty cleanup path and linked stable commits, but affected version semantics in the supplied data are incomplete. Avoid assuming broad exposure without confirming driver presence and patch status.

Mitigation direction

  • Check vendor or Linux distribution advisories for kernels containing the referenced stable fixes.
  • Update affected Linux kernels to a version that includes the zynq-ipi error-handling fix.
  • Prioritize systems where the zynq-ipi mailbox driver is enabled or required.
  • If updates are delayed, monitor for kernel crashes around zynqmp_ipi mailbox initialization.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Determine whether the zynq-ipi mailbox driver is built, loaded, or used.
  • Verify the kernel includes one of the referenced upstream stable commits.
  • Review distribution changelogs for CVE-2022-50672 or the zynq-ipi fix.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50672 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4981b82ba2ff87df6a711fcd7a233c615df5fc79, 4981b82ba2ff87df6a711fcd7a233c615df5fc79, 4981b82ba2ff87df6a711fcd7a233c615df5fc79, 4981b82ba2ff87df6a711fcd7a233c615df5fc79, 4981b82ba2ff87df6a711fcd7a233c615df5fc79, 4981b82ba2ff87df6a711fcd7a233c615df5fc79unaffected
LinuxLinux5.1, 0, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.