https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:46:30 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509 certfr-2025-avi-0509 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509 https://cve.radiocsirt.org/vuln/euvd-2026-320333 EUVD-2026-320333 https://cve.radiocsirt.org/vuln/euvd-2026-320333 https://cve.radiocsirt.org/vuln/fkie_cve-2022-49889 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters()</p> <p>On some machines the number of listed CPUs may be bigger than the actual CPUs that exist. The tracing subsystem allocates a per_cpu directory with access to the per CPU ring buffer via a cpuX file. But to save space, the ring buffer will only allocate buffers for online CPUs, even though the CPU array will be as big as the nr_cpu_ids.</p> <p>With the addition of waking waiters on the ring buffer when closing the file, the ring_buffer_wake_waiters() now needs to make sure that the buffer is allocated (with the irq_work allocated with it) before trying to wake waiters, as it will cause a NULL pointer dereference.</p> <p>While debugging this, I added a NULL check for the buffer itself (which is OK to do), and also NULL pointer checks against buffer-&gt;buffers (which is not fine, and will WARN) as well as making sure the CPU number passed in is within the nr_cpu_ids (which is also not fine if it isn&#39;t).</p> <p>Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1204705</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters()</p> <p>On some machines the number of listed CPUs may be bigger than the actual CPUs that exist. The tracing subsystem allocates a per_cpu directory with access to the per CPU ring buffer via a cpuX file. But to save space, the ring buffer will only allocate buffers for online CPUs, even though the CPU array will be as big as the nr_cpu_ids.</p> <p>With the addition of waking waiters on the ring buffer when closing the file, the ring_buffer_wake_waiters() now needs to make sure that the buffer is allocated (with the irq_work allocated with it) before trying to wake waiters, as it will cause a NULL pointer dereference.</p> <p>While debugging this, I added a NULL check for the buffer itself (which is OK to do), and also NULL pointer checks against buffer-&gt;buffers (which is not fine, and will WARN) as well as making sure the CPU number passed in is within the nr_cpu_ids (which is also not fine if it isn&#39;t).</p> <p>Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1204705</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-49889 https://cve.radiocsirt.org/vuln/ghsa-w9wh-q8v9-3rwf <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters()</p> <p>On some machines the number of listed CPUs may be bigger than the actual CPUs that exist. The tracing subsystem allocates a per_cpu directory with access to the per CPU ring buffer via a cpuX file. But to save space, the ring buffer will only allocate buffers for online CPUs, even though the CPU array will be as big as the nr_cpu_ids.</p> <p>With the addition of waking waiters on the ring buffer when closing the file, the ring_buffer_wake_waiters() now needs to make sure that the buffer is allocated (with the irq_work allocated with it) before trying to wake waiters, as it will cause a NULL pointer dereference.</p> <p>While debugging this, I added a NULL check for the buffer itself (which is OK to do), and also NULL pointer checks against buffer-&gt;buffers (which is not fine, and will WARN) as well as making sure the CPU number passed in is within the nr_cpu_ids (which is also not fine if it isn&#39;t).</p> <p>Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1204705</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters()</p> <p>On some machines the number of listed CPUs may be bigger than the actual CPUs that exist. The tracing subsystem allocates a per_cpu directory with access to the per CPU ring buffer via a cpuX file. But to save space, the ring buffer will only allocate buffers for online CPUs, even though the CPU array will be as big as the nr_cpu_ids.</p> <p>With the addition of waking waiters on the ring buffer when closing the file, the ring_buffer_wake_waiters() now needs to make sure that the buffer is allocated (with the irq_work allocated with it) before trying to wake waiters, as it will cause a NULL pointer dereference.</p> <p>While debugging this, I added a NULL check for the buffer itself (which is OK to do), and also NULL pointer checks against buffer-&gt;buffers (which is not fine, and will WARN) as well as making sure the CPU number passed in is within the nr_cpu_ids (which is also not fine if it isn&#39;t).</p> <p>Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1204705</p> https://cve.radiocsirt.org/vuln/ghsa-w9wh-q8v9-3rwf https://cve.radiocsirt.org/vuln/suse-su-2025:01918-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:01918-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49889 <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 70 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters() On some machines the number of listed CPUs may be bigger than the actual CPUs that exist. The tracing subsystem allocates a per_cpu directory with access to the per CPU ring buffer via a cpuX file. But to save space, the ring buffer will only allocate buffers for online CPUs, even though the CPU array will be as big as the nr_cpu_ids. With the addition of waking waiters on the ring buffer when closing the file, the ring_buffer_wake_waiters() now needs to make sure that the buffer is allocated (with the irq_work allocated with it) before trying to wake waiters, as it will cause a NULL pointer dereference. While debugging this, I added a NULL check for the buffer itself (which is OK to do), and also NULL pointer checks against buffer-&gt;buffers (which is not fine, and will WARN) as well as making sure the CPU number passed in is within the nr_cpu_ids (which is also not fine if it isn&#39;t). Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1204705</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 70 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters() On some machines the number of listed CPUs may be bigger than the actual CPUs that exist. The tracing subsystem allocates a per_cpu directory with access to the per CPU ring buffer via a cpuX file. But to save space, the ring buffer will only allocate buffers for online CPUs, even though the CPU array will be as big as the nr_cpu_ids. With the addition of waking waiters on the ring buffer when closing the file, the ring_buffer_wake_waiters() now needs to make sure that the buffer is allocated (with the irq_work allocated with it) before trying to wake waiters, as it will cause a NULL pointer dereference. While debugging this, I added a NULL check for the buffer itself (which is OK to do), and also NULL pointer checks against buffer-&gt;buffers (which is not fine, and will WARN) as well as making sure the CPU number passed in is within the nr_cpu_ids (which is also not fine if it isn&#39;t). Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1204705</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49889