Skip to main content

Linux Kernel EUVDEUVD-2026-45489

| CVE-2026-63823 HIGH
2026-07-19 Linux GHSA-hhf9-cxvj-3mv7
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
7.0 HIGH

Local unprivileged access (AV:L/PR:L) via keyctl, but reliable triggering needs winning a page-fault race window so AC:H; kernel UAF yields full C/I/A impact.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
7.0 MEDIUM
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:43 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:

keys: Pin request_key_auth payload in instantiate paths

A: request_key() B: KEYCTL_INSTANTIATE_IOV ==== =====

create auth key store rka in auth key wait for helper get auth key load rka from auth key copy user payload sleep on #PF

helper completed detach and free rka destroy auth key wake up use rka->target_key USE-AFTER-FREE

Give request_key_auth payloads a refcount. Take a payload reference while authkey->sem stabilizes the payload and revocation state. Hold that reference across the instantiate and reject paths. Drop the auth key owning reference from revoke and destroy.

[jarkko: Replaced the first two paragraphs of text with an actual concurrency scenario.]

AnalysisAI

Local privilege escalation via a use-after-free in the Linux kernel's key management (keys) subsystem allows an unprivileged local user to corrupt kernel memory by racing a request_key() helper against KEYCTL_INSTANTIATE_IOV. The request_key_auth payload (rka) could be detached and freed by the key-request helper's completion path while a concurrent instantiate/reject operation was still dereferencing rka->target_key, yielding a UAF (CWE-416). It is not in CISA KEV and no public exploit was identified at time of analysis; EPSS is low at 0.17% (6th percentile), and a vendor patch is available across multiple stable branches.

Technical ContextAI

The flaw lives in the Linux kernel keyrings/keyctl subsystem, specifically the request_key_auth key type used to authorize a userspace upcall (request-key helper) to instantiate a pending key. When request_key() creates an authorization ('auth') key, it stores a request_key_auth payload (rka) that references the target key being instantiated. A second thread using KEYCTL_INSTANTIATE_IOV loads that rka and copies a user-supplied payload; if it sleeps on a page fault while copying, the helper-completion path on the first thread can revoke/destroy the auth key and free the rka out from under the second thread, which then uses the dangling rka->target_key pointer. This is a classic use-after-free (CWE-416) rooted in a missing lifetime/refcount guarantee on the payload; the fix adds a refcount to request_key_auth payloads, takes a reference under authkey->sem across the instantiate and reject paths, and moves the owning-reference drop into the revoke/destroy paths. The CPE data identifies the affected product as the Linux kernel (cpe:2.3:a:linux:linux:*), and the CWE was reported as N/A by the source but maps cleanly to use-after-free.

RemediationAI

Apply the vendor-released kernel patch: upgrade to a fixed stable release for your branch - 5.10.260, 5.15.211, 6.1.177, 6.6.144, 6.12.95, 6.18.38, 7.1.3, or mainline 7.2-rc1 or later - or your distribution's equivalent backport, then reboot (or apply live-patch if your vendor provides one). The upstream fixes are available as the kernel.org stable commits (https://git.kernel.org/stable/c/d8274181b0f28d450b42489723a5ba81042158d7 and the related commits listed in the references). Because the bug is in the core keyrings/request-key path, there is no clean feature toggle to disable it; a partial compensating control is to restrict who can invoke key upcalls by limiting access to keyctl/request_key from untrusted local accounts and containers (e.g., via seccomp filters that block the keyctl/add_key/request_key syscalls for sandboxed workloads, or by not granting shell access to untrusted users) - the trade-off is that applications relying on kernel key management (Kerberos/GSSAPI, dm-crypt/ecryptfs helpers, NFS, container secret handling) may break. Prioritize patching over the seccomp workaround where those subsystems are in use.

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-45489 vulnerability details – vuln.today

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