Linux Kernel up to 7.1.9 Signal restore_sigcontext privileges management

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.4	$0-$5k	1.22-

Summaryinfo

A vulnerability categorized as very critical has been discovered in Linux Kernel up to 7.1.9. This issue affects the function restore_sigcontext of the component Signal. Executing a manipulation can lead to privileges management. This vulnerability is tracked as CVE-2026-80560. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1.9. It has been declared as very critical. This vulnerability affects the function restore_sigcontext of the component Signal. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-80560 since 08/26/2026. The exploitation appears to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/26/2026). The MITRE ATT&CK project declares the attack technique as T1068.

Upgrading to version 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46 or 7.1.10 eliminates this vulnerability. Applying the patch bc2e24ba6e167ccf374a197457aa5640a802f429/cf1b5514ddf9df098ce7e3741fc9679fd85a4ec6/cd8b43a71755c516f5c1f265a103438ae9ab15be/b4d73c3848bae9084fa8b9b2aa76d99a7d8eb17d/89a91b30685c0493b0fa2b47d0ab41061a63069d/a88d688be8d7f03cbf927f2ab454ea9fa58d2979/212fc482ddd7f9ccdd74a05eab1cac849350dcd6/32ef1b30ad736519f7a207bcc2986f3d4129d972 is able to eliminate this problem.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.10.265
• 5.15.216
• 6.1.183
• 6.6.152
• 6.12.104
• 6.18.0
• 6.18.1
• 6.18.2
• 6.18.3
• 6.18.4
• 6.18.5
• 6.18.6
• 6.18.7
• 6.18.8
• 6.18.9
• 6.18.10
• 6.18.11
• 6.18.12
• 6.18.13
• 6.18.14
• 6.18.15
• 6.18.16
• 6.18.17
• 6.18.18
• 6.18.19
• 6.18.20
• 6.18.21
• 6.18.22
• 6.18.23
• 6.18.24
• 6.18.25
• 6.18.26
• 6.18.27
• 6.18.28
• 6.18.29
• 6.18.30
• 6.18.31
• 6.18.32
• 6.18.33
• 6.18.34
• 6.18.35
• 6.18.36
• 6.18.37
• 6.18.38
• 6.18.39
• 6.18.40
• 6.18.41
• 6.18.42
• 6.18.43
• 6.18.44
• 6.18.45
• 7.1.0
• 7.1.1
• 7.1.2
• 7.1.3
• 7.1.4
• 7.1.5
• 7.1.6
• 7.1.7
• 7.1.8
• 7.1.9

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Privileges management
CWE: CWE-269 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.266/5.15.217/6.1.184/6.6.153/6.12.105/6.18.46/7.1.10
Patch: bc2e24ba6e167ccf374a197457aa5640a802f429/cf1b5514ddf9df098ce7e3741fc9679fd85a4ec6/cd8b43a71755c516f5c1f265a103438ae9ab15be/b4d73c3848bae9084fa8b9b2aa76d99a7d8eb17d/89a91b30685c0493b0fa2b47d0ab41061a63069d/a88d688be8d7f03cbf927f2ab454ea9fa58d2979/212fc482ddd7f9ccdd74a05eab1cac849350dcd6/32ef1b30ad736519f7a207bcc2986f3d4129d972

Timelineinfo

08/26/2026 Advisory disclosed
08/26/2026 +0 days CVE reserved
08/26/2026 +0 days VulDB entry created
08/26/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80560 (🔒)
GCVE (CVE): GCVE-0-2026-80560
GCVE (VulDB): GCVE-100-395872

Entryinfo

Created: 08/26/2026 17:56
Changes: 08/26/2026 17:56 (59)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

Interested in the pricing of exploits?

See the underground prices here!