CVE-2026-31739: Linux kernel · crypto: tegra – Add missing CRYPTO_ALG_ASYNC
Affects Linux kernelSource CVE Database V5
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
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| 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
- git.kernel.org/stable/c/bdbf027a4504b4a86740de6beb6d18a957331839 (opens in a new tab)
- git.kernel.org/stable/c/3aea268b6d5cde3b087df9eeecc3bc620aa09513 (opens in a new tab)
- git.kernel.org/stable/c/429d05565eb19ee545d8a8395991372adbe4daf3 (opens in a new tab)
- git.kernel.org/stable/c/4b56770d345524fc2acc143a2b85539cf7d74bc1 (opens in a new tab)