Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-38556net/mlx5: Add a timeout to acquire the command queue semaphore

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

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-38556, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 8e715cd613a1e872b9d918e912d90b399785761a – < 4baae687a20ef2b82fde12de3c04461e6f2521d6
    • affected 8e715cd613a1e872b9d918e912d90b399785761a – < f9caccdd42e999b74303c9b0643300073ed5d319
    • affected 8e715cd613a1e872b9d918e912d90b399785761a – < 2d0962d05c93de391ce85f6e764df895f47c8918
    • affected 8e715cd613a1e872b9d918e912d90b399785761a – < 94024332a129c6e4275569d85c0c1bfb2ae2d71b
    • affected 8e715cd613a1e872b9d918e912d90b399785761a – < 485d65e1357123a697c591a5aeb773994b247ad7
    • affected 74dd45122b84479eee50bd0956ae8bc5799c9f8a
    • affected e801f81cee3c8901f52ee48c6329802b28fbb49c
    • affected d73d81447c6651904dd4a9e3fd88651ff174c1b7
    • affected 4646175c19fd019b773444a11ff62748eb83745b
    • affected 5.4.174 – < 5.5
    • affected 5.10.94 – < 5.11
    • affected 5.15.17 – < 5.16
    • affected 5.16.3 – < 5.17
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 6.1.93 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.8.12 – ≤ 6.8.*
    • unaffected 6.9.3 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-38556 badge
[![CVE-2024-38556](https://cveledger.app/badge/CVE-2024-38556.svg)](https://cveledger.app/cve/CVE-2024-38556)

Record last updated .