CVE-2022-50123: ASoC: mediatek: mt8173: Fix refcount leak in mt8173_rt5650_rt5676_dev_probe
In the Linux kernel, the following vulnerability has been resolved:
ASoC: mediatek: mt8173: Fix refcount leak in mt8173_rt5650_rt5676_dev_probe
of_parse_phandle() returns a node pointer with refcount
incremented, we should use of_node_put() on it when not need anymore.
Fix missing of_node_put() in error paths.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a resource-management bug in a MediaTek MT8173 audio driver path. The public record describes a missing reference release during probe error handling. No CVSS score, CWE, or exploitation evidence is provided, so business urgency depends on whether affected Linux kernels and this hardware-specific driver exist in your fleet.
Executive priority
Treat as normal patch-cycle work unless you operate MediaTek MT8173-based devices or appliances. There is insufficient public evidence for emergency action, but affected embedded fleets should confirm vendor fixes because kernel resource leaks can reduce reliability over time.
Technical view
The flaw is a refcount leak in mt8173_rt5650_rt5676_dev_probe. of_parse_phandle() increments a device-tree node reference, but some error paths did not call of_node_put(). Kernel stable commits are listed as fixes. The source data does not describe privilege requirements, crashability, or a security boundary impact.
Likely exposure
Likely limited to Linux systems using affected kernel versions with the MediaTek MT8173 ASoC rt5650/rt5676 machine driver path. The bundle does not identify downstream distributions, appliances, or cloud images. Validate against kernel version, vendor backports, device tree, and enabled driver configuration.
Exploitation context
The source bundle does not report active exploitation, public exploit code, KEV listing, or an attack scenario. The described condition is a refcount leak on probe error paths, not a documented remote or user-triggered exploit chain.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploitability analysis, or downstream advisory details are included. The strongest facts are the Linux kernel fix description and stable commit references. Avoid broad claims beyond the MT8173 ASoC driver and listed Linux kernel source records.
Mitigation direction
Check Linux vendor advisories for your exact kernel package and platform.
Apply kernel updates that include the listed stable commits when available.
Prioritize embedded or appliance fleets using MediaTek MT8173 audio hardware.
Track distribution backports instead of relying only on upstream version numbers.
Document exceptions where the affected driver is absent or disabled.
Validation and detection
Inventory Linux kernel versions across managed assets.
Identify systems with MediaTek MT8173 ASoC rt5650/rt5676 driver support enabled.
Confirm vendor kernels include one of the listed upstream stable fixes.
Review boot and driver-probe logs for relevant MediaTek ASoC driver loading.
Record whether exposed systems are vendor-supported and patchable.
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-50123 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.