Live › vulnerability › CVE-2026-99232
The Linux kernel's syscall tracing code copied syscall buffer arguments with a routine that skips the access check that rejects non-user addresses. The fix switches to the checked copy routine so invalid addresses are rejected and recorded as faulted.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 16:24 UTC. All times on this page are UTC.
The sources describe the flaw only as a concern for machines that trust perf too much; they do not say which kernel versions are affected or what configuration exposes it. Teams running Linux servers should check their kernel version against their vendor's advisory. unknown
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99232")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.