CVE-2022-50355
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.
How to fix
- linux linux_kernel4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| linux linux_kernel | 4.18 ≤ v < 4.19.262, 4.20 ≤ v < 5.4.220, 5.5 ≤ v < 5.10.150, 5.11 ≤ v < 5.15.75, 5.16 ≤ v < 5.19.17, 6.0 ≤ v < 6.0.3 | 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.