Answer in brief
CVE-2022-50355 records a High severity (CVSS 7.8) vulnerability in staging: vt6655: fix some erroneous memory clean-up loops. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-50355 records a High severity (CVSS 7.8) vulnerability in staging: vt6655: fix some erroneous memory clean-up loops. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <637672a71f5016a40b0a6c0f3c8ad25eacedc8c3 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <95ac62e8545be2b0a8cae0beef7c682e2e470e48 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <f19e5b7df54590c831f350381963f25585c8f7d5 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <a9e9806d1c315bc50dce05479a079b9a104474b8 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <ed11b73c963292e7b49c0f37025c58ed3b7921d6 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <2a2db520e3ca5aafba7c211abfd397666c9b5f9d | 637672a71f5016a40b0a6c0f3c8ad25eacedc8c3, 88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0, 95ac62e8545be2b0a8cae0beef7c682e2e470e48, f19e5b7df54590c831f350381963f25585c8f7d5, a9e9806d1c315bc50dce05479a079b9a104474b8, ed11b73c963292e7b49c0f37025c58ed3b7921d6, 2a2db520e3ca5aafba7c211abfd397666c9b5f9d |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Sep 17, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <637672a71f5016a40b0a6c0f3c8ad25eacedc8c3 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <95ac62e8545be2b0a8cae0beef7c682e2e470e48 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <f19e5b7df54590c831f350381963f25585c8f7d5 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <a9e9806d1c315bc50dce05479a079b9a104474b8 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <ed11b73c963292e7b49c0f37025c58ed3b7921d6 || >=5341ee0adb17d12a96dc5344e0d267cd12b52135 <2a2db520e3ca5aafba7c211abfd397666c9b5f9d | 637672a71f5016a40b0a6c0f3c8ad25eacedc8c3, 88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0, 95ac62e8545be2b0a8cae0beef7c682e2e470e48, f19e5b7df54590c831f350381963f25585c8f7d5, a9e9806d1c315bc50dce05479a079b9a104474b8, ed11b73c963292e7b49c0f37025c58ed3b7921d6, 2a2db520e3ca5aafba7c211abfd397666c9b5f9d |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Sep 17, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.