tracing/syscalls: Use copy_from_user for the faultable syscall buffer
Historical advisory recorded 2 Nov 2026 17:57:17 UTC. Read the latest advisory.
cve-program · CVE-2026-99232
PublishedIn 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.
Read the publisher's advisoryAffected versions, risk and source history
cve-program · CVE-2026-99232
Publishedtracing/syscalls: Use copy_from_user for the faultable syscall buffer
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.
- Source published
- 2 Nov 2026 16:06:39 UTC
- Source modified
- 2 Nov 2026 16:06:39 UTC
- Saved here
- 2 Nov 2026 17:57:17 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.