https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:28:55 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895 certfr-2025-avi-0895 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895 https://cve.radiocsirt.org/vuln/euvd-2026-344898 EUVD-2026-344898 https://cve.radiocsirt.org/vuln/euvd-2026-344898 https://cve.radiocsirt.org/vuln/fkie_cve-2022-50355 <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>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://cve.radiocsirt.org/vuln/fkie_cve-2022-50355 https://cve.radiocsirt.org/vuln/ghsa-r7xh-cr9c-6wxq <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>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://cve.radiocsirt.org/vuln/ghsa-r7xh-cr9c-6wxq https://cve.radiocsirt.org/vuln/suse-su-2025:03613-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:03613-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50355 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 127 more</p> <p>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 &#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. 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> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 127 more</p> <p>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 &#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. 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://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50355 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2087 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2087