CVE-2026-72111
Description
A flaw was found in the Linux kernel's BPF verifier. When processing a context load of an LSM hook return value, the __mark_reg_s32_range() function incorrectly intersects new register bounds with stale ones, rather than replacing them. This can lead to a mismatch between the verifier's understanding of register values and the actual runtime values. An attacker could potentially leverage this verifier/runtime mismatch to bypass BPF memory safety checks.
Statement
A BPF verifier range tracking bug can leave stale bounds on a register before narrowing an LSM hook return value. The verifier may believe the register has a narrower value than it will have at runtime, creating a verifier/runtime mismatch that can bypass BPF memory safety checks. This is a memory safety class issue because an accepted BPF program may perform memory accesses that were validated against incorrect bounds. For the CVSS the PR:L is used for the paranoid score because BPF loading may be available to a local user, delegated service account, container root, or process with reduced BPF related capabilities rather than only to a full host administrator. The issue is local and is not network reachable by itself. Impact may include local privilege escalation, kernel memory corruption, information disclosure, and denial of service.
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 | 8.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| 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:L/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.