CVE-2026-80519
Description
A flaw was found in the Linux kernel. Specifically, within the OpenVPN (OVPN) module's crypto completion callback mechanism, a timing issue exists. This vulnerability arises when peer references are released prematurely, before the associated cleanup operations are complete. An attacker could potentially exploit this to trigger a use-after-free condition, leading to system instability or a denial of service (DoS).
Statement
Red Hat Enterprise Linux and Red Hat In-Vehicle OS are not affected by this Moderate-severity Linux kernel flaw, because the vulnerable ovpn (OpenVPN) module code is not present in any shipped Red Hat kernel version. The flaw is a use-after-free in the ovpn module's crypto completion callback cleanup. These callbacks hold both key-slot and peer references, and the peer reference pins the netdev; when the peer reference is dropped before the callback has finished its own cleanup, an RCU callback backed by module text can be scheduled after ovpn_cleanup's rcu_barrier has already run, and the TX error path can free the remaining skb outside the peer/netdev lifetime window. A local attacker with the ability to interact with the ovpn module on an affected kernel could exploit this timing flaw to trigger a use-after-free, resulting in a kernel panic and denial of service. Red Hat rates this flaw Moderate (CVSS 5.5, availability impact only) because exploitation requires local access and privileges; this differs from the Critical 9.8 score in the upstream CVE record, which assumes a network attack vector with no privileges or user interaction that is not consistent with the local, privilege-gated attack path of this flaw.
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.8 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| 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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
