CVE-2026-80667
Description
A flaw was found in the Linux kernel's Mellanox (mlx5) network driver, specifically within the Multi-Port Ethernet Switch (MPESW) work handling for Link Aggregation Groups (LAG). When the mlx5_lag_get_devcom_comp() function returns a null value, the mlx5_mpesw_work() function fails to call complete(). This oversight can cause a process waiting for the work to finish to block indefinitely, leading to a denial of service (DoS) for the affected system.
Statement
A flaw in the Linux kernel's Mellanox (mlx5) network driver was rated as having low security impact for Red Hat products. The flaw is in the Multi-Port Ethernet Switch (MPESW) work handling for Link Aggregation Groups (LAG): when mlx5_lag_get_devcom_comp() returns NULL, mlx5_mpesw_work() returns early without calling complete(), so a caller that queued the work and waits on the completion object can block indefinitely, causing a local denial of service. Triggering the vulnerable path requires local access and specific LAG/MPESW configuration on Mellanox hardware; it is not reachable through ordinary network traffic, and it affects availability only, with no impact on confidentiality or integrity. Red Hat Enterprise Linux 6, 7, and 8 and the RHEL 9.2.0.z and 9.4.z streams are not affected because the vulnerable code is not present there, while the kernel and kernel-rt packages in RHEL 9.6.z, 9.8.z, 9.9, and 9.10, the kernel packages in RHEL 10.0.z, 10.2.z, 10.3, and 10.4, and the kernel and kernel-ivos-qualcomm packages in Red Hat In-Vehicle OS 2.0 and 2.1 are affected. The fix for the affected streams is currently deferred given the low impact; the residual risk of deferral is limited to a local, hard-to-trigger hang in the mlx5 driver control path rather than memory corruption, information disclosure, or privilege escalation.
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: Resource Consumption (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart
Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.