CVE-2026-80671
Description
A flaw was found in the Linux kernel's perf sched subsystem. Multiple vulnerabilities exist within the register_pid() function when processing untrusted performance data. These include an integer overflow that can lead to out-of-bounds memory writes and a heap buffer overflow due to improper string handling. Additionally, allocation failures are not handled gracefully, which can result in a denial of service (DoS) by terminating the process. An attacker could potentially exploit these issues to cause memory corruption, leading to arbitrary code execution or system instability.
Statement
A MODERATE severity flaw was found in the Linux kernel's perf tool ('perf sched'), triggered when the userspace perf utility processes an untrusted perf.data file. The register_pid() function contains an integer overflow in the task-array size calculation, which can wrap to a small value on 32-bit systems for large pid values and lead to heap out-of-bounds writes, and copies the untrusted task comm string with strcpy() into a fixed 20-byte buffer without a length check, causing a heap buffer overflow. In addition, allocation failures are handled with BUG_ON, terminating the process. A local attacker who supplies a crafted perf.data file to 'perf sched' could exploit these issues to cause memory corruption in the perf process, potentially leading to arbitrary code execution in the context of the user running the tool, or a denial of service through a crash. Red Hat rates this flaw as MODERATE (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because exploitation requires local access and processing a crafted perf.data file and the impact is confined to the userspace perf tool; this differs from the upstream CVE record's CRITICAL rating, which assumes no privileges and broad confidentiality, integrity, and availability impact. All Red Hat Enterprise Linux and Red Hat In-Vehicle OS kernel, kernel-rt, and kernel-ivos-qualcomm components have been evaluated as NOT AFFECTED because the vulnerable code is not present in these shipped components.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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 | 5.5 | N/A | 9.3 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Changed |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.