Skip to main content

In the Linux kernel, the following vulnerability has been resolved: riscv: entry: gate shadow call stack reload on sstatus.SPP, not tp Under… (CVE-2026-99018)

0
High
Published: 10/23/2026 (10/23/2026, 15:31:35 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's RISC-V architecture under CONFIG_SHADOW_CALL_STACK allowed an unprivileged user to bypass kernel shadow call stack pointer reload checks by manipulating the user-writable tp register. This could lead to arbitrary kernel memory write and control-flow hijacking. The issue was fixed by changing the check to rely on the hardware sstatus.SPP bit, which cannot be forged by user mode, ensuring correct reload of the shadow call stack pointer on user traps.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/23/2026, 18:54:08 UTC

Technical Analysis

The vulnerability in the Linux kernel's RISC-V entry code under CONFIG_SHADOW_CALL_STACK involved an incorrect determination of whether a trap came from userspace. The kernel used a comparison of the trap-time tp register (user-writable) against the current tp to decide whether to reload the kernel shadow call stack pointer (gp). An attacker could set tp to the linear-map address of its own task_struct before trapping, causing the kernel to skip reloading gp and continue execution with a poisoned gp value controlled by userspace. This allowed an unprivileged kernel arbitrary-write and control-flow hijack primitive. The fix changes the decision to use the hardware sstatus.SPP bit, which is set by hardware on trap entry and cannot be forged from user mode, thus correctly gating the shadow call stack reload.

Potential Impact

An unprivileged user could exploit this vulnerability to perform arbitrary writes in kernel memory and hijack kernel control flow, potentially leading to privilege escalation or kernel compromise. The vulnerability arises from improper validation of the trap origin, allowing manipulation of the shadow call stack pointer.

Mitigation Recommendations

A fix is available that changes the trap origin check to rely on the hardware sstatus.SPP bit instead of the user-writable tp register. Users should apply the official Linux kernel patch that addresses this issue. No alternative mitigations are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-7x79-hrpm-vw9w
Osv Schema Version
1.4.0
Aliases
["CVE-2026-99018"]

Threat ID: 6adbaacfd73cc49347b2053c

Added to database: 10/23/2026, 18:43:27 UTC

Last enriched: 10/23/2026, 18:54:08 UTC

Last updated: 10/23/2026, 23:45:11 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses