CVE-2026-89488
Description
A flaw was found in the Linux kernel's Open vSwitch (OVS) component. An unprivileged user, operating from a user and network namespace, can trigger a use-after-free vulnerability during network namespace teardown. This occurs because packet processing attempts to use connection tracking (CT) limit state after it has been freed, leading to a slab-use-after-free condition. This vulnerability could potentially lead to a denial of service.
Statement
This vulnerability is rated as Important severity because an unprivileged local attacker can induce a race condition resulting in a kernel crash (denial of service) or potential arbitrary code execution with kernel privileges, elevating the risk beyond a Moderate flaw. Exploitation requires the ability to instantiate unprivileged namespaces on systems where the openvswitch subsystem is actively processing connection-tracking flows. Standard enterprise deployments that do not load the Open vSwitch module or do not permit unprivileged user namespace creation are not exposed to this flaw.
Mitigation
To mitigate this vulnerability, prevent the openvswitch kernel module from loading on systems where Open vSwitch is not required:
1. Create a modprobe configuration file to disable the module:
echo "install openvswitch /bin/true" > /etc/modprobe.d/disable-openvswitch.conf
2. If the module is already loaded, unload it:
modprobe -r openvswitch
Warning: Unloading the module or applying this configuration may require restarting services or rebooting the system if the module is currently in use.
Caveat: Disabling the openvswitch module will prevent Open vSwitch from functioning and will break network connectivity in environments that depend on it, such as OpenShift Container Platform clusters utilizing OVN-Kubernetes or OpenShift SDN.
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).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/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.