https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 04 Nov 2026 19:41:36 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-99232 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing/syscalls: Use copy_from_user for the faultable syscall buffer</p> <p>syscall_copy_user_array() copies the buffer argument of faultable syscalls (write, pwrite64, ...) with __copy_from_user(), which skips access_ok(). Use copy_from_user() instead so a non-user address is rejected and the entry is recorded as faulted.</p> <p>It could be a security concern for machines that trust perf a bit too much.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing/syscalls: Use copy_from_user for the faultable syscall buffer</p> <p>syscall_copy_user_array() copies the buffer argument of faultable syscalls (write, pwrite64, ...) with __copy_from_user(), which skips access_ok(). Use copy_from_user() instead so a non-user address is rejected and the entry is recorded as faulted.</p> <p>It could be a security concern for machines that trust perf a bit too much.</p> https://db.gcve.eu/vuln/fkie_cve-2026-99232 https://db.gcve.eu/vuln/ghsa-2w2h-c9pf-xxjf <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing/syscalls: Use copy_from_user for the faultable syscall buffer</p> <p>syscall_copy_user_array() copies the buffer argument of faultable syscalls (write, pwrite64, ...) with __copy_from_user(), which skips access_ok(). Use copy_from_user() instead so a non-user address is rejected and the entry is recorded as faulted.</p> <p>It could be a security concern for machines that trust perf a bit too much.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing/syscalls: Use copy_from_user for the faultable syscall buffer</p> <p>syscall_copy_user_array() copies the buffer argument of faultable syscalls (write, pwrite64, ...) with __copy_from_user(), which skips access_ok(). Use copy_from_user() instead so a non-user address is rejected and the entry is recorded as faulted.</p> <p>It could be a security concern for machines that trust perf a bit too much.</p> https://db.gcve.eu/vuln/ghsa-2w2h-c9pf-xxjf https://db.gcve.eu/vuln/ubuntu-cve-2026-99232 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 257 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: tracing/syscalls: Use copy_from_user for the faultable syscall buffer syscall_copy_user_array() copies the buffer argument of faultable syscalls (write, pwrite64, ...) with __copy_from_user(), which skips access_ok(). Use copy_from_user() instead so a non-user address is rejected and the entry is recorded as faulted. It could be a security concern for machines that trust perf a bit too much.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 257 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: tracing/syscalls: Use copy_from_user for the faultable syscall buffer syscall_copy_user_array() copies the buffer argument of faultable syscalls (write, pwrite64, ...) with __copy_from_user(), which skips access_ok(). Use copy_from_user() instead so a non-user address is rejected and the entry is recorded as faulted. It could be a security concern for machines that trust perf a bit too much.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-99232