Skip to main content

Linux Kernel EUVDEUVD-2026-45471

| CVE-2026-63805 HIGH
2026-07-19 Linux GHSA-3m8h-qjhw-m7c5
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.5 MEDIUM

Local low-priv user triggers a kernel oent via AF_ALG (AV:L/AC:L/PR:L/UI:N); demonstrated impact is a crash (A:H) with no evidenced confidentiality or integrity loss (C:N/I:N).

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 15:36 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
7.8 (HIGH)
Patch available
Jul 19, 2026 - 14:17 EUVD
CVE Published
Jul 19, 2026 - 12:02 cve.org
HIGH 7.8
CVE Published
Jul 19, 2026 - 12:02 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

crypto: nx - fix nx_crypto_ctx_exit argument

nx_crypto_ctx_shash_exit calls nx_crypto_ctx_exit with crypto_shash_ctx(...) but crypto_shash_ctx gives a nx_crypto_ctx *, not a crypto_tfm *.

Fix the type in nx_crypto_ctx_exit and drop the bogus crypto_tfm_ctx call.

This fixes the following oops:

BUG: Unable to handle kernel data access at 0xc0403effffffffc8 Faulting instruction address: 0xc000000000396cb4 Oops: Kernel access of bad area, sig: 11 [#15] Call Trace: nx_crypto_ctx_shash_exit+0x24/0x60 crypto_shash_exit_tfm+0x28/0x40 crypto_destroy_tfm+0x98/0x140 crypto_exit_ahash_using_shash+0x20/0x40 crypto_destroy_tfm+0x98/0x140 hash_release+0x1c/0x30 alg_sock_destruct+0x38/0x60 __sk_destruct+0x48/0x2b0 af_alg_release+0x58/0xb0 __sock_release+0x68/0x150 sock_close+0x20/0x40 __fput+0x110/0x3a0 sys_close+0x48/0xa0 system_call_exception+0x140/0x2d0 system_call_common+0xf4/0x258

.. which came from hardlink(1) opportunistically using AF_ALG.

The same problem exists with nx_crypto_ctx_skcipher_exit getting a context it wasn't expecting, but apparently nobody hit that for years.

AnalysisAI

A local privilege-context memory corruption in the Linux kernel's IBM PowerPC 'nx' hardware crypto driver (drivers/crypto/nx) causes a kernel oops when userspace uses the AF_ALG socket interface for shash hashing. nx_crypto_ctx_shash_exit passed a wrong pointer type (an nx_crypto_ctx* treated as a crypto_tfm*) into nx_crypto_ctx_exit, producing a bad-address kernel access (observed at 0xc0403effffffffc8) during teardown, reachable by any local user - e.g. hardlink(1) opportunistically selecting AF_ALG. No public exploit is identified at time of analysis; EPSS is low (0.17%) and this is not on CISA KEV, so real-world risk is a local denial-of-service (kernel crash) on affected NX-capable POWER systems rather than confirmed code execution.

Technical ContextAI

The affected component is the IBM Power7+/POWER 'Nest Accelerator' (NX) cryptographic coprocessor driver in the Linux kernel (drivers/crypto/nx), which registers shash and skcipher transforms with the kernel Crypto API. The Crypto API exposes algorithms to userspace through AF_ALG sockets, and here crypto_exit_ahash_using_shash wraps the NX shash. The bug is a pointer-type confusion: crypto_shash_ctx() returns the driver's private nx_crypto_ctx*, but the exit path treated it as a crypto_tfm* and additionally called crypto_tfm_ctx() on it, dereferencing an invalid offset and faulting the kernel. Root cause is a type/pointer-arithmetic error in cleanup code (CWE is listed as N/A in the input, but this maps conceptually to CWE-843 type confusion / CWE-763 incorrect pointer arithmetic on free). The commit note observes the sibling nx_crypto_ctx_skcipher_exit path has the same latent defect that simply went untriggered for years. CPE data only identifies cpe:2.3:a:linux:linux, i.e. the generic Linux kernel, without pinning the exact NX-driver-affected build.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 6.18.38 or 7.1.3, or mainline 7.2-rc1 and later - which correct nx_crypto_ctx_exit to take the proper nx_crypto_ctx* and drop the erroneous crypto_tfm_ctx call. Apply the corresponding distribution kernel update that backports commits 4e67f504ee9ded15e256b64f4fde150e917381d7 / 8d8507a457667f23477a15496b91908a5b5b7cf3 / 833033e6e55acf11304ff7bbbdf18351d139c281 (git.kernel.org/stable). If immediate patching is not possible, the practical compensating control is to remove exposure of the NX shash path: blacklist/unload the nx-crypto module (e.g. modprobe nx-crypto is not loaded) on affected POWER systems so the kernel falls back to software crypto - trade-off is loss of hardware crypto acceleration and possible performance impact. Alternatively, restrict access to the AF_ALG interface, since that is the trigger surface: disable CONFIG_CRYPTO_USER_API_HASH / prevent AF_ALG socket use where feasible, or apply seccomp/LSM policy blocking AF_ALG for untrusted local processes - trade-off is breaking applications (like hardlink(1) or others) that opportunistically use AF_ALG. These controls only apply to PowerPC hosts with the NX accelerator; non-PPC systems are unaffected.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-45471 vulnerability details – vuln.today

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