https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 00:06:59 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-05975 bdu:2025-05975 https://cve.radiocsirt.org/vuln/bdu:2025-05975 https://cve.radiocsirt.org/vuln/bell-cve-2024-46823 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-46823 https://cve.radiocsirt.org/vuln/certfr-2024-avi-1080 certfr-2024-avi-1080 https://cve.radiocsirt.org/vuln/certfr-2024-avi-1080 https://cve.radiocsirt.org/vuln/euvd-2026-346136 EUVD-2026-346136 https://cve.radiocsirt.org/vuln/euvd-2026-346136 https://cve.radiocsirt.org/vuln/fkie_cve-2024-46823 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kunit/overflow: Fix UB in overflow_allocation_test</p> <p>The &#39;device_name&#39; array doesn&#39;t exist out of the &#39;overflow_allocation_test&#39; function scope. However, it is being used as a driver name when calling &#39;kunit_driver_create&#39; from &#39;kunit_device_register&#39;. It produces the kernel panic with KASAN enabled.</p> <p>Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kunit/overflow: Fix UB in overflow_allocation_test</p> <p>The &#39;device_name&#39; array doesn&#39;t exist out of the &#39;overflow_allocation_test&#39; function scope. However, it is being used as a driver name when calling &#39;kunit_driver_create&#39; from &#39;kunit_device_register&#39;. It produces the kernel panic with KASAN enabled.</p> <p>Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-46823 https://cve.radiocsirt.org/vuln/ghsa-hm28-rwr4-j8f5 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kunit/overflow: Fix UB in overflow_allocation_test</p> <p>The &#39;device_name&#39; array doesn&#39;t exist out of the &#39;overflow_allocation_test&#39; function scope. However, it is being used as a driver name when calling &#39;kunit_driver_create&#39; from &#39;kunit_device_register&#39;. It produces the kernel panic with KASAN enabled.</p> <p>Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kunit/overflow: Fix UB in overflow_allocation_test</p> <p>The &#39;device_name&#39; array doesn&#39;t exist out of the &#39;overflow_allocation_test&#39; function scope. However, it is being used as a driver name when calling &#39;kunit_driver_create&#39; from &#39;kunit_device_register&#39;. It produces the kernel panic with KASAN enabled.</p> <p>Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.</p> https://cve.radiocsirt.org/vuln/ghsa-hm28-rwr4-j8f5 https://cve.radiocsirt.org/vuln/msrc_cve-2024-46823 msrc_CVE-2024-46823 https://cve.radiocsirt.org/vuln/msrc_cve-2024-46823 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46823 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 188 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: kunit/overflow: Fix UB in overflow_allocation_test The &#39;device_name&#39; array doesn&#39;t exist out of the &#39;overflow_allocation_test&#39; function scope. However, it is being used as a driver name when calling &#39;kunit_driver_create&#39; from &#39;kunit_device_register&#39;. It produces the kernel panic with KASAN enabled. Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 188 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: kunit/overflow: Fix UB in overflow_allocation_test The &#39;device_name&#39; array doesn&#39;t exist out of the &#39;overflow_allocation_test&#39; function scope. However, it is being used as a driver name when calling &#39;kunit_driver_create&#39; from &#39;kunit_device_register&#39;. It produces the kernel panic with KASAN enabled. Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46823 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3050 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht spezifizierte Auswirkungen zu verursachen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht spezifizierte Auswirkungen zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3050