CVE-2026-43109
Description
In the Linux kernel, the following vulnerability has been resolved:
x86: shadow stacks: proper error handling for mmap lock
김영민 reports that shstk_pop_sigframe() doesn't check for errors from mmap_read_lock_killable(), which is a silly oversight, and also shows that we haven't marked those functions with "__must_check", which would have immediately caught it.
So let's fix both issues.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In Linux kernel x86 shadow stack, shstk_pop_sigframe() ignores mmap_read_lock_killable() errors; patches add proper checks and __must_check.
Vulnerability
Details
In the Linux kernel's x86 shadow stack code, the function shstk_pop_sigframe() calls mmap_read_lock_killable() but fails to check its return value. This function can return an error if the lock attempt is interrupted by a signal, and ignoring the error means the function may proceed without holding the mmap read lock, potentially leading to access of inconsistent or unprotected memory [1].
Exploitation
To exploit this, an attacker needs local access and the ability to send signals to a process using shadow stacks. If a signal interrupts the lock acquisition during the execution of shstk_pop_sigframe(), the kernel may manipulate shadow stack state without proper synchronization, leading to a race condition. The complexity is high due to precise timing requirements.
Impact
A successful exploit could result in memory corruption or information disclosure, but the exact impact is limited by the function's role in signal handling. An attacker may be able to cause a denial of service or potentially escalate privileges if combined with other vulnerabilities.
Mitigation
The kernel community has fixed the issue by adding error checking for mmap_read_lock_killable() and marking the relevant functions with __must_check to prevent future oversights. Multiple stable kernel commits address this vulnerability [1][2][3][4]. Users should update to a kernel version that includes these patches.
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
5- git.kernel.org/stable/c/262b6d38a81d51b135db81e1f30c13d30e38feeenvdPatch
- git.kernel.org/stable/c/52f657e34d7b21b47434d9d8b26fa7f6778b63a0nvdPatch
- git.kernel.org/stable/c/c64cebcc5c4f223dbcbe7dcdf74908fc092a0aa4nvdPatch
- git.kernel.org/stable/c/1a30468eff661937d978495644d2e5ebfeef5ce6nvd
- git.kernel.org/stable/c/c79cf42321600e931933e11f94aba8b245d4cd66nvd
News mentions
1- Patch Tuesday - May 2026Rapid7 Blog · May 13, 2026