CVE-2026-97962
Description
A flaw was found in the Linux kernel's mlx5 network driver. The driver fails to hold the required lock when destroying virtual network interface health reporters during device unloading. A local user with administrative privileges could trigger this flaw by unbinding the driver, resulting in a kernel assertion failure that may cause system instability or a Denial of Service (DoS).
Statement
A moderate-impact flaw exists in the Linux kernel mlx5 network driver as shipped in Red Hat Enterprise Linux 8, 9, and 10, Red Hat In-Vehicle OS 2, and the RHEL CoreOS 9 kernel used by OpenShift Container Platform 4. The mlx5e representor vnic devlink health reporter is created and destroyed along the representor netdev (un)load path, which is not serialized by the devlink instance lock. Consequently, when a local user with administrative privileges unbinds the mlx5 driver, destruction of the health reporter triggers a kernel assertion failure (a devl_assert_locked() WARNING). This kernel warning may cause system instability or a denial of service, particularly on systems where panic_on_warn is enabled. Confidentiality and integrity are not impacted; Red Hat rates this flaw Moderate severity (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Fixes for the affected streams are currently deferred to a future routine update because the issue manifests as a kernel warning that requires privileged local access to trigger and affects only availability, so it does not warrant an immediate out-of-band kernel update; the residual risk is limited to local denial of service on hosts where an administrative user unbinds the mlx5 driver. Red Hat Enterprise Linux 7, the RHEL 8.4, 8.6, and 8.8 update streams, the RHEL 9.2 update stream, and OpenShift Container Platform versions built on RHEL CoreOS 8 are not affected because the vulnerable code, the mlx5e representor vnic devlink health reporter, is not present in those versions.
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.