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:31:37 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-64180 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-64180 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/euvd-2026-338792 EUVD-2026-338792 https://cve.radiocsirt.org/vuln/euvd-2026-338792 https://cve.radiocsirt.org/vuln/fkie_cve-2026-64180 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/memory_hotplug: fix memory block reference leak on remove</p> <p>Patch series &#34;mm: Fix memory block leaks and locking&#34;, v2.</p> <p>This series fixes two memory block device reference leaks and one locking issue around the per-memory_block hwpoison counter.</p> <p>This patch (of 2):</p> <p>remove_memory_blocks_and_altmaps() looks up each memory block with find_memory_block(), which acquires a reference to the memory block device.</p> <p>That reference is never dropped on this path, resulting in a leaked device reference when removing memory blocks and their altmaps. Drop the reference after retrieving mem-&gt;altmap and clearing mem-&gt;altmap, before removing the memory block device.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/memory_hotplug: fix memory block reference leak on remove</p> <p>Patch series &#34;mm: Fix memory block leaks and locking&#34;, v2.</p> <p>This series fixes two memory block device reference leaks and one locking issue around the per-memory_block hwpoison counter.</p> <p>This patch (of 2):</p> <p>remove_memory_blocks_and_altmaps() looks up each memory block with find_memory_block(), which acquires a reference to the memory block device.</p> <p>That reference is never dropped on this path, resulting in a leaked device reference when removing memory blocks and their altmaps. Drop the reference after retrieving mem-&gt;altmap and clearing mem-&gt;altmap, before removing the memory block device.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-64180 https://cve.radiocsirt.org/vuln/ghsa-8rwj-765p-2628 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/memory_hotplug: fix memory block reference leak on remove</p> <p>Patch series &#34;mm: Fix memory block leaks and locking&#34;, v2.</p> <p>This series fixes two memory block device reference leaks and one locking issue around the per-memory_block hwpoison counter.</p> <p>This patch (of 2):</p> <p>remove_memory_blocks_and_altmaps() looks up each memory block with find_memory_block(), which acquires a reference to the memory block device.</p> <p>That reference is never dropped on this path, resulting in a leaked device reference when removing memory blocks and their altmaps. Drop the reference after retrieving mem-&gt;altmap and clearing mem-&gt;altmap, before removing the memory block device.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/memory_hotplug: fix memory block reference leak on remove</p> <p>Patch series &#34;mm: Fix memory block leaks and locking&#34;, v2.</p> <p>This series fixes two memory block device reference leaks and one locking issue around the per-memory_block hwpoison counter.</p> <p>This patch (of 2):</p> <p>remove_memory_blocks_and_altmaps() looks up each memory block with find_memory_block(), which acquires a reference to the memory block device.</p> <p>That reference is never dropped on this path, resulting in a leaked device reference when removing memory blocks and their altmaps. Drop the reference after retrieving mem-&gt;altmap and clearing mem-&gt;altmap, before removing the memory block device.</p> https://cve.radiocsirt.org/vuln/ghsa-8rwj-765p-2628 https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-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:21910-1 https://cve.radiocsirt.org/vuln/suse-su-2026:23881-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:23881-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64180 <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 153 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/memory_hotplug: fix memory block reference leak on remove Patch series &#34;mm: Fix memory block leaks and locking&#34;, v2. This series fixes two memory block device reference leaks and one locking issue around the per-memory_block hwpoison counter. This patch (of 2): remove_memory_blocks_and_altmaps() looks up each memory block with find_memory_block(), which acquires a reference to the memory block device. That reference is never dropped on this path, resulting in a leaked device reference when removing memory blocks and their altmaps. Drop the reference after retrieving mem-&gt;altmap and clearing mem-&gt;altmap, before removing the memory block device.</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 153 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/memory_hotplug: fix memory block reference leak on remove Patch series &#34;mm: Fix memory block leaks and locking&#34;, v2. This series fixes two memory block device reference leaks and one locking issue around the per-memory_block hwpoison counter. This patch (of 2): remove_memory_blocks_and_altmaps() looks up each memory block with find_memory_block(), which acquires a reference to the memory block device. That reference is never dropped on this path, resulting in a leaked device reference when removing memory blocks and their altmaps. Drop the reference after retrieving mem-&gt;altmap and clearing mem-&gt;altmap, before removing the memory block device.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64180 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403