CVE-2026-98951

Register-state corruption via uninitialized ptrace buffers

Published Oct 23, 2026 · Updated Oct 23, 2026

Uninitialized data use in Linux RISC-V ptrace allows local users to corrupt traced register state via short regset writes. In arch/riscv/kernel/ptrace.c, user_regset_copyin() leaves buffer tails unwritten when iov_len is short; riscv_vr_set() consumes those bytes as vector state, while riscv_cfi_set() uses them as a shadow stack pointer. Triggering the affected setters requires permission to trace the target on RISC-V Linux; the published evidence does not establish privilege escalation.

CVSS severityUnavailable
Unscored
EPSS probability0.16%
Next 30 days · Nov 22, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Contact us

Summary

What happened

Uninitialized data use in Linux RISC-V ptrace allows local users to corrupt traced register state via short regset writes. In arch/riscv/kernel/ptrace.c, user_regset_copyin() leaves buffer tails unwritten when iov_len is short; riscv_vr_set() consumes those bytes as vector state, while riscv_cfi_set() uses them as a shadow stack pointer. Triggering the affected setters requires permission to trace the target on RISC-V Linux; the published evidence does not establish privilege escalation.

The record

CVE
CVE-2026-98951
Published
Oct 23, 2026
Updated
Oct 23, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 23, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 23, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.5.3 <6.6
  2. Affected versionversion=6.6
  3. Affected versionversion=9300f00439743c4a34d735e1a27118eb68a1504e <59052a88ba5fe4a7bb34b3a0a42aa5d453d3bb97
  4. Affected versionversion=9300f00439743c4a34d735e1a27118eb68a1504e <89fc70d73f4ac8781f9e15edd1dbc6b6088453b3
  5. Affected versionversion=f2a9cd050901c4734bc175294c3bd6a40a1a9e99

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.5.3 <6.6; version=6.6; version=9300f00439743c4a34d735e1a27118eb68a1504e <59052a88ba5fe4a7bb34b3a0a42aa5d453d3bb97; version=9300f00439743c4a34d735e1a27118eb68a1504e <89fc70d73f4ac8781f9e15edd1dbc6b6088453b3; version=f2a9cd050901c4734bc175294c3bd6a40a1a9e99

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Contact us