CVE-2022-50355
published 2025-09-17CVE-2022-50355: In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix some erroneous memory clean-up loops In some initialization functions…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.20%
10.1th percentile
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.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.3-1 (bookworm) | linux 6.0.3-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 5341ee0adb17d12a96dc5344e0d267cd12b52135 < 637672a71f5016a40b0a6c0f3c8ad25eacedc8c3 | 637672a71f5016a40b0a6c0f3c8ad25eacedc8c3 |
| linux | linux | >= 5341ee0adb17d12a96dc5344e0d267cd12b52135 < 88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0 | 88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0 |
| linux | linux | >= 5341ee0adb17d12a96dc5344e0d267cd12b52135 < 95ac62e8545be2b0a8cae0beef7c682e2e470e48 | 95ac62e8545be2b0a8cae0beef7c682e2e470e48 |
| linux | linux | >= 5341ee0adb17d12a96dc5344e0d267cd12b52135 < f19e5b7df54590c831f350381963f25585c8f7d5 | f19e5b7df54590c831f350381963f25585c8f7d5 |
| linux | linux | >= 5341ee0adb17d12a96dc5344e0d267cd12b52135 < a9e9806d1c315bc50dce05479a079b9a104474b8 | a9e9806d1c315bc50dce05479a079b9a104474b8 |
| linux | linux | >= 5341ee0adb17d12a96dc5344e0d267cd12b52135 < ed11b73c963292e7b49c0f37025c58ed3b7921d6 | ed11b73c963292e7b49c0f37025c58ed3b7921d6 |
| linux | linux | >= 5341ee0adb17d12a96dc5344e0d267cd12b52135 < 2a2db520e3ca5aafba7c211abfd397666c9b5f9d | 2a2db520e3ca5aafba7c211abfd397666c9b5f9d |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 4.18 < 4.19.262 | 4.19.262 |
| linux | linux_kernel | >= 4.20 < 5.4.220 | 5.4.220 |
| linux | linux_kernel | >= 5.11 < 5.15.75 | 5.15.75 |
| linux | linux_kernel | >= 5.16 < 5.19.17 | 5.19.17 |
| linux | linux_kernel | >= 5.5 < 5.10.150 | 5.10.150 |
| linux | linux_kernel | >= 6.0 < 6.0.3 | 6.0.3 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: staging: vt6655: fix some erroneous memory clean-up loops
vendor_redhat·2025-09-17·CVSS 5.5
CVE-2022-50355 [MEDIUM] kernel: staging: vt6655: fix some erroneous memory clean-up loops
kernel: 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 le
Debian
CVE-2022-50355: linux - In the Linux kernel, the following vulnerability has been resolved: staging: vt...
vendor_debian·2022·CVSS 5.5
CVE-2022-50355 [MEDIUM] CVE-2022-50355: linux - In the Linux kernel, the following vulnerability has been resolved: staging: vt...
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.
Scope: local
bookworm: res
GHSA
GHSA-r7xh-cr9c-6wxq: In the Linux kernel, the following vulnerability has been resolved:
staging: vt6655: fix some erroneous memory clean-up loops
In some initialization
ghsa_unreviewed·2025-09-17
CVE-2022-50355 [MEDIUM] CWE-401 GHSA-r7xh-cr9c-6wxq: In the Linux kernel, the following vulnerability has been resolved:
staging: vt6655: fix some erroneous memory clean-up loops
In some initialization
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.
OSV
CVE-2022-50355: In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix some erroneous memory clean-up loops In some initialization f
osv·2025-09-17·CVSS 5.5
CVE-2022-50355 [MEDIUM] CVE-2022-50355: In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix some erroneous memory clean-up loops In some initialization f
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.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/2a2db520e3ca5aafba7c211abfd397666c9b5f9dhttps://git.kernel.org/stable/c/637672a71f5016a40b0a6c0f3c8ad25eacedc8c3https://git.kernel.org/stable/c/88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0https://git.kernel.org/stable/c/95ac62e8545be2b0a8cae0beef7c682e2e470e48https://git.kernel.org/stable/c/a9e9806d1c315bc50dce05479a079b9a104474b8https://git.kernel.org/stable/c/ed11b73c963292e7b49c0f37025c58ed3b7921d6https://git.kernel.org/stable/c/f19e5b7df54590c831f350381963f25585c8f7d5
2025-09-17
Published