Skip to main content

In the Linux kernel, the following vulnerability has been resolved: riscv: futex: untag the user pointer before the atomic access access_ok() checks… (CVE-2026-99016)

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

Description

A vulnerability in the Linux kernel's RISC-V futex implementation allows an unprivileged process to perform atomic read-modify-write operations on arbitrary kernel addresses due to improper handling of tagged user pointers. The issue arises because the futex atomic operations use the raw tagged address without untagging it after access_ok() validation, enabling potential kernel memory manipulation. This vulnerability has been resolved by ensuring the pointer is untagged before the atomic operations.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/23/2026, 18:56:31 UTC

Technical Analysis

The Linux kernel's RISC-V futex code did not untag user pointers before performing atomic operations, despite access_ok() validating the untagged address. When the tagged address ABI is enabled, the tagged pointer used in atomic operations can overlap with kernel virtual addresses, allowing an unprivileged process to perform atomic read-modify-write operations on arbitrary kernel memory. This occurs because supervisor-mode data accesses do not strip tag bits, and the futex atomic helpers used the raw tagged address. The fix involves untagging the pointer in futex helpers to match the address validated by access_ok().

Potential Impact

An unprivileged user process can exploit this vulnerability to perform atomic read-modify-write operations on arbitrary kernel memory addresses, potentially leading to unauthorized kernel memory modification or information disclosure via the FUTEX_OP_CMP_* result as a read oracle. This undermines kernel memory protection and could facilitate privilege escalation or kernel integrity compromise.

Mitigation Recommendations

A fix has been implemented in the Linux kernel to untag the user pointer before performing atomic futex operations, ensuring the address used matches the one validated by access_ok(). Users should apply the official kernel update that includes this fix to mitigate the vulnerability.

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-5mv4-wx47-m6wh
Osv Schema Version
1.4.0
Aliases
["CVE-2026-99016"]

Threat ID: 6adbaacfd73cc49347b2055e

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

Last enriched: 10/23/2026, 18:56:31 UTC

Last updated: 10/23/2026, 23:05:09 UTC

Views: 4

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