LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50197: cpufreq: zynq: Fix refcount leak in zynq_get_revision

In the Linux kernel, the following vulnerability has been resolved: cpufreq: zynq: Fix refcount leak in zynq_get_revision of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel resource leak in the Zynq CPU frequency driver. The code takes a reference to a device-tree node and fails to release it. The public record does not provide CVSS, demonstrated impact, or active exploitation evidence.

Executive priority

Handle through normal kernel patch management unless Zynq-based systems are business-critical or difficult to reboot. There is no cited evidence of exploitation, but kernel resource leaks can affect reliability over time.

Technical view

The issue is in zynq_get_revision within the Linux cpufreq zynq code. of_find_compatible_node() increments a node reference count, but the affected code path missed of_node_put(), causing a reference-count leak. Kernel stable commits add the missing release.

Likely exposure

Most relevant exposure is Linux systems using the Zynq cpufreq driver, especially embedded or Xilinx Zynq-based deployments. The bundle lists Linux kernel versions and stable commit references but provides no CPEs, distro advisories, or product-specific deployment evidence.

Exploitation context

The provided sources do not show active exploitation, public exploit availability, or KEV listing. Treat this as a kernel maintenance and availability-risk item until vendor advisories or severity scoring clarify practical impact.

Researcher notes

Evidence is limited to the CVE record and kernel stable fixes. No CVSS, CWE, CPE, exploit detail, or distribution-specific advisory is included. Validation should focus on driver presence, Zynq hardware use, and whether the stable fix is present.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • For custom kernels, confirm the missing of_node_put() fix is backported.
  • Ask embedded Linux vendors for updated Zynq kernel builds.
  • Track distro or vendor advisories for severity and supported package versions.

Validation and detection

  • Inventory systems running Linux on Zynq-based hardware.
  • Confirm whether the zynq cpufreq driver is built or loaded.
  • Compare kernel source or package changelogs against the referenced stable commits.
  • Check vendor advisories for your exact kernel branch and support status.
Prepared
Confidence
medium
Sources
6

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-50197 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
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux00f7dc636366f72474b1896f4990b3c086cd2c6d, 00f7dc636366f72474b1896f4990b3c086cd2c6d, 00f7dc636366f72474b1896f4990b3c086cd2c6d, 00f7dc636366f72474b1896f4990b3c086cd2c6d, 00f7dc636366f72474b1896f4990b3c086cd2c6d, 00f7dc636366f72474b1896f4990b3c086cd2c6d, 00f7dc636366f72474b1896f4990b3c086cd2c6d, 00f7dc636366f72474b1896f4990b3c086cd2c6dunaffected
LinuxLinux3.16, 0, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

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