Loading vulnerability…
CVE-2024-26584 is an incorrect status-code handling flaw in the Linux kernel TLS subsystem's asynchronous AEAD cryptographic request processing. TLS crypto requests are submitted with CRYPTO_TFM_REQ_MAY_BACKLOG. Under valid crypto backlogging conditions, such as a saturated cryptd AES-NI queue, the crypto API can return -EBUSY while retaining the request for later processing, rather than returning -EINPROGRESS. The affected TLS handling did not correctly treat this valid asynchronous state; a backlogged request may also produce an initial asynchronous callback with -EINPROGRESS followed by a successful completion callback. The upstream correction uses TLS asynchronous-crypto wait helpers and translates -EBUSY to -EINPROGRESS, preserving the established asynchronous error-handling path.
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.
22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel TLS flaw in handling backlogged cryptographic requests.
Linux kernel TLS crypto-request backlog handling vulnerability.
Linux kernel TLS flaw involving backlog handling of cryptographic requests.
Linux kernel TLS cryptographic-request backlog handling vulnerability.
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.