https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:52:35 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-03342 bdu:2026-03342 https://cve.radiocsirt.org/vuln/bdu:2026-03342 https://cve.radiocsirt.org/vuln/bell-cve-2023-53484 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2023-53484 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1047 certfr-2025-avi-1047 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1047 https://cve.radiocsirt.org/vuln/euvd-2026-345219 EUVD-2026-345219 https://cve.radiocsirt.org/vuln/euvd-2026-345219 https://cve.radiocsirt.org/vuln/fkie_cve-2023-53484 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib: cpu_rmap: Avoid use after free on rmap-&gt;obj array entries</p> <p>When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free.</p> <p>Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap().</p> <p>The current code does not suffer from this since there are no cases where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the notify arg) is called, followed by a call to free_irq_cpu_rmap() so we don&#39;t hit and issue. Subsequent patches in this series excersize this flow, hence the required fix.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib: cpu_rmap: Avoid use after free on rmap-&gt;obj array entries</p> <p>When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free.</p> <p>Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap().</p> <p>The current code does not suffer from this since there are no cases where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the notify arg) is called, followed by a call to free_irq_cpu_rmap() so we don&#39;t hit and issue. Subsequent patches in this series excersize this flow, hence the required fix.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-53484 https://cve.radiocsirt.org/vuln/ghsa-9598-2w9x-r9v4 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib: cpu_rmap: Avoid use after free on rmap-&gt;obj array entries</p> <p>When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free.</p> <p>Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap().</p> <p>The current code does not suffer from this since there are no cases where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the notify arg) is called, followed by a call to free_irq_cpu_rmap() so we don&#39;t hit and issue. Subsequent patches in this series excersize this flow, hence the required fix.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib: cpu_rmap: Avoid use after free on rmap-&gt;obj array entries</p> <p>When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free.</p> <p>Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap().</p> <p>The current code does not suffer from this since there are no cases where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the notify arg) is called, followed by a call to free_irq_cpu_rmap() so we don&#39;t hit and issue. Subsequent patches in this series excersize this flow, hence the required fix.</p> https://cve.radiocsirt.org/vuln/ghsa-9598-2w9x-r9v4 https://cve.radiocsirt.org/vuln/suse-su-2025:4189-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:4189-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53484 <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 162 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: lib: cpu_rmap: Avoid use after free on rmap-&gt;obj array entries When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free. Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap(). The current code does not suffer from this since there are no cases where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the notify arg) is called, followed by a call to free_irq_cpu_rmap() so we don&#39;t hit and issue. Subsequent patches in this series excersize this flow, hence the required fix.</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 162 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: lib: cpu_rmap: Avoid use after free on rmap-&gt;obj array entries When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free. Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap(). The current code does not suffer from this since there are no cases where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the notify arg) is called, followed by a call to free_irq_cpu_rmap() so we don&#39;t hit and issue. Subsequent patches in this series excersize this flow, hence the required fix.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53484 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187