https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 01:10:42 +0000 https://cve.radiocsirt.org/vuln/bdu:2015-04356 bdu:2015-04356 https://cve.radiocsirt.org/vuln/bdu:2015-04356 https://cve.radiocsirt.org/vuln/euvd-2026-121926 EUVD-2026-121926 https://cve.radiocsirt.org/vuln/euvd-2026-121926 https://cve.radiocsirt.org/vuln/fkie_cve-2009-0835 <p>The __secure_computing function in kernel/seccomp.c in the seccomp subsystem in the Linux kernel 2.6.28.7 and earlier on the x86_64 platform, when CONFIG_SECCOMP is enabled, does not properly handle (1) a 32-bit process making a 64-bit syscall or (2) a 64-bit process making a 32-bit syscall, which allows local users to bypass intended access restrictions via crafted syscalls that are misinterpreted as (a) stat or (b) chmod, a related issue to CVE-2009-0342 and CVE-2009-0343.</p> <p>The __secure_computing function in kernel/seccomp.c in the seccomp subsystem in the Linux kernel 2.6.28.7 and earlier on the x86_64 platform, when CONFIG_SECCOMP is enabled, does not properly handle (1) a 32-bit process making a 64-bit syscall or (2) a 64-bit process making a 32-bit syscall, which allows local users to bypass intended access restrictions via crafted syscalls that are misinterpreted as (a) stat or (b) chmod, a related issue to CVE-2009-0342 and CVE-2009-0343.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2009-0835 https://cve.radiocsirt.org/vuln/ghsa-x75x-89gj-wfcm <p>The __secure_computing function in kernel/seccomp.c in the seccomp subsystem in the Linux kernel 2.6.28.7 and earlier on the x86_64 platform, when CONFIG_SECCOMP is enabled, does not properly handle (1) a 32-bit process making a 64-bit syscall or (2) a 64-bit process making a 32-bit syscall, which allows local users to bypass intended access restrictions via crafted syscalls that are misinterpreted as (a) stat or (b) chmod, a related issue to CVE-2009-0342 and CVE-2009-0343.</p> <p>The __secure_computing function in kernel/seccomp.c in the seccomp subsystem in the Linux kernel 2.6.28.7 and earlier on the x86_64 platform, when CONFIG_SECCOMP is enabled, does not properly handle (1) a 32-bit process making a 64-bit syscall or (2) a 64-bit process making a 32-bit syscall, which allows local users to bypass intended access restrictions via crafted syscalls that are misinterpreted as (a) stat or (b) chmod, a related issue to CVE-2009-0342 and CVE-2009-0343.</p> https://cve.radiocsirt.org/vuln/ghsa-x75x-89gj-wfcm https://cve.radiocsirt.org/vuln/gsd-2009-0835 gsd-2009-0835 https://cve.radiocsirt.org/vuln/gsd-2009-0835 https://cve.radiocsirt.org/vuln/rhsa-2009:0451 <p>Kernel BUG() in locks_remove_flock Linux kernel minor signal handling vulnerability kernel: x86-64: syscall-audit: 32/64 syscall hole kernel: x86-64: seccomp: 32/64 syscall hole kernel: utf8 selection memory corruption kernel: exit_notify: kill the wrong capable(CAP_KILL) check</p> <p>Kernel BUG() in locks_remove_flock Linux kernel minor signal handling vulnerability kernel: x86-64: syscall-audit: 32/64 syscall hole kernel: x86-64: seccomp: 32/64 syscall hole kernel: utf8 selection memory corruption kernel: exit_notify: kill the wrong capable(CAP_KILL) check</p> https://cve.radiocsirt.org/vuln/rhsa-2009:0451