CVE-2026-98551
Description
A flaw was found in the Linux kernel's Performance Events (perf) subsystem on ARM64 architectures. This flaw allows a local user to cause an information disclosure of sensitive kernel memory. The issue occurs because certain branch tracking data structures are not properly cleared, allowing an attacker reading branch records to access uninitialized kernel memory.
Statement
This vulnerability is classified as Low impact for Red Hat products because it requires local system access, cannot be exploited remotely, and only affects ARM64 hardware utilizing branch recording capabilities. While uninitialized heap memory can leak into user space through performance monitoring records, the exposure does not enable privilege escalation or permit tampering with kernel memory. Additionally, earlier enterprise releases such as Red Hat Enterprise Linux 7 and 8 do not contain the affected 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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.3 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | Low | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | None | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory; Read Application Data
When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability
The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.
Other
Technical Impact: Unexpected State; Varies by Context
The consequences vary depending on the type of resource and how it is used within the product.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
