CVE-2024-38556

net/mlx5: Add a timeout to acquire the command queue semaphore

HIGH
7.8
CVSS Score
Published: June 19, 2024 at 01:35 PM UTC
Updated: August 5, 2026 at 12:04 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Add a timeout to acquire the command queue semaphore Prevent forced completion handling on an entry that has not yet been assigned an index, causing an out of bounds access on idx = -22. Instead of waiting indefinitely for the sem, blocking flow now waits for index to be allocated or a sem acquisition timeout before beginning the timer for FW completion. Kernel log example: mlx5_core 0000:06:00.0: wait_func_handle_exec_timeout:1128:(pid 185911): cmd[-22]: CREATE_UCTX(0xa04) No done completion

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.10.94v ≥ 5.15.17v ≥ 5.16.3v ≥ 5.4.1745.10.94 ≤ v < 5.115.15.17 ≤ v < 5.165.16.3 ≤ v ≤ 6.1.935.16.3 ≤ v < 5.175.17 ≤ v < 6.1.935.17 ≤ v < 6.105.17 ≤ v < 6.6.335.17 ≤ v < 6.8.125.17 ≤ v < 6.9.35.4.174 ≤ v < 5.56.2 ≤ v ≤ 6.6.336.7 ≤ v ≤ 6.8.126.9 ≤ v ≤ 6.9.34646175c19fd019b773444a11ff62748eb83745b5.10.945.15.175.16.35.175.4.17474dd45122b84479eee50bd0956ae8bc5799c9f8a8e715cd613a1e872b9d918e912d90b399785761ad73d81447c6651904dd4a9e3fd88651ff174c1b7e801f81cee3c8901f52ee48c6329802b28fbb49c
Vendor states this is fixed in 2d0962d05c93de391ce85f6e764df895f47c8918 (fixed)
Vendor states this is fixed in 485d65e1357123a697c591a5aeb773994b247ad7 (fixed)
Vendor states this is fixed in 4baae687a20ef2b82fde12de3c04461e6f2521d6 (fixed)
Vendor states this is fixed in 94024332a129c6e4275569d85c0c1bfb2ae2d71b (fixed)
Vendor states this is fixed in f9caccdd42e999b74303c9b0643300073ed5d319 (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.17 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.93 (unaffected)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.6.33 (unaffected)
Vendor states this is fixed in 6.8.12 (unaffected)
Vendor states this is fixed in 6.9.3 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2d0962d05c93de391ce85f6e764df895f47c8918
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/485d65e1357123a697c591a5aeb773994b247ad7
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4baae687a20ef2b82fde12de3c04461e6f2521d6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/94024332a129c6e4275569d85c0c1bfb2ae2d71b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f9caccdd42e999b74303c9b0643300073ed5d319

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-129

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card