CVE-2026-43493

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-19. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 19, 2026

Last Modified

October 19, 2026

Advisory Details (9)

Auto-updated Oct 20, 2026
Patch available.
Web page

crypto: pcrypt - Fix handling of MAY_BACKLOG requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eb34e243df57e32f4c08fa191f3602ea19076276
Web page

crypto: pcrypt - Fix handling of MAY_BACKLOG requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ae7e95638d956d556d74b9abb9e780d3bd3dcd9e
Web page

crypto: pcrypt - Fix handling of MAY_BACKLOG requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f1cbca178c03188e201ed175251372149bb25f2
Web page

crypto: pcrypt - Fix handling of MAY_BACKLOG requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/915b692e6cb723aac658c25eb82c58fd81235110
Web page

crypto: pcrypt - Fix handling of MAY_BACKLOG requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/77d55bc8675ee851ed639dc9be77325a8024cf67
Web page

crypto: pcrypt - Fix handling of MAY_BACKLOG requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76641449b28979ebd6c02e9598367e119e385236
Web page

crypto: pcrypt - Fix handling of MAY_BACKLOG requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46271895ddfb1ba41f89f7e0dffbe9c2bcf7380a
Web page

crypto: pcrypt - Fix handling of MAY_BACKLOG requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d7f07df450bac3301938fbc4251f2611be4084e

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-raspi-nolpae (5.15.0.1105.103) @ jammy2026-10-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1074 (5.15.0-1074.78) @ jammy2026-10-23ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1021.21) @ questing2026-10-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1106.112~20.04.1) @ focal2026-10-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-gcp-fips-5.4 (5.4.0.1165.107) @ focal2026-10-23ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1161.171~18.04.1) @ bionic2026-10-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1116.101) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-23ubuntu
ubuntulinux-tools-fips (4.4.0.1127.129) @ xenial2026-10-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-10-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-10-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.185.166) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-10-23ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-10-23ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.254.238) @ bionic2026-10-23ubuntu
redhatkernel-0:4.18.0-372.223.1.el8_62026-10-19redhat
redhatkernel-0:6.12.0-55.108.1.el10_02026-10-05redhat
redhatkernel-0:5.14.0-570.146.1.el9_62026-10-01redhat
redhatkernel-0:5.14.0-687.46.1.el9_82026-09-10redhat
redhatkernel-0:4.18.0-553.160.1.el8_102026-09-09redhat
redhatkernel-rt-0:4.18.0-553.160.1.rt7.501.el8_102026-09-08redhat
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
linuxKernel @ 5.10.258 (fixes >=2.6.34)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)
  • every version up to 6.12.86-1: fixed in 6.12.86-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (135 versions)
  • every version up to 7.0.4-1: fixed in 7.0.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 29× in last 7d / 76× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 497 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 397 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-10-23 03:25 UTCEG score recompute
  3. 2026-10-23 03:25 UTCVendor advisory
  4. 2026-10-23 03:24 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  6. 2026-10-22 01:06 UTCEG score recompute
  7. 2026-10-22 01:06 UTCVendor advisory
  8. 2026-10-22 01:05 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-20 22:46 UTCEG score recompute
  11. 2026-10-20 22:46 UTCVendor advisory
  12. 2026-10-20 22:45 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-19 20:27 UTCEG score recompute
  15. 2026-10-19 20:27 UTCVendor advisory
  16. 2026-10-19 20:26 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-19 19:31 UTCEG score recompute
  18. 2026-10-19 19:31 UTCVendor advisory
  19. 2026-10-19 19:30 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-10-18 21:15 UTCEG score recompute
  22. 2026-10-18 21:15 UTCVendor advisory
  23. 2026-10-18 21:15 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-10-18 03:40 UTCEG score recompute
Show 75 more
  1. 2026-10-17 18:57 UTCEG score recompute
  2. 2026-10-17 18:57 UTCVendor advisory
  3. 2026-10-17 18:56 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-16 16:36 UTCEG score recompute
  7. 2026-10-16 16:36 UTCVendor advisory
  8. 2026-10-16 16:36 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-16 16:30 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-16 15:30 UTCEG score recompute
  11. 2026-10-16 15:30 UTCVendor advisory
  12. 2026-10-16 15:30 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-16 04:48 UTCEG score recompute
  14. 2026-10-16 04:48 UTCVendor advisory
  15. 2026-10-16 04:48 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-15 02:30 UTCEG score recompute
  18. 2026-10-15 02:30 UTCVendor advisory
  19. 2026-10-15 02:29 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-15 01:33 UTCEG score recompute
  21. 2026-10-15 01:33 UTCVendor advisory
  22. 2026-10-15 01:32 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-10-14 12:33 UTCEG score recompute
  25. 2026-10-14 12:33 UTCVendor advisory
  26. 2026-10-14 12:33 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  28. 2026-10-13 10:13 UTCEG score recompute
  29. 2026-10-13 10:13 UTCVendor advisory
  30. 2026-10-13 10:12 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  32. 2026-10-12 16:06 UTCEG score recompute
  33. 2026-10-12 07:54 UTCVendor advisory
  34. 2026-10-12 07:53 UTCGHSA enrichmentGHSA-v9g7-8cgp-9v29 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-11 19:48 UTCEG score recompute
  36. 2026-10-11 17:02 UTCEG score recompute
  37. 2026-10-11 14:28 UTCEG score recompute
  38. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  39. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  40. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  41. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  42. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  43. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  44. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  45. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  46. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  47. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  48. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  49. 2026-09-30 13:32 UTCOSV refresh
  50. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  51. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  52. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  53. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  54. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  55. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  56. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  57. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  58. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  59. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  60. 2026-09-11 20:23 UTCOSV refresh
  61. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  62. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  63. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  64. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  65. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  66. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  67. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  68. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  69. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  70. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  71. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  72. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  73. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  74. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  75. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.6% · 43rd percentile

Frequently asked(5)

What is CVE-2026-43493?
CVE-2026-43493 is a critical-severity vulnerability; its CVE record was published on May 19, 2026. 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.
When was the CVE record for CVE-2026-43493 published?
The CVE record for CVE-2026-43493 was published on May 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-43493 actively exploited?
CVE-2026-43493 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43493?
CVE-2026-43493 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-43493?
A fix for CVE-2026-43493 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43493 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43493

Explore →

Is Your Infrastructure Affected by CVE-2026-43493?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.