Skip to main content

Linux Kernel CVE-2026-31739

| EUVDEUVD-2026-26552 HIGH
Reachable Assertion (CWE-617)
2026-05-01 Linux
Red Hat Suse Denial Of Service Linux
8.8
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
SUSE
HIGH
qualitative
Red Hat
5.5 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

7
Analysis Generated
May 03, 2026 - 07:28 vuln.today
CVSS changed
May 03, 2026 - 07:22 NVD
8.8 (HIGH)
Patch released
May 03, 2026 - 07:16 nvd
Patch available
Patch available
May 01, 2026 - 16:02 EUVD
EUVD ID Assigned
May 01, 2026 - 15:00 euvd
EUVD-2026-26552
Analysis Generated
May 01, 2026 - 15:00 vuln.today
CVE Published
May 01, 2026 - 14:14 nvd
HIGH 8.8

DescriptionCVE.org

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.

AnalysisAI

Missing CRYPTO_ALG_ASYNC flag in Linux kernel's Tegra crypto driver causes the crypto API to incorrectly select asynchronous algorithms for synchronous-only requests, resulting in system crashes. This affects Tegra-based Linux systems (typically NVIDIA Jetson devices) running kernel versions 6.10 through early 7.0 development branches. Vendor patches are available across stable branches (6.12.81, 6.18.22, 6.19.12, 7.0). EPSS score of 0.02% (5th percentile) indicates minimal observed exploitation probability, and no active exploitation or public POC has been identified. The CVSS vector (AV:N/AC:L/PR:L/UI:N) suggests network-based exploitation requiring authenticated access, though this conflicts with the technical nature of a local driver configuration bug.

Technical ContextAI

The Tegra crypto driver provides hardware-accelerated cryptographic operations for NVIDIA Tegra SoCs (commonly used in Jetson embedded platforms). The Linux kernel crypto API differentiates between synchronous algorithms (blocking, immediate results) and asynchronous algorithms (non-blocking, callback-based). Algorithm registration requires the CRYPTO_ALG_ASYNC flag to identify async implementations. The Tegra driver incorrectly omitted this flag during registration, causing the crypto subsystem's algorithm selection logic to treat async algorithms as synchronous. When kernel code or userspace applications requested synchronous-only crypto operations (common for inline encryption, device-mapper, IPsec fastpath), the API would select the Tegra async algorithms, leading to incorrect control flow, null pointer dereferences, or use-after-free conditions when callbacks fired unexpectedly. The patch adds CRYPTO_ALG_ASYNC and removes deprecated CRYPTO_ALG_TYPE_* flags that modern registration functions override. Affects kernel versions containing commit 0880bb3b00c8 through patches applied in stable branches.

RemediationAI

Apply vendor patches immediately for Tegra-based Linux systems. Upgrade to patched stable kernel versions: 6.12.81 or later in the 6.12.x series, 6.18.22+ in 6.18.x, 6.19.12+ in 6.19.x, or 7.0+ for development branches. Patches available at https://git.kernel.org/stable/c/bdbf027a4504b4a86740de6beb6d18a957331839 (6.12 branch), https://git.kernel.org/stable/c/3aea268b6d5cde3b087df9eeecc3bc620aa09513 (6.18), https://git.kernel.org/stable/c/429d05565eb19ee545d8a8395991372adbe4daf3 (6.19), and https://git.kernel.org/stable/c/4b56770d345524fc2acc143a2b85539cf7d74bc1 (mainline 7.0). If immediate patching is not feasible, disable Tegra crypto hardware acceleration by blacklisting the tegra_se kernel module (modprobe.blacklist=tegra_se), forcing fallback to software crypto implementations. This workaround eliminates crash risk but reduces cryptographic performance on Tegra hardware by 40-80% depending on workload. For embedded/IoT devices with immutable firmware, restrict access to crypto API consumers (disable unnecessary VPN/IPsec daemons, limit dm-crypt usage) until vendor firmware updates incorporating these kernel patches become available.

Same weakness CWE-617 – Reachable Assertion

View all
CVE-2016-8864 HIGH
7.5
CVE-2020-12417 HIGH POC
8.8
CVE-2020-6623 HIGH POC
8.8
CVE-2020-6619 HIGH POC
8.8
CVE-2020-6617 HIGH POC
8.8
CVE-2023-37023 HIGH POC
8.6
CVE-2023-37021 HIGH POC
8.6
CVE-2023-37020 HIGH POC
8.6

Same technique Denial Of Service

View all
CVE-2015-5119 CRITICAL POC
9.8
CVE-2011-2462 CRITICAL POC
9.8
CVE-2011-0611 HIGH POC
8.8
CVE-2012-1889 HIGH POC
8.8
CVE-2012-0507 CRITICAL POC
9.8
CVE-2014-1761 HIGH POC
7.8
CVE-2015-5122 CRITICAL POC
9.8
CVE-2011-0609 HIGH POC
7.8

Vendor StatusVendor

SUSE

Severity: High
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Share

CVE-2026-31739 vulnerability details – vuln.today
Back

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy