CVE-2024-38556 is an out-of-bounds access vulnerability in the Linux kernel mlx5 networking driver’s command-queue handling. The command path could wait indefinitely while acquiring the command-queue semaphore. Forced completion handling could then operate on a command entry before its index had been allocated, using the invalid index value -22 and accessing the command-entry array out of bounds. The fix waits for index allocation or semaphore-acquisition timeout before starting the firmware-completion timer.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A missing timeout when acquiring a command-queue semaphore in the Linux kernel mlx5 network driver.
Linux kernel mlx5 network-driver flaw involving acquisition of the command-queue semaphore without a timeout.
Linux kernel net/mlx5 flaw addressed by adding a timeout when acquiring the command-queue semaphore.
Linux kernel mlx5 networking-driver issue involving acquisition of the command-queue semaphore without a timeout.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.