CVE-2026-46063
Analyzed Analyzed - Analysis Complete
x86/shstk Deadlock in Linux Kernel

Publication date: 2026-05-27

Last updated on: 2026-06-16

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: x86/shstk: Prevent deadlock during shstk sigreturn During sigreturn the shadow stack signal frame is popped. The kernel does this by reading the shadow stack using normal read accesses. When it can't assume the memory is shadow stack, it takes extra steps to makes sure it is reading actual shadow stack memory and not other normal readable memory. It does this by holding the mmap read lock while doing the access and checking the flags of the VMA. Unfortunately that is not safe. If the read of the shadow stack sigframe hits a page fault, the fault handler will try to recursively grab another mmap read lock. This normally works ok, but if a writer on another CPU is also waiting, the second read lock could fail and cause a deadlock. Fix this by not holding mmap lock during the read access to userspace. Instead use mmap_lock_speculate_...() to watch for changes between dropping mmap lock and the userspace access. Retry if anything grabbed an mmap write lock in between and could have changed the VMA. These mmap_lock_speculate_...() helpers use mm::mm_lock_seq, which is only available when PER_VMA_LOCK is configured. So make X86_USER_SHADOW_STACK depend on it. On x86, PER_VMA_LOCK is a default configuration for SMP kernels. So drop support for the other configs under the assumption that the !SMP shadow stack user base does not exist. Currently there is a check that skips the lookup work when the SSP can be assumed to be on a shadow stack. While reorganizing the function, remove the optimization to make the tricky code flows more common, such that issues like this cannot escape detection for so long.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-27
Last Modified
2026-06-16
Generated
2026-06-16
AI Q&A
2026-05-27
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.7 (inc) to 6.12.88 (exc)
linux linux_kernel From 6.13 (inc) to 6.18.27 (exc)
linux linux_kernel From 6.19 (inc) to 7.0.4 (exc)
linux linux_kernel From 6.6 (inc) to 6.6.140 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-667 The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the Linux kernel's x86 shadow stack implementation during the sigreturn process. When the kernel pops the shadow stack signal frame, it reads the shadow stack memory while holding the mmap read lock to ensure it is accessing valid shadow stack memory. However, if this read causes a page fault, the fault handler attempts to acquire the mmap read lock again, which can lead to a deadlock if another CPU is holding a write lock.

The issue arises because the kernel holds the mmap read lock during the read access, which is unsafe. The fix involves not holding the mmap lock during the read and instead using a speculative locking mechanism (mmap_lock_speculate_...) to detect changes and retry if necessary. This change requires certain kernel configuration dependencies and removes some optimizations to make the code paths more robust.

Impact Analysis

This vulnerability can cause a deadlock in the Linux kernel during the sigreturn process on x86 systems using the shadow stack feature. A deadlock means that the system or affected processes could hang or become unresponsive, potentially leading to denial of service conditions.

Mitigation Strategies

The vulnerability has been resolved by changes in the Linux kernel related to the handling of the shadow stack during sigreturn.

Immediate mitigation involves updating your Linux kernel to a version that includes the fix for this issue.

The fix prevents deadlock by not holding the mmap lock during the read access to userspace and instead uses mmap_lock_speculate_...() helpers to safely handle memory access.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46063. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart