CVE-2026-31739

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

crypto: tegra - Add missing CRYPTO_ALG_ASYNC

The tegra crypto driver failed to set the CRYPTO_ALG_ASYNC on its asynchronous algorithms, causing the crypto API to select them for users that request only synchronous algorithms. This causes crashes (at least). Fix this by adding the flag like what the other drivers do. Also remove the unnecessary CRYPTO_ALG_TYPE_* flags, since those just get ignored and overridden by the registration function anyway.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
33.9%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (4)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

crypto: tegra - Add missing CRYPTO_ALG_ASYNC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bdbf027a4504b4a86740de6beb6d18a957331839
generic

crypto: tegra - Add missing CRYPTO_ALG_ASYNC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4b56770d345524fc2acc143a2b85539cf7d74bc1
generic

crypto: tegra - Add missing CRYPTO_ALG_ASYNC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/429d05565eb19ee545d8a8395991372adbe4daf3
generic

crypto: tegra - Add missing CRYPTO_ALG_ASYNC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3aea268b6d5cde3b087df9eeecc3bc620aa09513

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.81—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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 135 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31739?
CVE-2026-31739 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - Add missing CRYPTOALGASYNC The tegra crypto driver failed to set the CRYPTOALGASYNC on its asynchronous algorithms, causing the crypto API to select them for users that request only synchronous algorithms. This…
When was CVE-2026-31739 disclosed?
CVE-2026-31739 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31739 actively exploited?
CVE-2026-31739 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31739?
CVE-2026-31739 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-31739?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31739, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-31739

Explore →

Is Your Infrastructure Affected by CVE-2026-31739?

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

Start Free Scan →Browse All CVEs