staging: vt6655: fix some erroneous memory clean-up loops
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5341ee0adb17d12a96dc5344e0d267cd12b52135 · < ed11b73c963292e7b49c0f37025c58ed3b7921d6| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's staging vt6655 driver has faulty cleanup loops during initialization. If memory allocation fails, the loops can leak memory or access invalid memory locations. The input does not establish how an attacker could trigger the failure or whether access or user interaction is required.
Engineers running Linux kernels with the staging vt6655 driver should check whether their kernel includes the fix; affected versions are not specified.