CVE-2026-98552

Description

A flaw was found in the Linux kernel's Performance Counters for Linux (perf) subsystem. A race condition during the attachment of performance monitoring context data can cause the kernel to fail to update tracking flags, resulting in a reference count leak. A local attacker could exploit this vulnerability to prevent allocated kernel memory from being released, potentially leading to memory exhaustion and a denial of service (DoS).

Statement

This vulnerability is evaluated as Low severity because triggering the race condition requires authenticated local access, specific timing preconditions, and only causes a gradual leakage of kernel memory without enabling code execution or privilege escalation. Older distributions including Red Hat Enterprise Linux 8 and 9 do not include the affected context attachment logic and remain unaffected. In environments where this code is present, substantial and sustained local activity would be required to induce a system-wide denial of service.

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 Score2.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactLowN/AN/A

Vector

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing an error that causes the product to crash or exit out of its current operation.

Frequently Asked Questions

Want to get errata notifications? Sign up here.