LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50139: usb: aspeed-vhub: Fix refcount leak bug in ast_vhub_init_desc()

In the Linux kernel, the following vulnerability has been resolved: usb: aspeed-vhub: Fix refcount leak bug in ast_vhub_init_desc() We should call of_node_put() for the reference returned by of_get_child_by_name() which has increased the refcount.

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 the ASPEED virtual USB hub driver. The code failed to release a device-tree reference during descriptor initialization, creating a reference-count leak. The public record does not provide CVSS, impact details, or evidence of exploitation, so business urgency depends on whether affected kernels use this driver.

Executive priority

Treat this as a targeted kernel maintenance issue, not an emergency, unless affected ASPEED vhub systems are business-critical. Patch through normal kernel update channels once exposure is confirmed.

Technical view

CVE-2022-50139 fixes a missing of_node_put() after of_get_child_by_name() in ast_vhub_init_desc(). The issue is a kernel reference-count leak in usb/aspeed-vhub. The source bundle lists Linux kernel affected ranges with stable fixes including 5.10.137, 5.15.61, 5.18.18, 5.19.2, and 6.0.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds where the ASPEED virtual USB hub driver is present and relevant. The bundle does not identify remote attack surface, privileges required, or affected distributions.

Exploitation context

No active exploitation is reported in the provided sources, and this CVE is not marked KEV. The sources describe a refcount leak fix, not an exploit technique, weaponized proof of concept, or observed campaign.

Researcher notes

The record lacks CVSS, CWE, exploitability, and concrete impact. Analysis should focus on code lineage, fixed stable commits, driver reachability, and whether downstream vendors backported the missing of_node_put() fix.

Mitigation direction

  • Identify kernels in affected ranges and map them to vendor-supported fixed builds.
  • Prioritize systems using or enabling the ASPEED virtual USB hub driver.
  • Apply kernel updates containing the referenced stable fixes when available.
  • Check Linux distribution advisories for package-specific backports and support status.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Check whether the ASPEED virtual USB hub driver is built, loaded, or enabled.
  • Confirm vendor kernels include the referenced upstream stable commits or equivalent backports.
  • Review logs and stability history for symptoms only after confirming driver exposure.
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-50139 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
LinuxLinux30d2617fd7ed052c30d1c21ddd4af4703d922be8, 30d2617fd7ed052c30d1c21ddd4af4703d922be8, 30d2617fd7ed052c30d1c21ddd4af4703d922be8, 30d2617fd7ed052c30d1c21ddd4af4703d922be8, 30d2617fd7ed052c30d1c21ddd4af4703d922be8unaffected
LinuxLinux5.8, 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.