riscv: process: Fix kernel gp leakage
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 00effef72c98294edb1efa87ffa0f6cfb61b36a4, 9abc3e6f1116adb7a2d4fbb8ce20c37916976bf5, d14fa1fcf69db9d070e75f1c4425211fa619dfc8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 00effef72c98294edb1efa87ffa0f6cfb61b36a4, 9abc3e6f1116adb7a2d4fbb8ce20c37916976bf5, d14fa1fcf69db9d070e75f1c4425211fa619dfc8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernel5.11 and later · before 5.15.154
- linux linux kernel5.16 and later · before 6.1.85
- linux linux kernel4.15 and later · before 5.10.216
- linux linux kernel6.7 and later · before 6.8.5
- linux linux kernel6.2 and later · before 6.6.26
- linux linux kernel6.9
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.15affected
- 7db91e57a0acde126a162ababfb1e0ab190130cb and later · before 9abc3e6f1116adb7a2d4fbb8ce20c37916976bf5affected · git
- 7db91e57a0acde126a162ababfb1e0ab190130cb and later · before dff6072124f6df77bfd36951fbd88565746980efaffected · git
- 7db91e57a0acde126a162ababfb1e0ab190130cb and later · before f6583444d7e78dae750798552b65a2519ff3ca84affected · git
- 7db91e57a0acde126a162ababfb1e0ab190130cb and later · before 00effef72c98294edb1efa87ffa0f6cfb61b36a4affected · git
- 7db91e57a0acde126a162ababfb1e0ab190130cb and later · before d8dcba0691b8e42bddb61aab201e4d918a08e5d9affected · git
- 7db91e57a0acde126a162ababfb1e0ab190130cb and later · before d14fa1fcf69db9d070e75f1c4425211fa619dfc8affected · git
- before 4.15not affected · semver
- 5.10.216 and later · up to and including 5.10.*not affected · semver
- 5.15.154 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.85-1 | 6.1.85-1 |
| Debian:13 | linux | before 6.8.9-1 | 6.8.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2024-35869May 19, 2024 · smb: client: guarantee refcounted children from parent session39Monitor
- ← EarlierCVE-2024-35870May 19, 2024 · smb: client: fix UAF in smb2_reconnect_server()39Monitor
- Later →CVE-2024-35872May 19, 2024 · mm/secretmem: fix GUP-fast succeeding on secretmem folios22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 00effef72c98294edb1efa87ffa0f6cfb61b36a4 | Vendor (CNA) |
| Linux Linux | 9abc3e6f1116adb7a2d4fbb8ce20c37916976bf5 | Vendor (CNA) |
| Linux Linux | d14fa1fcf69db9d070e75f1c4425211fa619dfc8 | Vendor (CNA) |
| Linux Linux | d8dcba0691b8e42bddb61aab201e4d918a08e5d9 | Vendor (CNA) |
| Linux Linux | dff6072124f6df77bfd36951fbd88565746980ef | Vendor (CNA) |
| Linux Linux | f6583444d7e78dae750798552b65a2519ff3ca84 | Vendor (CNA) |
| debian:linux | 6.1.85-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0506 · May 20, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/9abc3e6f1116adb7a2d4fbb8ce20c37916976bf5
- git.kernel.org/stable/c/d14fa1fcf69db9d070e75f1c4425211fa619dfc8
- git.kernel.org/stable/c/d8dcba0691b8e42bddb61aab201e4d918a08e5d9
- git.kernel.org/stable/c/dff6072124f6df77bfd36951fbd88565746980ef
- git.kernel.org/stable/c/f6583444d7e78dae750798552b65a2519ff3ca84
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.