Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50355

staging: vt6655: fix some erroneous memory clean-up loops

High7.8EPSS 0.22%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Scores

CVSS scores of CVE-2022-50355, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < 637672a71f5016a40b0a6c0f3c8ad25eacedc8c3
    • affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < 88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0
    • affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < 95ac62e8545be2b0a8cae0beef7c682e2e470e48
    • affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < f19e5b7df54590c831f350381963f25585c8f7d5
    • affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < a9e9806d1c315bc50dce05479a079b9a104474b8
    • affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < ed11b73c963292e7b49c0f37025c58ed3b7921d6
    • affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < 2a2db520e3ca5aafba7c211abfd397666c9b5f9d
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 4.19.262 – ≤ 4.19.*
    • unaffected 5.4.220 – ≤ 5.4.*
    • unaffected 5.10.150 – ≤ 5.10.*
    • unaffected 5.15.75 – ≤ 5.15.*
    • unaffected 5.19.17 – ≤ 5.19.*
    • unaffected 6.0.3 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (7)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50355 badge
[![CVE-2022-50355](https://trackcve.app/badge/CVE-2022-50355.svg)](https://trackcve.app/cve/CVE-2022-50355)

Record last updated .