Skip to main content

Linux Kernel CVE-2026-72090

| EUVDEUVD-2026-59048 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-qqcm-w5c8-f3qv
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.8 HIGH

Local low-privileged access to the DRM device node is required to invoke the ioctl; the client confusion yields cross-process hardware context access with full CIA impact.

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

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

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
Aug 17, 2026 - 06:45 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:21 cve.org
HIGH 7.8
CVE Published
Aug 15, 2026 - 06:21 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

accel/amdxdna: Use caller client for debug BO sync

amdxdna_drm_sync_bo_ioctl() looks up args->handle in the ioctl caller's drm_file. For SYNC_DIRECT_FROM_DEVICE, it then calls amdxdna_hwctx_sync_debug_bo(), but passes abo->client.

amdxdna_hwctx_sync_debug_bo() uses the passed client both as the handle namespace for debug_bo_hdl and as the owner of the hardware context xarray. Those must match the file that supplied args->handle. The BO's stored client pointer is object state, not the ioctl context.

Pass filp->driver_priv instead, matching the original handle lookup.

AnalysisAI

Client pointer confusion in the Linux kernel's amdxdna DRM accelerator driver allows a local low-privileged user to trigger cross-process access to another process's hardware context and debug buffer objects via a misrouted SYNC_DIRECT_FROM_DEVICE ioctl. Systems running AMD XDNA NPU hardware (such as AMD Ryzen AI series processors) with the amdxdna kernel module loaded are affected across kernel versions from the driver's introduction up to the patched releases in 7.1.5 and 7.2-rc1. No public exploit exists and the EPSS score of 0.20% (10th percentile) reflects low near-term exploitation probability, though the CVSS 7.8 score correctly captures the high CIA impact should exploitation succeed.

Technical ContextAI

The amdxdna driver implements DRM (Direct Rendering Manager) infrastructure for AMD's XDNA neural processing unit accelerators, including those embedded in AMD Ryzen AI series SoCs. DRM Buffer Objects (BOs) are reference-counted memory allocations tracked per open DRM file handle - each handle exists within the namespace of the owning drm_file. The vulnerability lies in amdxdna_drm_sync_bo_ioctl(): when handling a SYNC_DIRECT_FROM_DEVICE request, it correctly resolves args->handle against the ioctl caller's file (filp->driver_priv), but then calls amdxdna_hwctx_sync_debug_bo() passing abo->client - the client pointer baked into the buffer object at allocation time - rather than the caller's live file context. Since amdxdna_hwctx_sync_debug_bo() uses that client pointer both as the handle namespace for debug_bo_hdl and to look up hardware contexts in an xarray, a mismatch between the two clients creates a situation where handle resolution and context lookup occur against different security domains. The root cause class, while formally unassigned (CWE: N/A in the advisory), is consistent with CWE-706 (Use of Incorrectly-Resolved Name or Reference) - where object-state context substitutes for ioctl-caller context in a privileged operation.

RemediationAI

The primary fix is upgrading to Linux kernel 7.1.5 (stable) or 7.2-rc1 (mainline), which incorporate the one-line caller-context correction. The exact upstream patch commits are available at https://git.kernel.org/stable/c/7caf2a2351d4053075670ff3e26a6815da0a9e1e and https://git.kernel.org/stable/c/216e43d93dd49ec253052741aa476e51a8c54cd8; distribution maintainers should be consulted for backported stable packages. Where patching is not immediately feasible, restricting access to the DRM accelerator device node (for example, chmod o-rw /dev/accel/accel* and enforcing this via udev rules) prevents unprivileged local users from invoking the vulnerable ioctl - the trade-off is that non-privileged applications lose NPU access entirely. A more disruptive but complete compensating control is blacklisting the amdxdna module by adding 'blacklist amdxdna' to /etc/modprobe.d/amdxdna-blacklist.conf and rebooting, which eliminates the attack surface at the cost of all XDNA NPU functionality. Neither workaround substitutes for applying the vendor patch.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-72090 vulnerability details – vuln.today

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