LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50823: clk: tegra: Fix refcount leak in tegra114_clock_init

In the Linux kernel, the following vulnerability has been resolved: clk: tegra: Fix refcount leak in tegra114_clock_init of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50823 is a Linux kernel defect in NVIDIA Tegra114 clock initialization. The code failed to release a device-tree node reference, causing a reference-count leak. The public record does not show active exploitation, CVSS scoring, or broad business impact evidence.

Executive priority

Treat as routine kernel maintenance unless Tegra114-based products are business-critical. No source indicates active exploitation, but embedded systems often lag on kernel fixes and should be inventoried.

Technical view

The issue is in tegra114_clock_init: of_find_matching_node() returns a node with an incremented reference count, but the affected code did not call of_node_put() after use. Stable kernel commits add the missing release to prevent the leak.

Likely exposure

Likely limited to Linux systems using the Tegra114 clock driver on affected kernel versions or downstream kernels carrying the vulnerable code. General Linux servers without this Tegra platform path are unlikely to be exposed based on the provided evidence.

Exploitation context

The source bundle marks KEV as false and provides no public evidence of exploitation. The described flaw is a kernel reference-count leak, not a documented remote code execution or privilege escalation path.

Researcher notes

Evidence is limited to the CVE record and Linux stable commits. No CVSS, CWE, exploit report, or operational trigger conditions are provided. Avoid assuming impact beyond the documented reference-count leak.

Mitigation direction

  • Update to a kernel or vendor build containing the referenced stable fixes.
  • Check distribution or device-vendor advisories for the relevant backport.
  • Prioritize embedded and appliance fleets using NVIDIA Tegra114-based kernels.
  • Track downstream kernel forks that may carry the vulnerable driver code.

Validation and detection

  • Inventory Linux kernel versions across Tegra-based devices.
  • Confirm whether the tegra114 clock driver code is present in deployed kernels.
  • Review kernel changelogs for the referenced stable commit backports.
  • Validate vendor firmware or OS images include the missing of_node_put() fix.
Prepared
Confidence
medium
Sources
11

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-50823 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
10Source 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
LinuxLinux2cb5efefd6f7d3e7df9a7430b910a80515821256, 2cb5efefd6f7d3e7df9a7430b910a80515821256, 2cb5efefd6f7d3e7df9a7430b910a80515821256, 2cb5efefd6f7d3e7df9a7430b910a80515821256, 2cb5efefd6f7d3e7df9a7430b910a80515821256, 2cb5efefd6f7d3e7df9a7430b910a80515821256, 2cb5efefd6f7d3e7df9a7430b910a80515821256, 2cb5efefd6f7d3e7df9a7430b910a80515821256, 2cb5efefd6f7d3e7df9a7430b910a80515821256unaffected
LinuxLinux3.10, 0, 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

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