CVE-2026-80667
Received Received - Intake

Memory Leak in Linux Kernel LAG Component

Publication date: 2026-08-28

Last updated on: 2026-08-28

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error mlx5_mpesw_work() returned without calling complete() when mlx5_lag_get_devcom_comp() returned NULL. A caller that queued the work and waited on mpesww->comp would block indefinitely. Funnel the early-return path through a new "complete" label so the waiter is always woken.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-28
Last Modified
2026-08-28
Generated
2026-09-17
AI Q&A
2026-08-28
EPSS Evaluated
2026-09-15
NVD
CVE-2026-80667
EUVD
EUVD-2026-67543

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux_kernel linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a missing complete() call in the mlx5_mpesw_work() function when mlx5_lag_get_devcom_comp() returns NULL. This causes a caller waiting on mpesww->comp to block indefinitely, leading to a potential deadlock situation.

Detection Guidance

This vulnerability may cause indefinite blocking in the Linux kernel's mlx5 driver when handling LAG or MPESW operations. Detection requires checking kernel logs for hangs or timeouts in mlx5-related processes. Monitor for processes stuck in 'D' state (uninterruptible sleep) using commands like 'ps aux | grep mlx5' or 'top'. Check kernel logs with 'dmesg | grep mlx5' for errors or warnings.

Impact Analysis

If you use systems with the affected Linux kernel, this vulnerability could cause processes to hang indefinitely when certain network operations fail. This may lead to system unresponsiveness or crashes in scenarios involving MLX5 network drivers.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a kernel-level issue causing indefinite blocking due to missing completion handling in the mlx5 driver, which could lead to system hangs but does not involve data exposure or privacy violations.

Mitigation Strategies

Apply the latest kernel update from your Linux distribution to patch the mlx5 driver issue. If immediate patching is not possible, consider disabling affected mlx5 features or services temporarily. Monitor vendor advisories for official patches and workarounds.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-80667. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart