Linux kernel memory exposure in syscall tracing buffers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
7.2.147.3.17.4-rc1In 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.
From the CVE record · Linux
The Linux kernel’s syscall tracing code copies buffers for faultable syscalls without checking whether the address is a user address. A non-user address may therefore be accepted instead of being recorded as faulted. The description flags a potential security concern on machines that trust perf too much, but does not specify an attacker capability or authentication requirements.
Operators of Linux systems using kernel syscall tracing should check their kernel versions against the vendor advisory; affected versions are not specified.