https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 06:12:52 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-46281 <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-2026-46281 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/euvd-2026-327196 EUVD-2026-327196 https://cve.radiocsirt.org/vuln/euvd-2026-327196 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46281 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>vmalloc: fix buffer overflow in vrealloc_node_align()</p> <p>Commit 4c5d3365882d (&#34;mm/vmalloc: allow to set node and align in vrealloc&#34;) added the ability to force a new allocation if the current pointer is on the wrong NUMA node, or if an alignment constraint is not met, even if the user is shrinking the allocation.</p> <p>On this path (need_realloc), the code allocates a new object of &#39;size&#39; bytes and then memcpy()s &#39;old_size&#39; bytes into it. If the request is to shrink the object (size &lt; old_size), this results in an out-of-bounds write on the new buffer.</p> <p>Fix this by bounding the copy length by the new allocation size.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>vmalloc: fix buffer overflow in vrealloc_node_align()</p> <p>Commit 4c5d3365882d (&#34;mm/vmalloc: allow to set node and align in vrealloc&#34;) added the ability to force a new allocation if the current pointer is on the wrong NUMA node, or if an alignment constraint is not met, even if the user is shrinking the allocation.</p> <p>On this path (need_realloc), the code allocates a new object of &#39;size&#39; bytes and then memcpy()s &#39;old_size&#39; bytes into it. If the request is to shrink the object (size &lt; old_size), this results in an out-of-bounds write on the new buffer.</p> <p>Fix this by bounding the copy length by the new allocation size.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46281 https://cve.radiocsirt.org/vuln/ghsa-xwpx-34xj-4qmq <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>vmalloc: fix buffer overflow in vrealloc_node_align()</p> <p>Commit 4c5d3365882d (&#34;mm/vmalloc: allow to set node and align in vrealloc&#34;) added the ability to force a new allocation if the current pointer is on the wrong NUMA node, or if an alignment constraint is not met, even if the user is shrinking the allocation.</p> <p>On this path (need_realloc), the code allocates a new object of &#39;size&#39; bytes and then memcpy()s &#39;old_size&#39; bytes into it. If the request is to shrink the object (size &lt; old_size), this results in an out-of-bounds write on the new buffer.</p> <p>Fix this by bounding the copy length by the new allocation size.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>vmalloc: fix buffer overflow in vrealloc_node_align()</p> <p>Commit 4c5d3365882d (&#34;mm/vmalloc: allow to set node and align in vrealloc&#34;) added the ability to force a new allocation if the current pointer is on the wrong NUMA node, or if an alignment constraint is not met, even if the user is shrinking the allocation.</p> <p>On this path (need_realloc), the code allocates a new object of &#39;size&#39; bytes and then memcpy()s &#39;old_size&#39; bytes into it. If the request is to shrink the object (size &lt; old_size), this results in an out-of-bounds write on the new buffer.</p> <p>Fix this by bounding the copy length by the new allocation size.</p> https://cve.radiocsirt.org/vuln/ghsa-xwpx-34xj-4qmq https://cve.radiocsirt.org/vuln/opensuse-su-2026:11014-1 <p>kernel-devel-7.0.12-1.1 on GA media</p> <p>kernel-devel-7.0.12-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11014-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46281 <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 98 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: vmalloc: fix buffer overflow in vrealloc_node_align() Commit 4c5d3365882d (&#34;mm/vmalloc: allow to set node and align in vrealloc&#34;) added the ability to force a new allocation if the current pointer is on the wrong NUMA node, or if an alignment constraint is not met, even if the user is shrinking the allocation. On this path (need_realloc), the code allocates a new object of &#39;size&#39; bytes and then memcpy()s &#39;old_size&#39; bytes into it. If the request is to shrink the object (size &lt; old_size), this results in an out-of-bounds write on the new buffer. Fix this by bounding the copy length by the new allocation size.</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 98 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: vmalloc: fix buffer overflow in vrealloc_node_align() Commit 4c5d3365882d (&#34;mm/vmalloc: allow to set node and align in vrealloc&#34;) added the ability to force a new allocation if the current pointer is on the wrong NUMA node, or if an alignment constraint is not met, even if the user is shrinking the allocation. On this path (need_realloc), the code allocates a new object of &#39;size&#39; bytes and then memcpy()s &#39;old_size&#39; bytes into it. If the request is to shrink the object (size &lt; old_size), this results in an out-of-bounds write on the new buffer. Fix this by bounding the copy length by the new allocation size.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46281 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1827 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1827