CVE-2026-89489

openrisc: fix arbitrary kernel memory access via or1k_atomic syscall

HIGH
7.8
CVSS Score
Published: September 11, 2026 at 07:43 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

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. [[email protected]: fix comment style]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.19d02a4283e9ce4e9ca11ff00615bdacdb0515a1a
Vendor states this is fixed in 1f2e92e499d863f81df1732af59b4a3559969193 (fixed)
Vendor states this is fixed in 497cba0b02e5555d99fe9ee1dc478af743ab7f7a (fixed)
Vendor states this is fixed in 574ae2ac2b314aa33498cd2c28add106cbe644f2 (fixed)
Vendor states this is fixed in 78004e9a87f240df03e2f73120d291763c32e0a7 (fixed)
Vendor states this is fixed in a520e8cac54fb403f3800125b606f55fcad42cb9 (fixed)
Vendor states this is fixed in b53435c079c78f89f70a62dd5a322cca4e292b34 (fixed)
Vendor states this is fixed in bf310718c6fa6adeee06d207a55489546d860e2c (fixed)
Vendor states this is fixed in d64a75369cd0f2ee79afcc9d9ca34a3890989379 (fixed)
Vendor states this is fixed in 3.1 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card