https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 11:22:46 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-46026 <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-46026 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0731 certfr-2026-avi-0731 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0731 https://cve.radiocsirt.org/vuln/euvd-2026-328691 EUVD-2026-328691 https://cve.radiocsirt.org/vuln/euvd-2026-328691 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46026 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: qrtr: ns: Limit the maximum number of lookups</p> <p>Current code does no bound checking on the number of lookups a client can perform. Though the code restricts the lookups to local clients, there is still a possibility of a malicious local client sending a flood of NEW_LOOKUP messages over the same socket.</p> <p>Fix this issue by limiting the maximum number of lookups to 64 globally. Since the nameserver allows only atmost one local observer, this global lookup count will ensure that the lookups stay within the limit.</p> <p>Note that, limit of 64 is chosen based on the current platform requirements. If requirement changes in the future, this limit can be increased.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: qrtr: ns: Limit the maximum number of lookups</p> <p>Current code does no bound checking on the number of lookups a client can perform. Though the code restricts the lookups to local clients, there is still a possibility of a malicious local client sending a flood of NEW_LOOKUP messages over the same socket.</p> <p>Fix this issue by limiting the maximum number of lookups to 64 globally. Since the nameserver allows only atmost one local observer, this global lookup count will ensure that the lookups stay within the limit.</p> <p>Note that, limit of 64 is chosen based on the current platform requirements. If requirement changes in the future, this limit can be increased.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46026 https://cve.radiocsirt.org/vuln/ghsa-5wpx-pvcm-rf34 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: qrtr: ns: Limit the maximum number of lookups</p> <p>Current code does no bound checking on the number of lookups a client can perform. Though the code restricts the lookups to local clients, there is still a possibility of a malicious local client sending a flood of NEW_LOOKUP messages over the same socket.</p> <p>Fix this issue by limiting the maximum number of lookups to 64 globally. Since the nameserver allows only atmost one local observer, this global lookup count will ensure that the lookups stay within the limit.</p> <p>Note that, limit of 64 is chosen based on the current platform requirements. If requirement changes in the future, this limit can be increased.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: qrtr: ns: Limit the maximum number of lookups</p> <p>Current code does no bound checking on the number of lookups a client can perform. Though the code restricts the lookups to local clients, there is still a possibility of a malicious local client sending a flood of NEW_LOOKUP messages over the same socket.</p> <p>Fix this issue by limiting the maximum number of lookups to 64 globally. Since the nameserver allows only atmost one local observer, this global lookup count will ensure that the lookups stay within the limit.</p> <p>Note that, limit of 64 is chosen based on the current platform requirements. If requirement changes in the future, this limit can be increased.</p> https://cve.radiocsirt.org/vuln/ghsa-5wpx-pvcm-rf34 https://cve.radiocsirt.org/vuln/msrc_cve-2026-46026 msrc_CVE-2026-46026 https://cve.radiocsirt.org/vuln/msrc_cve-2026-46026 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 <p>kernel-devel-7.0.11-1.1 on GA media</p> <p>kernel-devel-7.0.11-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 https://cve.radiocsirt.org/vuln/suse-su-2026:23066-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:23066-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46026 <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 192 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: qrtr: ns: Limit the maximum number of lookups Current code does no bound checking on the number of lookups a client can perform. Though the code restricts the lookups to local clients, there is still a possibility of a malicious local client sending a flood of NEW_LOOKUP messages over the same socket. Fix this issue by limiting the maximum number of lookups to 64 globally. Since the nameserver allows only atmost one local observer, this global lookup count will ensure that the lookups stay within the limit. Note that, limit of 64 is chosen based on the current platform requirements. If requirement changes in the future, this limit can be increased.</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 192 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: qrtr: ns: Limit the maximum number of lookups Current code does no bound checking on the number of lookups a client can perform. Though the code restricts the lookups to local clients, there is still a possibility of a malicious local client sending a flood of NEW_LOOKUP messages over the same socket. Fix this issue by limiting the maximum number of lookups to 64 globally. Since the nameserver allows only atmost one local observer, this global lookup count will ensure that the lookups stay within the limit. Note that, limit of 64 is chosen based on the current platform requirements. If requirement changes in the future, this limit can be increased.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46026 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700