LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50019: tty: serial: Fix refcount leak bug in ucc_uart.c

In the Linux kernel, the following vulnerability has been resolved: tty: serial: Fix refcount leak bug in ucc_uart.c In soc_info(), of_find_node_by_type() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.

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-50019 is a Linux kernel bug where a device-tree node reference is not released in the ucc_uart serial driver. The public record describes a refcount leak, not direct code execution or privilege escalation. Business urgency is mainly for systems that ship or rely on affected Linux kernel builds with this driver enabled.

Executive priority

Handle through normal kernel patch governance unless the environment uses affected custom or embedded Linux builds. Escalate if vendor guidance links this bug to availability impact on critical systems.

Technical view

In ucc_uart.c, soc_info() calls of_find_node_by_type(), which increments a node reference count. The fix adds the matching of_node_put() when the node is no longer needed. The available sources do not provide CVSS, CWE, impact detail, or distribution-specific package status.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or vendor kernels containing the vulnerable ucc_uart.c code. The bundle does not identify affected distributions, devices, configurations, or whether the driver must be active.

Exploitation context

The source bundle shows no CISA KEV listing and provides no evidence of active exploitation, public exploit availability, or weaponized use. Treat this as a kernel maintenance vulnerability until vendor advisories add impact detail.

Researcher notes

Evidence is sparse: the record only states a refcount leak in soc_info() and lists stable kernel commit references. No CVSS, CWE, exploit conditions, trigger path, or operational impact is supplied, so validation should focus on source/package provenance.

Mitigation direction

  • Check your Linux vendor advisory for CVE-2022-50019 package status.
  • Update to a kernel build containing the referenced stable fixes.
  • Prioritize embedded or appliance fleets using customized Linux kernels.
  • Track unsupported kernels separately and plan replacement or backporting.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and embedded devices.
  • Confirm whether vendor kernels include ucc_uart.c and the stable fix.
  • Map findings against the CVE affected version data and vendor advisories.
  • Document any systems awaiting vendor-fixed kernels or backports.
Prepared
Confidence
medium
Sources
10

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-50019 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
9Source 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
LinuxLinuxd7584ed2b994a572326650b0c4d2c25961e6f49d, d7584ed2b994a572326650b0c4d2c25961e6f49d, d7584ed2b994a572326650b0c4d2c25961e6f49d, d7584ed2b994a572326650b0c4d2c25961e6f49d, d7584ed2b994a572326650b0c4d2c25961e6f49d, d7584ed2b994a572326650b0c4d2c25961e6f49d, d7584ed2b994a572326650b0c4d2c25961e6f49d, d7584ed2b994a572326650b0c4d2c25961e6f49dunaffected
LinuxLinux2.6.25, 0, 4.9.326, 4.14.291, 4.19.256, 5.4.211, 5.10.138, 5.15.63, 5.19.4, 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.