Loading vulnerability…
CVE-2026-43493 affects the Linux kernel's pcrypt cryptographic parallelization component. Requests marked MAY_BACKLOG can return EBUSY, which the vulnerable implementation handles incorrectly, along with EINPROGRESS notifications. The correction explicitly handles EBUSY and filters out EINPROGRESS notifications. Incorrect handling may disrupt cryptographic request processing and potentially cause denial of service; the precise security consequences are not established.
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.
45 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Incorrect handling of MAY_BACKLOG requests in the Linux kernel pcrypt cryptographic component. The content does not specify the precise security impact.
A vulnerability in the Linux kernel's pcrypt cryptographic component involving incorrect handling of MAY_BACKLOG requests and EBUSY/EINPROGRESS responses. The advisory assigns a critical CVSS v3 base score of 9.8 and recommends updating the linux package and related packages to version 6.1.176-1 or later. It states that no known exploits are available.
A Linux kernel vulnerability addressed in Red Hat Enterprise Linux EUS 9.6 kernel packages.
A vulnerability addressed by the referenced CentOS Stream 8 TuxCare security update; no technical details are provided.
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.