CVE-2026-80560

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (8)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

openrisc: signal: do not restore privileged SR bits on sigreturn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cf1b5514ddf9df098ce7e3741fc9679fd85a4ec6
generic

openrisc: signal: do not restore privileged SR bits on sigreturn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cd8b43a71755c516f5c1f265a103438ae9ab15be
generic

openrisc: signal: do not restore privileged SR bits on sigreturn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bc2e24ba6e167ccf374a197457aa5640a802f429
generic

openrisc: signal: do not restore privileged SR bits on sigreturn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b4d73c3848bae9084fa8b9b2aa76d99a7d8eb17d
generic

openrisc: signal: do not restore privileged SR bits on sigreturn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a88d688be8d7f03cbf927f2ab454ea9fa58d2979
generic

openrisc: signal: do not restore privileged SR bits on sigreturn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89a91b30685c0493b0fa2b47d0ab41061a63069d
generic

openrisc: signal: do not restore privileged SR bits on sigreturn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32ef1b30ad736519f7a207bcc2986f3d4129d972
generic

openrisc: signal: do not restore privileged SR bits on sigreturn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/212fc482ddd7f9ccdd74a05eab1cac849350dcd6

Vendor Advisories for CVE-2026-80560(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:39 UTCGHSA enrichment
  3. 2026-08-29 13:48 UTCGHSA enrichment
  4. 2026-08-29 02:56 UTCEG score recompute
  5. 2026-08-29 02:55 UTCGHSA enrichment
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-28 16:05 UTCGHSA enrichment
  8. 2026-08-28 04:55 UTCGHSA enrichment
  9. 2026-08-27 18:04 UTCEG score recompute
  10. 2026-08-27 18:04 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 06:19 UTCEG score recompute 7.80
  13. 2026-08-27 06:11 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-08-26 15:43 UTCNVD update
  15. 2026-08-26 14:42 UTCEG score recompute
  16. 2026-08-26 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80560?
CVE-2026-80560 is a high vulnerability published on August 26, 2026. 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 SPRSRSM before the value is reloaded into the hardware SR…
When was CVE-2026-80560 disclosed?
CVE-2026-80560 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80560 actively exploited?
CVE-2026-80560 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-80560?
CVE-2026-80560 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80560?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80560, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80560

Explore →

Is Your Infrastructure Affected by CVE-2026-80560?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.