https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 13:40:56 +0000 https://vulnerability.circl.lu/vuln/cve-2022-50355 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>staging: vt6655: fix some erroneous memory clean-up loops</p> <p>In some initialization functions of this driver, memory is allocated with &#39;i&#39; acting as an index variable and increasing from 0. The commit in &#34;Fixes&#34; introduces some clean-up codes in case of allocation failure, which free memory in reverse order with &#39;i&#39; 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.</p> <p>One of these loops has been fixed in commit c8ff91535880 (&#34;staging: vt6655: fix potential memory leak&#34;). Fix the remaining erroneous loops.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>staging: vt6655: fix some erroneous memory clean-up loops</p> <p>In some initialization functions of this driver, memory is allocated with &#39;i&#39; acting as an index variable and increasing from 0. The commit in &#34;Fixes&#34; introduces some clean-up codes in case of allocation failure, which free memory in reverse order with &#39;i&#39; 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.</p> <p>One of these loops has been fixed in commit c8ff91535880 (&#34;staging: vt6655: fix potential memory leak&#34;). Fix the remaining erroneous loops.</p> https://vulnerability.circl.lu/vuln/cve-2022-50355