Skip to content
Cryptography

CVE-2026-31739

8.8
High
EPSS 0.41%Patch availableMay 3, 2026

Linux Tegra crypto driver fix; CRYPTO_ALG_ASYNC flag added to prevent crashes.

common questions

Is CVE-2026-31739 being exploited?

Not confirmed. CVE-2026-31739 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.

How severe is CVE-2026-31739?

CVE-2026-31739 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-31739?

Yes. A fix has been recorded for CVE-2026-31739. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-31739 affect?

CVE-2026-31739 affects Linux kernel (TEGRA crypto driver). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-31739?

Patch kernel with Tegra crypto fix.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (TEGRA crypto driver)
impact

Local crash/DoS via kernel crypto API when sync requests are used.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and < bdbf027a4504b4a86740de6beb6d18a957331839
  • affected>= 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and < 3aea268b6d5cde3b087df9eeecc3bc620aa09513
  • affected>= 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and < 429d05565eb19ee545d8a8395991372adbe4daf3
  • affected>= 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and < 4b56770d345524fc2acc143a2b85539cf7d74bc1
  • affected6.10
vendor says fixed in< 6.10, >= 6.12.81 and <= 6.12.*, >= 6.18.22 and <= 6.18.*, >= 6.19.12 and <= 6.19.*, >= 7.0 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free