https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 01:43:18 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-03560 bdu:2026-03560 https://cve.radiocsirt.org/vuln/bdu:2026-03560 https://cve.radiocsirt.org/vuln/bell-cve-2026-23262 <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-23262 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0497 certfr-2026-avi-0497 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0497 https://cve.radiocsirt.org/vuln/euvd-2026-315436 EUVD-2026-315436 https://cve.radiocsirt.org/vuln/euvd-2026-315436 https://cve.radiocsirt.org/vuln/fkie_cve-2026-23262 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gve: Fix stats report corruption on queue count change</p> <p>The driver and the NIC share a region in memory for stats reporting. The NIC calculates its offset into this region based on the total size of the stats region and the size of the NIC&#39;s stats.</p> <p>When the number of queues is changed, the driver&#39;s stats region is resized. If the queue count is increased, the NIC can write past the end of the allocated stats region, causing memory corruption. If the queue count is decreased, there is a gap between the driver and NIC stats, leading to incorrect stats reporting.</p> <p>This change fixes the issue by allocating stats region with maximum size, and the offset calculation for NIC stats is changed to match with the calculation of the NIC.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gve: Fix stats report corruption on queue count change</p> <p>The driver and the NIC share a region in memory for stats reporting. The NIC calculates its offset into this region based on the total size of the stats region and the size of the NIC&#39;s stats.</p> <p>When the number of queues is changed, the driver&#39;s stats region is resized. If the queue count is increased, the NIC can write past the end of the allocated stats region, causing memory corruption. If the queue count is decreased, there is a gap between the driver and NIC stats, leading to incorrect stats reporting.</p> <p>This change fixes the issue by allocating stats region with maximum size, and the offset calculation for NIC stats is changed to match with the calculation of the NIC.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-23262 https://cve.radiocsirt.org/vuln/ghsa-2rm5-c5x9-v5x4 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gve: Fix stats report corruption on queue count change</p> <p>The driver and the NIC share a region in memory for stats reporting. The NIC calculates its offset into this region based on the total size of the stats region and the size of the NIC&#39;s stats.</p> <p>When the number of queues is changed, the driver&#39;s stats region is resized. If the queue count is increased, the NIC can write past the end of the allocated stats region, causing memory corruption. If the queue count is decreased, there is a gap between the driver and NIC stats, leading to incorrect stats reporting.</p> <p>This change fixes the issue by allocating stats region with maximum size, and the offset calculation for NIC stats is changed to match with the calculation of the NIC.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gve: Fix stats report corruption on queue count change</p> <p>The driver and the NIC share a region in memory for stats reporting. The NIC calculates its offset into this region based on the total size of the stats region and the size of the NIC&#39;s stats.</p> <p>When the number of queues is changed, the driver&#39;s stats region is resized. If the queue count is increased, the NIC can write past the end of the allocated stats region, causing memory corruption. If the queue count is decreased, there is a gap between the driver and NIC stats, leading to incorrect stats reporting.</p> <p>This change fixes the issue by allocating stats region with maximum size, and the offset calculation for NIC stats is changed to match with the calculation of the NIC.</p> https://cve.radiocsirt.org/vuln/ghsa-2rm5-c5x9-v5x4 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20572-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:20572-1 https://cve.radiocsirt.org/vuln/suse-su-2026:1668-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:1668-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23262 <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:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-gke-4.15 and 182 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: gve: Fix stats report corruption on queue count change The driver and the NIC share a region in memory for stats reporting. The NIC calculates its offset into this region based on the total size of the stats region and the size of the NIC&#39;s stats. When the number of queues is changed, the driver&#39;s stats region is resized. If the queue count is increased, the NIC can write past the end of the allocated stats region, causing memory corruption. If the queue count is decreased, there is a gap between the driver and NIC stats, leading to incorrect stats reporting. This change fixes the issue by allocating stats region with maximum size, and the offset calculation for NIC stats is changed to match with the calculation of the NIC.</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:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-gke-4.15 and 182 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: gve: Fix stats report corruption on queue count change The driver and the NIC share a region in memory for stats reporting. The NIC calculates its offset into this region based on the total size of the stats region and the size of the NIC&#39;s stats. When the number of queues is changed, the driver&#39;s stats region is resized. If the queue count is increased, the NIC can write past the end of the allocated stats region, causing memory corruption. If the queue count is decreased, there is a gap between the driver and NIC stats, leading to incorrect stats reporting. This change fixes the issue by allocating stats region with maximum size, and the offset calculation for NIC stats is changed to match with the calculation of the NIC.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23262 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0790 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einem Denial-of-Service-Zustand, einer Rechteausweitung oder einer Speicherbeschädigung führen können.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einem Denial-of-Service-Zustand, einer Rechteausweitung oder einer Speicherbeschädigung führen können.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0790