https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 18:54:33 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2008-1367 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2008-1367 https://cve.radiocsirt.org/vuln/certa-2008-avi-380 certa-2008-avi-380 https://cve.radiocsirt.org/vuln/certa-2008-avi-380 https://cve.radiocsirt.org/vuln/euvd-2026-126574 EUVD-2026-126574 https://cve.radiocsirt.org/vuln/euvd-2026-126574 https://cve.radiocsirt.org/vuln/fkie_cve-2008-1367 <p>gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can prevent the direction flag (DF) from being reset in violation of ABI conventions and cause data to be copied in the wrong direction during signal handling in the Linux kernel, which might allow context-dependent attackers to trigger memory corruption. NOTE: this issue was originally reported for CPU consumption in SBCL.</p> <p>gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can prevent the direction flag (DF) from being reset in violation of ABI conventions and cause data to be copied in the wrong direction during signal handling in the Linux kernel, which might allow context-dependent attackers to trigger memory corruption. NOTE: this issue was originally reported for CPU consumption in SBCL.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2008-1367 https://cve.radiocsirt.org/vuln/ghsa-mh8h-6q9x-8j58 <p>gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can prevent the direction flag (DF) from being reset in violation of ABI conventions and cause data to be copied in the wrong direction during signal handling in the Linux kernel, which might allow context-dependent attackers to trigger memory corruption. NOTE: this issue was originally reported for CPU consumption in SBCL.</p> <p>gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can prevent the direction flag (DF) from being reset in violation of ABI conventions and cause data to be copied in the wrong direction during signal handling in the Linux kernel, which might allow context-dependent attackers to trigger memory corruption. NOTE: this issue was originally reported for CPU consumption in SBCL.</p> https://cve.radiocsirt.org/vuln/ghsa-mh8h-6q9x-8j58 https://cve.radiocsirt.org/vuln/gsd-2008-1367 gsd-2008-1367 https://cve.radiocsirt.org/vuln/gsd-2008-1367 https://cve.radiocsirt.org/vuln/rhsa-2008:0211 <p>kernel Race condition in mincore can cause &#34;ps -ef&#34; to hang kernel asynchronous IO on a FIFO kernel panic I4L: fix isdn_ioctl memory issue Issue with core dump owner kernel: insufficient range checks in fault handlers with mremap Kernel doesn&#39;t clear DF for signal handlers kernel: race condition in dnotify (local DoS, local roothole possible) kernel: add rcu_read_lock() to fcheck() in both dnotify, locks.c and fix fcntl store/load race in locks.c</p> <p>kernel Race condition in mincore can cause &#34;ps -ef&#34; to hang kernel asynchronous IO on a FIFO kernel panic I4L: fix isdn_ioctl memory issue Issue with core dump owner kernel: insufficient range checks in fault handlers with mremap Kernel doesn&#39;t clear DF for signal handlers kernel: race condition in dnotify (local DoS, local roothole possible) kernel: add rcu_read_lock() to fcheck() in both dnotify, locks.c and fix fcntl store/load race in locks.c</p> https://cve.radiocsirt.org/vuln/rhsa-2008:0211