CVE-2026-98044
Description
A flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) verifier. This issue allows a privileged local user to cause a Denial of Service (DoS) or unexpected program rejection by loading a specially crafted BPF program containing legacy packet-load instructions inside callback functions. Due to an internal logic error during register state analysis on simulated return paths, the verifier fails validation and triggers a kernel warning.
Statement
A LOW severity denial-of-service flaw was found in the Linux kernel BPF (Berkeley Packet Filter) verifier, affecting Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS. A privileged local user who is able to load BPF programs (requiring privileges such as CAP_BPF or CAP_SYS_ADMIN) can load a specially crafted BPF program that uses deprecated legacy packet-load instructions (BPF_LD_ABS or BPF_LD_IND) inside callback functions. Due to an internal logic error in the verifier's register-state analysis on the synthesized failure-return path, precision backtracking triggers the "callback unexpected regs" verifier warning and the BPF_PROG_LOAD operation fails with -EFAULT. The direct consequence is a kernel warning and rejection of the crafted program load; on systems configured to panic on kernel warnings this can result in a system crash. Confidentiality and integrity are not impacted.
Red Hat Enterprise Linux 6, 7, 8, and 9, the RHEL 10.0 and 10.2 streams, and OpenShift Container Platform 4.12 through 4.23 and 5.x are not affected because the vulnerable code is not present in those products. For the affected streams, the fix is deferred: exploitation requires an already-privileged local user and results only in a verifier warning, a failed program load, or warning-induced denial of service, so the fix will be addressed in a future update rather than immediately. The residual risk is limited to local denial of service by a privileged user.
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 | 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
While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, an attacker can still cause a denial of service if they can trigger an assert statement, and if the scope of the assert() extends beyond the attacker's own session. For example, if a server handles multiple simultaneous connections, if an assert() occurs in one single connection that causes all other connections to be dropped, this could be a significant denial of service.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.