LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50557: pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()

In the Linux kernel, the following vulnerability has been resolved: pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions() The thunderbay_add_functions() will free memory of thunderbay_funcs when everything is ok, but thunderbay_funcs will not be freed when thunderbay_add_functions() fails, then there will be a memory leak, so we need to add kfree() when thunderbay_add_functions() fails to fix it. In addition, doing some cleaner works, moving kfree(funcs) from thunderbay_add_functions() to thunderbay_build_functions().

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

Security readout for executives and security teams

Plain-English summary

This CVE describes a Linux kernel memory leak in the Thunder Bay pin control driver. If an internal function fails, allocated memory may not be released. The sources do not show remote exposure, active exploitation, or a CVSS score.

Executive priority

Treat as routine kernel hygiene unless your environment uses Thunder Bay platforms. There is no sourced evidence of exploitation, but patched kernels should be adopted through normal maintenance because kernel memory leaks can affect reliability.

Technical view

The issue is in thunderbay_build_functions(), where thunderbay_funcs was not freed when thunderbay_add_functions() failed. Stable kernel commits move cleanup ownership and add kfree() on the failure path. The record does not identify a CWE or quantified severity.

Likely exposure

Likely limited to Linux systems using affected kernel versions with the Thunder Bay pinctrl driver present and relevant hardware or configuration. General Linux servers without this driver path are less likely to be exposed, but the provided affected-version data is incomplete.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The available description points to a memory leak on an error path, not a documented privilege escalation, remote code execution, or public exploit.

Researcher notes

The source record is sparse: no CVSS, CWE, exploit evidence, or detailed affected-version ranges beyond Linux kernel identifiers. Analysis should focus on commit inclusion, distro backports, and whether the Thunder Bay pinctrl code is reachable in the target environment.

Mitigation direction

  • Apply vendor kernel updates that include the cited stable fixes.
  • Check Linux distribution advisories for backported fixes.
  • Prioritize systems using Thunder Bay-related kernel support.
  • Avoid claiming remediation until the running kernel includes the fix.

Validation and detection

  • Inventory running Linux kernel versions across affected assets.
  • Confirm whether Thunder Bay pinctrl support is built or loaded.
  • Compare deployed kernels against vendor-fixed releases or cited commits.
  • Review distribution security notices for backport status.
Prepared
Confidence
medium
Sources
5

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-50557 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
4Source 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
LinuxLinux12422af8194df85243d68b11f8783de9d01e58dc, 12422af8194df85243d68b11f8783de9d01e58dc, 12422af8194df85243d68b11f8783de9d01e58dcunaffected
LinuxLinux5.17, 0, 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.