CVE-2026-99018

HIGH CVSS 7.8 PoC Available
Published: 2026-10-23
Modified: 2026-10-24
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-99018 is a high-severity vulnerability with a CVSS score of 7.8 affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

Description

In the Linux kernel, the following vulnerability has been resolved: riscv: entry: gate shadow call stack reload on sstatus.SPP, not tp Under CONFIG_SHADOW_CALL_STACK, handle_exception() reloads the kernel shadow call stack pointer (gp) only when the trap came from userspace. It made that decision with scs_load_current_if_task_changed, which compares the trap-time tp (read back from sscratch into s5) against the current tp: beq \prev, tp, _skip_scs scs_load_current _skip_scs: tp is a user-writable register. A user task that sets tp to the linear-map address of its own task_struct (&current) before trapping makes the comparison succeed (can achieve by brute force with KASLR enable under our test), so the kernel skips scs_load_current and keeps running with the gp that userspace left in place. Under CONFIG_SHADOW_CALL_STACK gp is the shadow call stack pointer and load_global_pointer is a no-op, so the compiler-emitted "sd ra, -8(gp)" / "ld ra, -8(gp)" in every non-leaf function then write to, and return through, an attacker-controlled address -- an unprivileged kernel arbitrary-write and control-flow-hijack primitive. The poisoned gp is saved to task_struct.scs_sp on return, so the reload is skipped on every subsequent entry as well. Decide "came from userspace" from the hardware sstatus.SPP bit (already in s1 at this point) instead of from tp, mirroring the check that ret_from_exception already uses a few instructions later. SPP is written by hardware on trap entry and cannot be forged from U-mode. Legitimate behaviour is unchanged: user entries (SPP=0) reload the task shadow call stack, nested kernel entries (SPP=1) skip it.

Attack Chain
1
Reconnaissance

Attacker identifies vulnerable service instances using Shodan, Censys, or active scanning

2
Initial Access

Attacker crafts malicious payload exploiting CVE-2026-99018 to achieve remote code execution

3
Execution

Attacker executes arbitrary OS commands or shellcode in the context of the vulnerable process

4
Persistence

Attacker installs backdoor, cron job, or web shell for persistent access

5
Lateral Movement

Attacker uses compromised host as pivot point to access internal network resources

MITRE ATT&CK Techniques
T1190 Exploit Public-Facing Application
Initial Access

Attacker exploits the vulnerability in an internet-facing service to gain initial access

T1059 Command and Scripting Interpreter
Execution

Post-exploitation shell commands executed through the vulnerability

T1105 Ingress Tool Transfer
Command and Control

Attacker downloads malware or tools after gaining code execution

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
registry_key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\backdoor Persistence mechanism after successful RCE
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.