https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:02:02 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-11090 bdu:2026-11090 https://cve.radiocsirt.org/vuln/bdu:2026-11090 https://cve.radiocsirt.org/vuln/bell-cve-2026-43150 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-43150 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0782 certfr-2026-avi-0782 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0782 https://cve.radiocsirt.org/vuln/euvd-2026-347839 EUVD-2026-347839 https://cve.radiocsirt.org/vuln/euvd-2026-347839 https://cve.radiocsirt.org/vuln/fkie_cve-2026-43150 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>perf/arm-cmn: Reject unsupported hardware configurations</p> <p>So far we&#39;ve been fairly lax about accepting both unknown CMN models (at least with a warning), and unknown revisions of those which we do know, as although things do frequently change between releases, typically enough remains the same to be somewhat useful for at least some basic bringup checks. However, we also make assumptions of the maximum supported sizes and numbers of things in various places, and there&#39;s no guarantee that something new might not be bigger and lead to nasty array overflows. Make sure we only try to run on things that actually match our assumptions and so will not risk memory corruption.</p> <p>We have at least always failed on completely unknown node types, so update that error message for clarity and consistency too.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>perf/arm-cmn: Reject unsupported hardware configurations</p> <p>So far we&#39;ve been fairly lax about accepting both unknown CMN models (at least with a warning), and unknown revisions of those which we do know, as although things do frequently change between releases, typically enough remains the same to be somewhat useful for at least some basic bringup checks. However, we also make assumptions of the maximum supported sizes and numbers of things in various places, and there&#39;s no guarantee that something new might not be bigger and lead to nasty array overflows. Make sure we only try to run on things that actually match our assumptions and so will not risk memory corruption.</p> <p>We have at least always failed on completely unknown node types, so update that error message for clarity and consistency too.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-43150 https://cve.radiocsirt.org/vuln/ghsa-wh2v-8c6h-56m5 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>perf/arm-cmn: Reject unsupported hardware configurations</p> <p>So far we&#39;ve been fairly lax about accepting both unknown CMN models (at least with a warning), and unknown revisions of those which we do know, as although things do frequently change between releases, typically enough remains the same to be somewhat useful for at least some basic bringup checks. However, we also make assumptions of the maximum supported sizes and numbers of things in various places, and there&#39;s no guarantee that something new might not be bigger and lead to nasty array overflows. Make sure we only try to run on things that actually match our assumptions and so will not risk memory corruption.</p> <p>We have at least always failed on completely unknown node types, so update that error message for clarity and consistency too.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>perf/arm-cmn: Reject unsupported hardware configurations</p> <p>So far we&#39;ve been fairly lax about accepting both unknown CMN models (at least with a warning), and unknown revisions of those which we do know, as although things do frequently change between releases, typically enough remains the same to be somewhat useful for at least some basic bringup checks. However, we also make assumptions of the maximum supported sizes and numbers of things in various places, and there&#39;s no guarantee that something new might not be bigger and lead to nasty array overflows. Make sure we only try to run on things that actually match our assumptions and so will not risk memory corruption.</p> <p>We have at least always failed on completely unknown node types, so update that error message for clarity and consistency too.</p> https://cve.radiocsirt.org/vuln/ghsa-wh2v-8c6h-56m5 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20965-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:20965-1 https://cve.radiocsirt.org/vuln/suse-su-2026:22099-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:22099-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43150 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 140 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: perf/arm-cmn: Reject unsupported hardware configurations So far we&#39;ve been fairly lax about accepting both unknown CMN models (at least with a warning), and unknown revisions of those which we do know, as although things do frequently change between releases, typically enough remains the same to be somewhat useful for at least some basic bringup checks. However, we also make assumptions of the maximum supported sizes and numbers of things in various places, and there&#39;s no guarantee that something new might not be bigger and lead to nasty array overflows. Make sure we only try to run on things that actually match our assumptions and so will not risk memory corruption. We have at least always failed on completely unknown node types, so update that error message for clarity and consistency too.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 140 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: perf/arm-cmn: Reject unsupported hardware configurations So far we&#39;ve been fairly lax about accepting both unknown CMN models (at least with a warning), and unknown revisions of those which we do know, as although things do frequently change between releases, typically enough remains the same to be somewhat useful for at least some basic bringup checks. However, we also make assumptions of the maximum supported sizes and numbers of things in various places, and there&#39;s no guarantee that something new might not be bigger and lead to nasty array overflows. Make sure we only try to run on things that actually match our assumptions and so will not risk memory corruption. We have at least always failed on completely unknown node types, so update that error message for clarity and consistency too.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43150 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405