CVE-2026-93044
Description
A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) component. This vulnerability occurs when the BPF interpreter attempts to process specific arena-related instructions that it does not support, particularly when a BPF program uses an arena map. This can lead to a kernel bug and an 'Oops' condition, resulting in a system crash and a Denial of Service (DoS) for the affected system.
Statement
BPF arena related instructions are not supported by the BPF interpreter, but an arena based program could still reach interpreter fallback and execute unsupported opcodes. This causes the interpreter to hit BUG_ON() in ___bpf_prog_run and can crash the kernel. For the CVSS the PR:L is used because triggering requires a local user or process able to load the relevant BPF program, but this does not necessarily mean full root privileges in practical deployments. The issue is not network reachable and is triggered through the local BPF control plane rather than packet traffic. Impact is denial of service only via kernel crash. No UAF, OOB access, or arbitrary write primitive is indicated by the code change, so confidentiality and integrity impact are not assigned.
Mitigation
Mitigation for this issue is either not available or the currently available options don't 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 | 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 | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/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)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
If an attacker can trigger the allocation of the limited resources, but the number or size of the resources is not controlled, then the most common result is denial of service. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment, i.e., the product may slow down, crash due to unhandled errors, or lock out legitimate users. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system.
Access Control,Other
Technical Impact: Bypass Protection Mechanism; Other
In some cases it may be possible to force the product to "fail open" in the event of resource exhaustion. The state of the product -- and possibly the security functionality - may then be compromised.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.