CVE-2022-50355 (GCVE-0-2022-50355)
Vulnerability from cvelistv5
Published
2025-09-17 14:56
Modified
2025-09-17 14:56
Severity ?
Summary
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.
Impacted products
Vendor Product Version
Linux Linux Version: 5341ee0adb17d12a96dc5344e0d267cd12b52135
Version: 5341ee0adb17d12a96dc5344e0d267cd12b52135
Version: 5341ee0adb17d12a96dc5344e0d267cd12b52135
Version: 5341ee0adb17d12a96dc5344e0d267cd12b52135
Version: 5341ee0adb17d12a96dc5344e0d267cd12b52135
Version: 5341ee0adb17d12a96dc5344e0d267cd12b52135
Version: 5341ee0adb17d12a96dc5344e0d267cd12b52135
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/staging/vt6655/device_main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "637672a71f5016a40b0a6c0f3c8ad25eacedc8c3",
              "status": "affected",
              "version": "5341ee0adb17d12a96dc5344e0d267cd12b52135",
              "versionType": "git"
            },
            {
              "lessThan": "88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0",
              "status": "affected",
              "version": "5341ee0adb17d12a96dc5344e0d267cd12b52135",
              "versionType": "git"
            },
            {
              "lessThan": "95ac62e8545be2b0a8cae0beef7c682e2e470e48",
              "status": "affected",
              "version": "5341ee0adb17d12a96dc5344e0d267cd12b52135",
              "versionType": "git"
            },
            {
              "lessThan": "f19e5b7df54590c831f350381963f25585c8f7d5",
              "status": "affected",
              "version": "5341ee0adb17d12a96dc5344e0d267cd12b52135",
              "versionType": "git"
            },
            {
              "lessThan": "a9e9806d1c315bc50dce05479a079b9a104474b8",
              "status": "affected",
              "version": "5341ee0adb17d12a96dc5344e0d267cd12b52135",
              "versionType": "git"
            },
            {
              "lessThan": "ed11b73c963292e7b49c0f37025c58ed3b7921d6",
              "status": "affected",
              "version": "5341ee0adb17d12a96dc5344e0d267cd12b52135",
              "versionType": "git"
            },
            {
              "lessThan": "2a2db520e3ca5aafba7c211abfd397666c9b5f9d",
              "status": "affected",
              "version": "5341ee0adb17d12a96dc5344e0d267cd12b52135",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/staging/vt6655/device_main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.18"
            },
            {
              "lessThan": "4.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "4.19.*",
              "status": "unaffected",
              "version": "4.19.262",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.4.*",
              "status": "unaffected",
              "version": "5.4.220",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.150",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.75",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.19.*",
              "status": "unaffected",
              "version": "5.19.17",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.0.*",
              "status": "unaffected",
              "version": "6.0.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "4.19.262",
                  "versionStartIncluding": "4.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.4.220",
                  "versionStartIncluding": "4.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.150",
                  "versionStartIncluding": "4.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.75",
                  "versionStartIncluding": "4.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.19.17",
                  "versionStartIncluding": "4.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.0.3",
                  "versionStartIncluding": "4.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1",
                  "versionStartIncluding": "4.18",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nstaging: vt6655: fix some erroneous memory clean-up loops\n\nIn some initialization functions of this driver, memory is allocated with\n\u0027i\u0027 acting as an index variable and increasing from 0. The commit in\n\"Fixes\" introduces some clean-up codes in case of allocation failure,\nwhich free memory in reverse order with \u0027i\u0027 decreasing to 0. However,\nthere are some problems:\n  - The case i=0 is left out. Thus memory is leaked.\n  - In case memory allocation fails right from the start, the memory\n    freeing loops will start with i=-1 and invalid memory locations will\n    be accessed.\n\nOne of these loops has been fixed in commit c8ff91535880 (\"staging:\nvt6655: fix potential memory leak\"). Fix the remaining erroneous loops."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-09-17T14:56:08.356Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/637672a71f5016a40b0a6c0f3c8ad25eacedc8c3"
        },
        {
          "url": "https://git.kernel.org/stable/c/88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0"
        },
        {
          "url": "https://git.kernel.org/stable/c/95ac62e8545be2b0a8cae0beef7c682e2e470e48"
        },
        {
          "url": "https://git.kernel.org/stable/c/f19e5b7df54590c831f350381963f25585c8f7d5"
        },
        {
          "url": "https://git.kernel.org/stable/c/a9e9806d1c315bc50dce05479a079b9a104474b8"
        },
        {
          "url": "https://git.kernel.org/stable/c/ed11b73c963292e7b49c0f37025c58ed3b7921d6"
        },
        {
          "url": "https://git.kernel.org/stable/c/2a2db520e3ca5aafba7c211abfd397666c9b5f9d"
        }
      ],
      "title": "staging: vt6655: fix some erroneous memory clean-up loops",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-50355",
    "datePublished": "2025-09-17T14:56:08.356Z",
    "dateReserved": "2025-09-17T14:53:06.993Z",
    "dateUpdated": "2025-09-17T14:56:08.356Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2022-50355\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-09-17T15:15:34.150\",\"lastModified\":\"2025-09-18T13:43:34.310\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nstaging: vt6655: fix some erroneous memory clean-up loops\\n\\nIn some initialization functions of this driver, memory is allocated with\\n\u0027i\u0027 acting as an index variable and increasing from 0. The commit in\\n\\\"Fixes\\\" introduces some clean-up codes in case of allocation failure,\\nwhich free memory in reverse order with \u0027i\u0027 decreasing to 0. However,\\nthere are some problems:\\n  - The case i=0 is left out. Thus memory is leaked.\\n  - In case memory allocation fails right from the start, the memory\\n    freeing loops will start with i=-1 and invalid memory locations will\\n    be accessed.\\n\\nOne of these loops has been fixed in commit c8ff91535880 (\\\"staging:\\nvt6655: fix potential memory leak\\\"). Fix the remaining erroneous loops.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/2a2db520e3ca5aafba7c211abfd397666c9b5f9d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/637672a71f5016a40b0a6c0f3c8ad25eacedc8c3\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/95ac62e8545be2b0a8cae0beef7c682e2e470e48\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a9e9806d1c315bc50dce05479a079b9a104474b8\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/ed11b73c963292e7b49c0f37025c58ed3b7921d6\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f19e5b7df54590c831f350381963f25585c8f7d5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…