CVE-2024-38556: net/mlx5: Add a timeout to acquire the command queue semaphore
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
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects the mlx5 network driver’s command handling. A command path could wait incorrectly and then process a forced completion before a queue index exists, causing an out-of-bounds access. The public data does not provide CVSS, business impact, or confirmed exploitation evidence.
Executive priority
Track this through normal vulnerability management, with faster action for critical Linux servers using mlx5 networking. There is no cited evidence of active exploitation, but kernel out-of-bounds access warrants timely patch planning.
Technical view
The fix adds timeout-aware semaphore acquisition in net/mlx5 command queue handling. The resolved bug involved forced completion on an entry without an assigned index, producing idx = -22 and an out-of-bounds access during firmware command completion handling.
Likely exposure
Likely limited to Linux systems running affected kernels with the mlx5 driver in use. The bundle lists Linux affected versions including 5.17, 6.1.93, 6.6.33, 6.8.12, 6.9.3, and 6.10, but product and environment exposure details are incomplete.
Exploitation context
No source in the bundle states active exploitation, public exploit availability, or inclusion in CISA KEV. Treat this as a kernel stability and memory-safety issue until vendor advisories provide stronger impact details.
Researcher notes
Evidence is limited to the Linux CVE text and stable commit references. The bundle does not include CVSS, CWE, exploitability analysis, or distribution-specific package status, so validation should focus on kernel version, driver use, and vendor backports.
Mitigation direction
Update affected Linux kernels to a release containing the referenced stable fixes.
Prioritize systems using the mlx5 driver in production or multi-tenant environments.
Check distribution vendor advisories for packaged kernel fix availability.
Avoid direct wrangler or deployment assumptions; follow normal kernel maintenance process.
Validation and detection
Inventory Linux hosts and identify kernels using the mlx5 driver.
Compare installed kernel packages against vendor advisories for CVE-2024-38556.
Review kernel logs for mlx5_core command timeout messages similar to the cited example.
Confirm the deployed kernel includes one of the referenced stable commits.
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-2024-38556 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.