CVE-2026-80560: openrisc: signal: do not restore privileged SR bits on sigreturn
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 212fc482ddd7f9ccdd74a05eab1cac849350dcd6, 32ef1b30ad736519f7a207bcc2986f3d4129d972, 89a91b30685c0493b0fa2b47d0ab41061a63069d; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 212fc482ddd7f9ccdd74a05eab1cac849350dcd6, 32ef1b30ad736519f7a207bcc2986f3d4129d972, 89a91b30685c0493b0fa2b47d0ab41061a63069d; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.1affected
- ac689eb7f9d4e270d1365853b82eece669387e2c and later · before bc2e24ba6e167ccf374a197457aa5640a802f429affected · git
- ac689eb7f9d4e270d1365853b82eece669387e2c and later · before cf1b5514ddf9df098ce7e3741fc9679fd85a4ec6affected · git
- ac689eb7f9d4e270d1365853b82eece669387e2c and later · before cd8b43a71755c516f5c1f265a103438ae9ab15beaffected · git
- ac689eb7f9d4e270d1365853b82eece669387e2c and later · before b4d73c3848bae9084fa8b9b2aa76d99a7d8eb17daffected · git
- ac689eb7f9d4e270d1365853b82eece669387e2c and later · before 89a91b30685c0493b0fa2b47d0ab41061a63069daffected · git
- ac689eb7f9d4e270d1365853b82eece669387e2c and later · before a88d688be8d7f03cbf927f2ab454ea9fa58d2979affected · git
- ac689eb7f9d4e270d1365853b82eece669387e2c and later · before 212fc482ddd7f9ccdd74a05eab1cac849350dcd6affected · git
- ac689eb7f9d4e270d1365853b82eece669387e2c and later · before 32ef1b30ad736519f7a207bcc2986f3d4129d972affected · git
- before 3.1not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.10-1 | 7.1.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80556Aug 26, 2026 · mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition31Monitor
- ← EarlierCVE-2026-80559Aug 26, 2026 · Input: sur40 - fix input device registration ordering31Monitor
- Later →CVE-2026-80562Aug 26, 2026 · gpio: ml-ioh: use raw_spinlock_t for the register lock0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 212fc482ddd7f9ccdd74a05eab1cac849350dcd6 | Vendor (CNA) |
| Linux Linux | 32ef1b30ad736519f7a207bcc2986f3d4129d972 | Vendor (CNA) |
| Linux Linux | 89a91b30685c0493b0fa2b47d0ab41061a63069d | Vendor (CNA) |
| Linux Linux | a88d688be8d7f03cbf927f2ab454ea9fa58d2979 | Vendor (CNA) |
| Linux Linux | b4d73c3848bae9084fa8b9b2aa76d99a7d8eb17d | Vendor (CNA) |
| Linux Linux | bc2e24ba6e167ccf374a197457aa5640a802f429 | Vendor (CNA) |
| Linux Linux | cd8b43a71755c516f5c1f265a103438ae9ab15be | Vendor (CNA) |
| Linux Linux | cf1b5514ddf9df098ce7e3741fc9679fd85a4ec6 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0919 · Aug 27, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/32ef1b30ad736519f7a207bcc2986f3d4129d972
- git.kernel.org/stable/c/89a91b30685c0493b0fa2b47d0ab41061a63069d
- git.kernel.org/stable/c/a88d688be8d7f03cbf927f2ab454ea9fa58d2979
- git.kernel.org/stable/c/b4d73c3848bae9084fa8b9b2aa76d99a7d8eb17d
- git.kernel.org/stable/c/bc2e24ba6e167ccf374a197457aa5640a802f429
- git.kernel.org/stable/c/cd8b43a71755c516f5c1f265a103438ae9ab15be
- git.kernel.org/stable/c/cf1b5514ddf9df098ce7e3741fc9679fd85a4ec6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.