openrisc: fix arbitrary kernel memory access via or1k_atomic syscall
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9d02a4283e9ce4e9ca11ff00615bdacdb0515a1a · < d64a75369cd0f2ee79afcc9d9ca34a3890989379| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
openrisc: fix arbitrary kernel memory access via or1k_atomic syscall
sys_or1k_atomic() (syscall 244 in the "or1k" ABI) takes two user pointers, v1 and v2, and swaps the words they point to in hand-written assembly.
l.lwz r29,0(r4) l.lwz r27,0(r5) l.sw 0(r4),r27 l.sw 0(r5),r29
The pointers are not checked with access_ok(). The four memory accesses also have no exception table entries.
A caller passes a kernel address as either pointer, and the syscall reads from and writes to it directly.
This gives an unprivileged process a kernel read/write primitive. It overwrites kernel data such as the sys_call_table, gaining code execution in kernel context.
Check both pointers before entering the critical section. Add fixups for the four memory accesses so faults on valid but unmapped user addresses return -EFAULT.
From the CVE record · Linux
The OpenRISC or1k_atomic syscall does not validate its user pointers before accessing memory. A local unprivileged process can pass a kernel address to read and write kernel memory, potentially gaining code execution in kernel context; no user interaction is needed.
Engineers running the Linux kernel on OpenRISC systems should check their kernel version against the vendor advisory; affected versions were not provided.