https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 16:51:42 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2017-17426 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2017-17426 https://cve.radiocsirt.org/vuln/cnvd-2018-00256 cnvd-2018-00256 https://cve.radiocsirt.org/vuln/cnvd-2018-00256 https://cve.radiocsirt.org/vuln/euvd-2026-164152 EUVD-2026-164152 https://cve.radiocsirt.org/vuln/euvd-2026-164152 https://cve.radiocsirt.org/vuln/fkie_cve-2017-17426 <p>The malloc function in the GNU C Library (aka glibc or libc6) 2.26 could return a memory block that is too small if an attempt is made to allocate an object whose size is close to SIZE_MAX, potentially leading to a subsequent heap overflow. This occurs because the per-thread cache (aka tcache) feature enables a code path that lacks an integer overflow check.</p> <p>The malloc function in the GNU C Library (aka glibc or libc6) 2.26 could return a memory block that is too small if an attempt is made to allocate an object whose size is close to SIZE_MAX, potentially leading to a subsequent heap overflow. This occurs because the per-thread cache (aka tcache) feature enables a code path that lacks an integer overflow check.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-17426 https://cve.radiocsirt.org/vuln/ghsa-5rxv-m65f-6q4g <p>The malloc function in the GNU C Library (aka glibc or libc6) 2.26 could return a memory block that is too small if an attempt is made to allocate an object whose size is close to SIZE_MAX, potentially leading to a subsequent heap overflow. This occurs because the per-thread cache (aka tcache) feature enables a code path that lacks an integer overflow check.</p> <p>The malloc function in the GNU C Library (aka glibc or libc6) 2.26 could return a memory block that is too small if an attempt is made to allocate an object whose size is close to SIZE_MAX, potentially leading to a subsequent heap overflow. This occurs because the per-thread cache (aka tcache) feature enables a code path that lacks an integer overflow check.</p> https://cve.radiocsirt.org/vuln/ghsa-5rxv-m65f-6q4g https://cve.radiocsirt.org/vuln/gsd-2017-17426 gsd-2017-17426 https://cve.radiocsirt.org/vuln/gsd-2017-17426 https://cve.radiocsirt.org/vuln/opensuse-su-2024:10792-1 <p>glibc-2.34-1.2 on GA media</p> <p>glibc-2.34-1.2 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:10792-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-17426 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:18.04:LTS: glibc</p> <p>The malloc function in the GNU C Library (aka glibc or libc6) 2.26 could return a memory block that is too small if an attempt is made to allocate an object whose size is close to SIZE_MAX, potentially leading to a subsequent heap overflow. This occurs because the per-thread cache (aka tcache) feature enables a code path that lacks an integer overflow check.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:18.04:LTS: glibc</p> <p>The malloc function in the GNU C Library (aka glibc or libc6) 2.26 could return a memory block that is too small if an attempt is made to allocate an object whose size is close to SIZE_MAX, potentially leading to a subsequent heap overflow. This occurs because the per-thread cache (aka tcache) feature enables a code path that lacks an integer overflow check.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-17426