CVE-2026-72028

Description

A flaw was found in the Linux kernel's kretprobe (kernel return probe) functionality on RISC-V architectures. A local attacker can trigger a kernel crash by attempting to read from the stack within a kretprobe. This occurs because the arch_rethook_trampoline does not correctly save the original stack pointer, leading to an arbitrary value being used when reading from the stack. Successful exploitation results in a Denial of Service (DoS) due to the kernel crashing.

Statement

This vulnerability is rated as having a Moderate impact because configuring return probe tracing requires elevated local privileges and the potential failure is restricted to a system-level denial of service. Furthermore, this issue specifically affects the RISC-V processor architecture, which is not supported in Red Hat Enterprise Linux. As a result, standard Red Hat kernel packages do not include the vulnerable architecture code and are not impacted.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the uninitialized pointer is used in a read operation, it might not point to a valid memory location. An attacker might be able to read sensitive portions of memory.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the uninitialized pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the uninitialized pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible. If the uninitialized pointer is used as a function call, then arbitrary functions could be invoked.

Frequently Asked Questions

Want to get errata notifications? Sign up here.