LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50208: soc: amlogic: Fix refcount leak in meson-secure-pwrc.c

In the Linux kernel, the following vulnerability has been resolved: soc: amlogic: Fix refcount leak in meson-secure-pwrc.c In meson_secure_pwrc_probe(), there is a refcount leak in one fail path.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in an Amlogic SoC power-controller driver. A failure path can leak a reference count during device probing. The public record does not provide CVSS, CWE, impact detail, or evidence of exploitation, so business urgency depends on whether affected kernels run on relevant Amlogic-based devices.

Executive priority

Treat this as a targeted kernel hygiene item, not an emergency based on current evidence. Prioritize confirmation for Amlogic-based embedded or appliance assets, then remediate through normal kernel or firmware update channels.

Technical view

The issue is a refcount leak in meson_secure_pwrc_probe() within meson-secure-pwrc.c. The available description limits the flaw to one probe failure path. Stable kernel commits are listed as references, but the source bundle does not describe a practical attack path, privilege requirement, or security impact beyond resource/reference leakage.

Likely exposure

Likely exposure is limited to Linux systems using affected kernel builds with the Amlogic Meson secure power controller code enabled. The affected-version metadata lists Linux and several kernel version entries, but downstream distribution backports require vendor-specific verification.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization. The record also does not explain whether an attacker can reliably trigger the probe failure path in real deployments.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed impact is provided. Analysis should focus on commit review, driver reachability, probe failure conditions, and whether downstream kernels include the stable fix or equivalent backport.

Mitigation direction

  • Check kernel vendor advisories for CVE-2022-50208 applicability and fixed package versions.
  • Prioritize Amlogic-based devices running affected Linux kernels or vendor forks.
  • Upgrade to a kernel containing the referenced stable fixes when available from your vendor.
  • Track embedded or appliance firmware separately, because fixes may arrive through OEM images.

Validation and detection

  • Inventory Linux kernel versions across servers, devices, appliances, and embedded fleets.
  • Identify systems using Amlogic SoCs or meson-secure-pwrc driver support.
  • Compare deployed kernel source or changelog against the referenced stable commits.
  • Confirm distribution or OEM advisories map CVE-2022-50208 to installed packages.
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-50208 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
LinuxLinuxb3dde5013e13d44799b3477cd0bf0c9ad34fe5e9, b3dde5013e13d44799b3477cd0bf0c9ad34fe5e9, b3dde5013e13d44799b3477cd0bf0c9ad34fe5e9, b3dde5013e13d44799b3477cd0bf0c9ad34fe5e9, b3dde5013e13d44799b3477cd0bf0c9ad34fe5e9unaffected
LinuxLinux5.7, 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.