LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50776: clk: st: Fix memory leak in st_of_quadfs_setup()

In the Linux kernel, the following vulnerability has been resolved: clk: st: Fix memory leak in st_of_quadfs_setup() If st_clk_register_quadfs_pll() fails, @lock should be freed before goto @err_exit, otherwise will cause meory leak issue, fix it.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50776 is a Linux kernel memory leak fix in the ST clock driver path. If a specific PLL registration fails, allocated memory is not freed. Public sources do not provide CVSS, CWE, exploitation evidence, or business-impact detail, so urgency should be driven by kernel exposure and vendor guidance.

Executive priority

Treat as a kernel maintenance item unless vendor guidance indicates broader impact. There is no cited evidence of exploitation or severe impact, but affected kernels should be updated through normal patch cycles, especially on platforms using the relevant driver.

Technical view

The issue is in st_of_quadfs_setup() under Linux kernel clk: st. On failure of st_clk_register_quadfs_pll(), the lock allocation was not freed before the error exit, causing a memory leak. The CVE record lists multiple stable kernel commits as references and affected Linux kernel versions, but no exploitability details.

Likely exposure

Likely limited to Linux kernels containing the affected clk: st code path, especially systems where that driver is built and relevant. The provided affected data lists Linux versions including 3.15, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, and 6.2.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not marked KEV. The described condition occurs when st_clk_register_quadfs_pll() fails, producing a memory leak. Sources do not state whether this is remotely triggerable, locally triggerable, or practically exploitable.

Researcher notes

The record describes a narrow memory-management bug with limited public context. Key unknowns are triggerability, affected hardware configurations, and practical impact. Validation should focus on code presence, backport status, and vendor advisories rather than assumptions from the CVE title alone.

Mitigation direction

  • Check Linux distribution or kernel vendor advisories for CVE-2022-50776 applicability.
  • Update to a vendor-supported kernel containing the referenced stable fix.
  • Prioritize systems using affected kernel versions and the relevant clk: st driver path.
  • If no vendor fix is available, track upstream stable commits and vendor backports.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Determine whether the clk: st driver code is present or enabled.
  • Compare kernel source or changelog against the referenced stable commits.
  • Confirm vendor packages document the CVE fix or equivalent backport.
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-50776 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
10Source 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
LinuxLinux5f7aa9071e935c8c0e869306c7ef073df6c409f6, 5f7aa9071e935c8c0e869306c7ef073df6c409f6, 5f7aa9071e935c8c0e869306c7ef073df6c409f6, 5f7aa9071e935c8c0e869306c7ef073df6c409f6, 5f7aa9071e935c8c0e869306c7ef073df6c409f6, 5f7aa9071e935c8c0e869306c7ef073df6c409f6, 5f7aa9071e935c8c0e869306c7ef073df6c409f6, 5f7aa9071e935c8c0e869306c7ef073df6c409f6, 5f7aa9071e935c8c0e869306c7ef073df6c409f6unaffected
LinuxLinux3.15, 0, 4.9.337, 4.14.303, 4.19.270, 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.