LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49399: tty: goldfish: Use tty_port_destroy() to destroy port

In the Linux kernel, the following vulnerability has been resolved: tty: goldfish: Use tty_port_destroy() to destroy port In goldfish_tty_probe(), the port initialized through tty_port_init() should be destroyed in error paths.In goldfish_tty_remove(), qtty->port also should be destroyed or else might leak resources. Fix the above by calling tty_port_destroy().

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-49399 is a Linux kernel resource cleanup flaw in the goldfish TTY driver. When setup fails or the driver is removed, the port may not be destroyed correctly, causing resource leakage. The source bundle provides no CVSS score, no CWE, and no evidence of active exploitation.

Executive priority

Handle through normal kernel patch management unless goldfish TTY is used in sensitive environments. There is no cited active exploitation or severity score, but kernel cleanup flaws should not be left indefinitely unpatched.

Technical view

The issue is in goldfish_tty_probe() and goldfish_tty_remove(). A tty_port initialized with tty_port_init() was not consistently released with tty_port_destroy() on error paths or removal. Stable kernel commits add the missing tty_port_destroy() calls. Impact details beyond resource leakage are not specified in the provided sources.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions or branch states with the goldfish TTY driver present. The bundle lists Linux 3.9 through 5.19-related versions, but distribution package mapping is not provided.

Exploitation context

The provided sources do not report public exploitation, weaponized exploit availability, or CISA KEV listing. Based only on the bundle, this should be treated as a kernel maintenance vulnerability with unclear real-world exploitability.

Researcher notes

The evidence supports a missing destructor/resource leak in Linux tty/goldfish lifecycle handling. The bundle does not define attack preconditions, privilege requirements, crash impact, or confidentiality/integrity effects, so validation should focus on affected kernel lineage and driver reachability.

Mitigation direction

  • Update to a Linux kernel build containing the referenced stable fixes.
  • Check your Linux distribution security advisory for package-level fixed versions.
  • Prioritize systems where the goldfish TTY driver is built or loaded.
  • Track the CVE record for any later CVSS or exploitability update.

Validation and detection

  • Inventory kernel versions across affected Linux hosts.
  • Check whether the goldfish TTY driver is present, built, or loaded.
  • Confirm installed kernel packages include one of the referenced fixes.
  • Review vendor advisories for backported fixes under different package versions.
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-49399 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
LinuxLinux666b7793d4bfa9f150b5c2007ab48c755ddc53ca, 666b7793d4bfa9f150b5c2007ab48c755ddc53ca, 666b7793d4bfa9f150b5c2007ab48c755ddc53ca, 666b7793d4bfa9f150b5c2007ab48c755ddc53ca, 666b7793d4bfa9f150b5c2007ab48c755ddc53ca, 666b7793d4bfa9f150b5c2007ab48c755ddc53ca, 666b7793d4bfa9f150b5c2007ab48c755ddc53ca, 666b7793d4bfa9f150b5c2007ab48c755ddc53caunaffected
LinuxLinux3.9, 0, 4.14.283, 4.19.247, 5.4.198, 5.10.122, 5.15.47, 5.17.15, 5.18.4, 5.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.