# crypto: tegra - Add missing CRYPTO_ALG_ASYNC

CVE record · `CVE-2026-31739`

- **Identifiers:** `CVE-2026-31739`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html)
- **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2026, 14:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 to before bdbf027a4504b4a86740de6beb6d18a957331839` (git)
  - affected: `0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 to before 3aea268b6d5cde3b087df9eeecc3bc620aa09513` (git)
  - affected: `0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 to before 429d05565eb19ee545d8a8395991372adbe4daf3` (git)
  - affected: `0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 to before 4b56770d345524fc2acc143a2b85539cf7d74bc1` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.10`
  - unaffected: `before 6.10` (semver)
  - unaffected: `6.12.81 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.22 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.12 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0042, the 36th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2026, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-31739)

## Sources

- [CVE List: CVE-2026-31739](https://www.cve.org/CVERecord?id=CVE-2026-31739)
- [NVD: CVE-2026-31739](https://nvd.nist.gov/vuln/detail/CVE-2026-31739)

### References from the CNA

- <https://git.kernel.org/stable/c/bdbf027a4504b4a86740de6beb6d18a957331839>
- <https://git.kernel.org/stable/c/3aea268b6d5cde3b087df9eeecc3bc620aa09513>
- <https://git.kernel.org/stable/c/429d05565eb19ee545d8a8395991372adbe4daf3>
- <https://git.kernel.org/stable/c/4b56770d345524fc2acc143a2b85539cf7d74bc1>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-31739>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-31739/>. Everything for agents: <https://agentprime.io/llms.txt>.
