LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50125: ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe

In the Linux kernel, the following vulnerability has been resolved: ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe of_parse_phandle() 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 analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50125 is a Linux kernel bug where a reference count is not released in the cros_ec_codec probe path. The public record describes a resource leak, not remote code execution or data theft. Business urgency is unclear because no CVSS score, CWE, or impact detail is provided.

Executive priority

Handle through normal kernel maintenance and vulnerability management. Escalate only if a vendor advisory links it to service impact, exploitation, or affected critical platforms in your environment.

Technical view

The bug is in ASoC cros_ec_codec_platform_probe. of_parse_phandle() increments a device-tree node reference, but the driver failed to call of_node_put() when done. Stable kernel commits add the missing release to avoid the refcount leak.

Likely exposure

Exposure appears limited to Linux kernels containing the affected cros_ec_codec code path. The source lists Linux as affected and provides stable kernel fix commits, but it does not identify distributions, appliances, or runtime prerequisites beyond the kernel driver context.

Exploitation context

The provided sources do not show active exploitation, KEV listing, exploit availability, or a practical attack path. Treat this as a kernel resource-management defect until vendor advisories provide impact or exploitability detail.

Researcher notes

The evidence supports a missing of_node_put() after of_parse_phandle(), causing a refcount leak. Public metadata lacks CVSS, CWE, threat model, and distribution-level affected package mapping, so exposure validation should rely on kernel source or vendor backport tracking.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fix status.
  • Inventory systems using kernels in the affected version ranges.
  • Prioritize standard kernel patching over emergency response unless vendor impact changes.

Validation and detection

  • Compare running kernel versions with vendor advisory status.
  • Confirm the relevant stable fix commit is present or backported.
  • Check whether cros_ec_codec is built or loaded on exposed systems.
  • Document any systems awaiting vendor-provided patched kernels.
Prepared
Confidence
medium
Sources
7

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-50125 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
6Source 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
LinuxLinuxb6bc07d4360dbf766e551f18e43c67fff6784955, b6bc07d4360dbf766e551f18e43c67fff6784955, b6bc07d4360dbf766e551f18e43c67fff6784955, b6bc07d4360dbf766e551f18e43c67fff6784955, b6bc07d4360dbf766e551f18e43c67fff6784955unaffected
LinuxLinux5.5, 0, 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.