CVE-2024-35871: riscv: process: Fix kernel gp leakage
In the Linux kernel, the following vulnerability has been resolved:
riscv: process: Fix kernel gp leakage
childregs represents the registers which are active for the new thread
in user context. For a kernel thread, childregs->gp is never used since
the kernel gp is not touched by switch_to. For a user mode helper, the
gp value can be observed in user space after execve or possibly by other
means.
[From the email thread]
The /* Kernel thread */ comment is somewhat inaccurate in that it is also used
for user_mode_helper threads, which exec a user process, e.g. /sbin/init or
when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have
PF_KTHREAD set and are valid targets for ptrace etc. even before they exec.
childregs is the *user* context during syscall execution and it is observable
from userspace in at least five ways:
1. kernel_execve does not currently clear integer registers, so the starting
register state for PID 1 and other user processes started by the kernel has
sp = user stack, gp = kernel __global_pointer$, all other integer registers
zeroed by the memset in the patch comment.
This is a bug in its own right, but I'm unwilling to bet that it is the only
way to exploit the issue addressed by this patch.
2. ptrace(PTRACE_GETREGSET): you can PTRACE_ATTACH to a user_mode_helper thread
before it execs, but ptrace requires SIGSTOP to be delivered which can only
happen at user/kernel boundaries.
3. /proc/*/task/*/syscall: this is perfectly happy to read pt_regs for
user_mode_helpers before the exec completes, but gp is not one of the
registers it returns.
4. PERF_SAMPLE_REGS_USER: LOCKDOWN_PERF normally prevents access to kernel
addresses via PERF_SAMPLE_REGS_INTR, but due to this bug kernel addresses
are also exposed via PERF_SAMPLE_REGS_USER which is permitted under
LOCKDOWN_PERF. I have not attempted to write exploit code.
5. Much of the tracing infrastructure allows access to user registers. I have
not attempted to determine which forms of tracing allow access to user
registers without already allowing access to kernel registers.
Security readout for executives and security teams
Plain-English summary
CVE-2024-35871 is a Linux kernel issue on RISC-V where a kernel pointer value can leak into user-observable process register state. This is not described as direct takeover, but it can weaken kernel address isolation and aid later attacks. No cited source says it is actively exploited.
Executive priority
Handle in normal kernel patch cycles, with priority for internet-facing, multi-user, or high-sensitivity RISC-V systems. Escalate if your environment relies on custom kernels or delayed downstream security updates.
Technical view
The RISC-V kernel could leave the kernel gp value in childregs for user-mode helper paths. That user context may be visible after execve or through register-observation mechanisms such as ptrace, perf user register sampling, or tracing. Stable Linux commits resolve the leakage.
Likely exposure
Exposure appears limited to Linux systems running affected RISC-V kernels or downstream builds lacking the referenced stable fixes. The bundle names Linux as affected and cites Debian LTS guidance, but it does not provide a complete distribution-by-distribution matrix.
Exploitation context
The source bundle says KEV is false and provides no evidence of public exploitation. The email-thread text discusses several possible observation paths, but also states exploit code was not attempted. Treat this as an information leak that may support further kernel attack research.
Researcher notes
Key uncertainty is practical impact. Sources document leakage of a kernel gp value through user-observable register state, but do not establish weaponized exploitation or a complete exposure matrix. Focus validation on RISC-V kernel lineage and backported fix presence.
Mitigation direction
Apply vendor kernel updates that include the referenced stable Linux fixes.
Check Debian LTS or your distribution advisory for patched package versions.
Prioritize RISC-V Linux assets and images first.
Avoid assuming non-RISC-V systems are affected without vendor confirmation.
Track kernel backport status for custom or embedded builds.
Validation and detection
Inventory RISC-V Linux hosts and kernel versions.
Confirm your kernel includes one of the referenced stable commits or a distro backport.
Review distribution advisories for CVE-2024-35871 coverage.
Check custom kernels for the childregs gp initialization fix.
Record unsupported kernels for upgrade or compensating controls review.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-35871 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.