---
title: "CVE-2026-89489: Linux Kernel - Broken Access Control"
description: "Linux kernel openrisc ABI < 244 contains an arbitrary kernel memory access vulnerability caused by unchecked user pointers in sys_or1k_atomic syscall, letting unprivileged attackers read/write kernel memory and execute code, exploit requires unprivileged process."
url: https://panop.io/threat-heartbeat/CVE-2026-89489/
---

# CVE-2026-89489 Linux Kernel - Broken Access Control

Linux kernel openrisc ABI < 244 contains an arbitrary kernel memory access vulnerability caused by unchecked user pointers in sys\_or1k\_atomic syscall, letting unprivileged attackers read/write kernel memory and execute code, exploit requires unprivileged process.

CVSS base score 7.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.14% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-89489)

## Details

Type

Broken Access Control

Impact

Remote Code Execution, Data Tampering, Information Disclosure

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Published

11 September 2026

Updated

15 October 2026

## Vendor fix

Update to a Linux kernel version with the sys\_or1k\_atomic pointer validation fix.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-89489](https://nvd.nist.gov/vuln/detail/CVE-2026-89489)
- [https://git.kernel.org/stable/c/574ae2ac2b314aa33498cd2c28add106cbe644f2](https://git.kernel.org/stable/c/574ae2ac2b314aa33498cd2c28add106cbe644f2)
- [https://git.kernel.org/stable/c/bf310718c6fa6adeee06d207a55489546d860e2c](https://git.kernel.org/stable/c/bf310718c6fa6adeee06d207a55489546d860e2c)
- [https://git.kernel.org/stable/c/78004e9a87f240df03e2f73120d291763c32e0a7](https://git.kernel.org/stable/c/78004e9a87f240df03e2f73120d291763c32e0a7)
- [https://git.kernel.org/stable/c/a520e8cac54fb403f3800125b606f55fcad42cb9](https://git.kernel.org/stable/c/a520e8cac54fb403f3800125b606f55fcad42cb9)
- [https://git.kernel.org/stable/c/b53435c079c78f89f70a62dd5a322cca4e292b34](https://git.kernel.org/stable/c/b53435c079c78f89f70a62dd5a322cca4e292b34)
- [https://git.kernel.org/stable/c/d64a75369cd0f2ee79afcc9d9ca34a3890989379](https://git.kernel.org/stable/c/d64a75369cd0f2ee79afcc9d9ca34a3890989379)
- [https://git.kernel.org/stable/c/1f2e92e499d863f81df1732af59b4a3559969193](https://git.kernel.org/stable/c/1f2e92e499d863f81df1732af59b4a3559969193)
- [https://git.kernel.org/stable/c/497cba0b02e5555d99fe9ee1dc478af743ab7f7a](https://git.kernel.org/stable/c/497cba0b02e5555d99fe9ee1dc478af743ab7f7a)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
