CVE-2026-43493 | crypto: pcrypt - Fix handling of MAY_BACKLOG requests

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.

Published: 2026-05-19 Last update: 2026-06-01 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-43493 is rated Moderate Risk (46/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.06%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-43493

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-21 0.02% 0.06% +0.04%
2 2026-05-19 — 0.02% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-43493

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Weakness enumeration for CVE-2026-43493

GitHub Security Advisory for CVE-2026-43493

GHSA-v9g7-8cgp-9v29 · Severity: critical — In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix...

OS Trackers for CVE-2026-43493

vendor priority summary link
debian not yet assigned CVE-2026-43493 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2026-43493
redhat medium — https://access.redhat.com/security/cve/CVE-2026-43493
suse medium CVE-2026-43493 severity moderate: SUSE including 16 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 54 product×package rows across 14 product lines (SUSE Linux Enterprise High Availability Extension 15 SP7, SUSE Linux Enterprise Live Patching 15 SP7, … (14 product lines)): Known Not Affected 54. https://www.suse.com/security/cve/CVE-2026-43493/
ubuntu medium CVE-2026-43493 medium priority: Ubuntu including 161 source packages (linux, linux-allwinner-5.19, …), 1449 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): DNE 1048, ignored 173, needed 139, released 83, needs-triage 6. https://ubuntu.com/security/CVE-2026-43493

Affected software / configurations for CVE-2026-43493

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-43493

cvelogic Threat Intelligence