LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50355: staging: vt6655: fix some erroneous memory clean-up loops

In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix some erroneous memory clean-up loops In some initialization functions of this driver, memory is allocated with 'i' acting as an index variable and increasing from 0. The commit in "Fixes" introduces some clean-up codes in case of allocation failure, which free memory in reverse order with 'i' decreasing to 0. However, there are some problems: - The case i=0 is left out. Thus memory is leaked. - In case memory allocation fails right from the start, the memory freeing loops will start with i=-1 and invalid memory locations will be accessed. One of these loops has been fixed in commit c8ff91535880 ("staging: vt6655: fix potential memory leak"). Fix the remaining erroneous loops.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel availability issue in the vt6655 staging wireless driver. A local low-privileged user could potentially trigger a crash or denial of service when driver initialization cleanup handles allocation failure incorrectly. The sources do not indicate data theft, privilege escalation, or active exploitation.

Executive priority

Treat as a routine but real availability patching item. Prioritize systems that allow local user access and include the vt6655 driver. It does not currently justify emergency response based on the provided evidence.

Technical view

Erroneous reverse cleanup loops in vt6655 initialization may skip index zero or start from -1 after early allocation failure. That can leak memory or access invalid memory. CVSS 3.1 is 5.5: local attack vector, low privileges, no user interaction, availability impact only.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds with the vt6655 staging driver present or loadable. General servers without this driver or hardware path are less likely to be exposed.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. Exploitation requires local access with low privileges and appears focused on denial of service, not remote compromise.

Researcher notes

The vulnerability is in error-path cleanup logic, not normal packet processing. Validation should focus on source version matching, module reachability, and vendor backport confirmation. The record names CWE-401, but also describes invalid memory access when allocation fails immediately.

Mitigation direction

  • Identify systems using affected Linux kernel versions and the vt6655 driver.
  • Prioritize kernel updates that include the referenced stable fixes.
  • Check distribution vendor advisories for packaged fixed kernel releases.
  • Disable or avoid loading vt6655 where it is unnecessary.
  • Apply normal local access controls to limit untrusted users.

Validation and detection

  • Inventory kernel versions across Linux assets.
  • Check whether the vt6655 module is present or loaded.
  • Confirm vendor kernel changelogs include one referenced stable commit.
  • Regression test wireless functionality after kernel updates.
  • Monitor for local kernel crash or denial-of-service reports.
Prepared
Confidence
high
Sources
9

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.

cwe · low confidence lookup

CWE-401: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-50355 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-50355Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5341ee0adb17d12a96dc5344e0d267cd12b52135, 5341ee0adb17d12a96dc5344e0d267cd12b52135, 5341ee0adb17d12a96dc5344e0d267cd12b52135, 5341ee0adb17d12a96dc5344e0d267cd12b52135, 5341ee0adb17d12a96dc5344e0d267cd12b52135, 5341ee0adb17d12a96dc5344e0d267cd12b52135, 5341ee0adb17d12a96dc5344e0d267cd12b52135unaffected
LinuxLinux4.18, 0, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

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

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.