CVE-2025-21662: net/mlx5: Fix variable not being completed when function returns
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5: Fix variable not being completed when function returns
When cmd_alloc_index(), fails cmd_work_handler() needs
to complete ent->slotted before returning early.
Otherwise the task which issued the command may hang:
mlx5_core 0000:01:00.0: cmd_work_handler:877:(pid 3880418): failed to allocate command entry
INFO: task kworker/13:2:4055883 blocked for more than 120 seconds.
Not tainted 4.19.90-25.44.v2101.ky10.aarch64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/13:2 D 0 4055883 2 0x00000228
Workqueue: events mlx5e_tx_dim_work [mlx5_core]
Call trace:
__switch_to+0xe8/0x150
__schedule+0x2a8/0x9b8
schedule+0x2c/0x88
schedule_timeout+0x204/0x478
wait_for_common+0x154/0x250
wait_for_completion+0x28/0x38
cmd_exec+0x7a0/0xa00 [mlx5_core]
mlx5_cmd_exec+0x54/0x80 [mlx5_core]
mlx5_core_modify_cq+0x6c/0x80 [mlx5_core]
mlx5_core_modify_cq_moderation+0xa0/0xb8 [mlx5_core]
mlx5e_tx_dim_work+0x54/0x68 [mlx5_core]
process_one_work+0x1b0/0x448
worker_thread+0x54/0x468
kthread+0x134/0x138
ret_from_fork+0x10/0x18
Security readout for executives and security teams
Plain-English summary
CVE-2025-21662 is a Linux kernel mlx5 driver flaw where an error path can leave a command waiting forever. In practical terms, affected systems may experience hung kernel worker tasks and degraded network device behavior. The public sources do not provide CVSS, exploitability, or a clear attacker model.
Executive priority
Prioritize patching on infrastructure that depends on mlx5 networking, especially production hosts where a kernel task hang could affect service availability. There is no source-backed evidence of active exploitation, so urgency should be operational-risk driven rather than incident-response driven.
Technical view
In net/mlx5, cmd_work_handler() returned early after cmd_alloc_index() failure without completing ent->slotted. Callers waiting in cmd_exec() could remain blocked, producing hung task reports. The kernel stable references are fixes for this completion handling issue across maintained branches.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with mlx5 driver usage. The bundle lists affected Linux versions including 6.10, 6.1.125, 6.6.72, 6.12.10, and 6.13, but product-specific distro mappings require vendor confirmation.
Exploitation context
No active exploitation is supported by the provided sources. The CVE is not marked KEV, and the bundle does not describe exploit code, remote reachability, privilege requirements, or public weaponization. Treat this primarily as an availability risk until vendor advisories clarify impact.
Researcher notes
The source evidence supports a missed completion on an mlx5 command error path causing waits to hang. Missing data includes CVSS, attacker prerequisites, remote/local triggerability, and distro-specific affected package ranges. Avoid assuming exploitability beyond the documented availability failure mode.
Mitigation direction
Apply kernel or distro updates that include the referenced stable fixes.
Check Linux vendor advisories for affected package versions and backports.
Prioritize systems using mlx5 network devices or modules.
Plan maintenance windows for kernel upgrades where reboot is required.
Monitor vendor guidance if running custom or long-term kernels.
Validation and detection
Inventory kernel versions against vendor advisories and the CVE record.
Confirm whether mlx5 drivers are present and used on critical hosts.
Review kernel logs for cmd_work_handler allocation failures or hung task reports.
Verify updated kernels include the relevant stable fix commits.
Confirm post-update stability on hosts using mlx5 networking.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21662 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jan 21, 2025, 12:18 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.