Skip to main content
VulnerabilityPublished Updated

CVE-2026-31739: Linux kernel · crypto: tegra – Add missing CRYPTO_ALG_ASYNC

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in bdbf027a4504b4a86740de6beb6d18a957331839 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in bdbf027a4504b4a86740de6beb6d18a957331839, 429d05565eb19ee545d8a8395991372adbe4daf3, 4b56770d345524fc2acc143a2b85539cf7d74bc1 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to bdbf027a4504b4a86740de6beb6d18a957331839, 429d05565eb19ee545d8a8395991372adbe4daf3, 4b56770d345524fc2acc143a2b85539cf7d74bc1 or 3aea268b6d5cde3b087df9eeecc3bc620aa09513.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0, < bdbf027a4504b4a86740de6beb6d18a957331839
Fixed in
  • bdbf027a4504b4a86740de6beb6d18a957331839
LinuxLinuxAffected
  • ≥ 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0, < 429d05565eb19ee545d8a8395991372adbe4daf3
Fixed in
  • 429d05565eb19ee545d8a8395991372adbe4daf3
LinuxLinuxAffected
  • ≥ 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0, < 4b56770d345524fc2acc143a2b85539cf7d74bc1
Fixed in
  • 4b56770d345524fc2acc143a2b85539cf7d74bc1
LinuxLinuxAffected
  • ≥ 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0, < 3aea268b6d5cde3b087df9eeecc3bc620aa09513
Fixed in
  • 3aea268b6d5cde3b087df9eeecc3bc620aa09513
LinuxLinuxAffected
  • =6.10
Fixed in–

Description

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.

References

Community reviews

Loading reviews…