CVE-2026-80560

openrisc: signal: do not restore privileged SR bits on sigreturn

HIGH
7.8
CVSS Score
Published: August 26, 2026 at 02:37 PM UTC
Updated: August 27, 2026 at 06:30 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.2%

Description

In the Linux kernel, the following vulnerability has been resolved: openrisc: signal: do not restore privileged SR bits on sigreturn restore_sigcontext() copies the whole supervision register (SR) from the signal frame and only clears SPR_SR_SM before the value is reloaded into the hardware SR (through ESR and l.rfe) on the return to user space. All other SR bits are left under user control. An unprivileged task can thus return from a signal handler through a crafted sigframe that clears SPR_SR_DME. With the data MMU disabled the CPU performs no translation or protection on data accesses, so the task gains read and write access to arbitrary physical memory, a local privilege escalation. SPR_SR_IME, SPR_SR_SUMRA, SPR_SR_LEE, SPR_SR_EPH and the cache-enable bits are exposed the same way. The ptrace GPR regset already refuses any change to SR for exactly this reason. Restore only the arithmetic flag bits (F, CY, OV) from the signal frame and take every privileged control bit from the SR the kernel saved on signal entry. Verified with qemu-system-or1k -M or1k-sim: before this change an unprivileged PoC clears SPR_SR_DME in rt_sigreturn and writes a marker to physical address 0x03000000 (beyond the kernel's mem=32M); afterwards the same PoC receives SIGSEGV and physical memory is unchanged.

Affected

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

3.1 ≤ v < 5.10.2663.1 ≤ v < 5.15.2173.1 ≤ v < 6.1.1843.1 ≤ v < 6.12.1053.1 ≤ v < 6.18.463.1 ≤ v < 6.6.1533.1 ≤ v < 7.1.103.1 ≤ v < 7.23.1ac689eb7f9d4e270d1365853b82eece669387e2c
Vendor states this is fixed in 212fc482ddd7f9ccdd74a05eab1cac849350dcd6 (fixed)
Vendor states this is fixed in 32ef1b30ad736519f7a207bcc2986f3d4129d972 (fixed)
Vendor states this is fixed in 89a91b30685c0493b0fa2b47d0ab41061a63069d (fixed)
Vendor states this is fixed in a88d688be8d7f03cbf927f2ab454ea9fa58d2979 (fixed)
Vendor states this is fixed in b4d73c3848bae9084fa8b9b2aa76d99a7d8eb17d (fixed)
Vendor states this is fixed in bc2e24ba6e167ccf374a197457aa5640a802f429 (fixed)
Vendor states this is fixed in cd8b43a71755c516f5c1f265a103438ae9ab15be (fixed)
Vendor states this is fixed in cf1b5514ddf9df098ce7e3741fc9679fd85a4ec6 (fixed)
Vendor states this is fixed in 3.1 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (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