CVE-2026-43493·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix handling of MAY_BACKLOG requests MAY_BACKLOG requests can return EBUSY. Handle them by checking for that value and filtering out EINPROGRESS notifications.
- Severity
- critical
- Software
- Kernel
- Fixed in
- 7.0.4
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.62% — higher than 49% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-43493 scores 9.8 on CVSS, so a successful attack would be serious — but at 0.62%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.4
Fixed in: 7.0.4
How to fix this CVE
Update your Linux kernel to version 7.0.4 or later to resolve a critical vulnerability in the pcrypt cryptographic module's handling of backlogged requests. This patch corrects improper error handling that could lead to system compromise through malformed cryptographic operations. Apply security updates immediately across all affected systems running kernel versions 6.19 through 7.0.3.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version with `uname -r` and compare against 7.0.4 (vulnerable if between 6.19 and 7.0.3)
- Step 2: Verify pcrypt module is loaded by running `lsmod | grep pcrypt` (if present, the vulnerable component is active)
- Step 3: Search system logs for pcrypt-related errors using `grep -i 'pcrypt\|EBUSY\|EINPROGRESS' /var/log/kernel.log /var/log/syslog` to identify exploitation attempts
- Step 4: After patching, confirm kernel version with `uname -r` returns 7.0.4 or higher, then verify module reloads cleanly with `sudo modprobe -r pcrypt && sudo modprobe pcrypt`
FAQ
What is CVE-2026-43493?
This vulnerability exists in the Linux kernel's pcrypt (parallel crypto) module, where improper handling of backlogged cryptographic requests can cause EBUSY errors to propagate incorrectly, potentially allowing attackers to trigger a denial of service or information disclosure through crafted cryptographic operations.
Is CVE-2026-43493 being actively exploited?
No, this CVE is not currently listed as actively exploited by CISA, and no public exploits are available. However, the critical CVSS score of 9.8 warrants immediate patching as a precautionary measure.
What versions of Kernel are affected by CVE-2026-43493?
Linux kernel versions 6.19 through 7.0.3 are vulnerable. Version 7.0.4 and later include the necessary fix.
How do I check if my server is vulnerable to CVE-2026-43493?
Run `uname -r` to retrieve your kernel version. If it falls between 6.19 and 7.0.3 inclusive, your system is vulnerable and requires immediate patching.
Does Defensia detect CVE-2026-43493?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-43493 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/1d7f07df450bac3301938fbc4251f2611be4084e
- https://git.kernel.org/stable/c/46271895ddfb1ba41f89f7e0dffbe9c2bcf7380a
- https://git.kernel.org/stable/c/76641449b28979ebd6c02e9598367e119e385236
- https://git.kernel.org/stable/c/77d55bc8675ee851ed639dc9be77325a8024cf67
- https://git.kernel.org/stable/c/915b692e6cb723aac658c25eb82c58fd81235110
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-43493. Free for 1 server.
Get started free