Skip to main content

Linux Kernel CVE-2026-72449

| EUVDEUVD-2026-59348 HIGH
2026-08-15 Linux GHSA-xgpc-q5wr-q4v5
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.8 HIGH

Local vector confirmed; PR:L because render group membership is a low-privilege OS-level permission, not root; AC:L because no race or grooming required beyond double-ioctl.

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:H/SI:H/SA:H
SUSE
HIGH
qualitative
Red Hat
7.0 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
Aug 17, 2026 - 09:28 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 - 05:56 cve.org
HIGH 7.8
CVE Published
Aug 15, 2026 - 05:56 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm

The cleanup tail of kfd_criu_resume_svm() walks svms->criu_svm_metadata_list and kfree()s each struct criu_svm_metadata without removing it from the list. The list head is left pointing at freed kmalloc-96 objects.

A second AMDKFD_IOC_CRIU_OP from the same process re-enters: list_empty() reads the dangling ->next (use-after-free), the loop walks freed entries, and each is kfree()'d again (double-free). This is reachable by an unprivileged render-group user via /dev/kfd with no capabilities required.

Add list_del() before the kfree() so the list is properly emptied. The list_for_each_entry_safe() iterator already caches the next pointer, so unlinking during the walk is safe.

(cherry picked from commit 6322d278a298e2c1430b9d2697743d3a04b788b1)

AnalysisAI

Use-after-free and double-free memory corruption in the Linux kernel's amdkfd DRM subsystem exposes systems with AMD GPUs to local privilege escalation. The flaw resides in kfd_criu_resume_svm(), where cleanup logic frees struct criu_svm_metadata objects without unlinking them from the list, leaving dangling pointers; a second AMDKFD_IOC_CRIU_OP ioctl from the same process then walks and double-frees those freed objects. Exploitation is reachable by any unprivileged user with render group membership via /dev/kfd - no additional capabilities required. No public exploit identified at time of analysis, and EPSS sits at 0.21% (12th percentile), consistent with a local-access kernel bug without weaponized tooling.

Technical ContextAI

The affected component is the AMD GPU Kernel Fusion Driver (amdkfd), part of the Linux DRM (Direct Rendering Manager) subsystem, responsible for managing GPU compute workloads including Shared Virtual Memory (SVM). The CRIU (Checkpoint/Restore In Userspace) resume path in kfd_criu_resume_svm() iterates svms->criu_svm_metadata_list using list_for_each_entry_safe() and calls kfree() on each struct criu_svm_metadata without first invoking list_del(). This leaves the list head pointing at freed kmalloc-96 slab objects. When the same process re-enters via a second AMDKFD_IOC_CRIU_OP ioctl, list_empty() dereferences the stale ->next pointer (CWE-416, use-after-free), the loop traverses already-freed memory, and each entry is kfree()'d again (CWE-415, double-free). The root cause is a classic linked-list cleanup antipattern: freeing members without delinking them. The fix is a single list_del() call before each kfree(), which is safe because list_for_each_entry_safe() caches the next pointer before the body executes. Affected CPE is cpe:2.3:a:linux:linux from the introduction commit 2a909ae718715b3bac75d945e38dc0a5e4a0f1ba through multiple stable branches.

RemediationAI

Upgrade to a patched stable kernel version: 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, or mainline 7.2-rc1. Commits are available via https://git.kernel.org/stable/c/ at the references listed in this CVE. Distributions (Debian, Ubuntu, RHEL, SUSE, etc.) will ship these as kernel security updates; check your distribution's security advisories for packaged versions. If immediate patching is not feasible, the following compensating controls can reduce exposure: restrict /dev/kfd permissions so that only trusted users or service accounts belong to the render group (e.g., remove non-essential users from the render group with gpasswd -d <user> render), which eliminates the attack surface for untrusted local users. Alternatively, if AMD GPU CRIU checkpoint/restore functionality is not required, consider blocking AMDKFD_IOC_CRIU_OP via a seccomp policy or BPF LSM rule targeting the ioctl command code - this prevents the vulnerable code path from being reached without disabling the broader amdkfd driver. Note that restricting render group membership may impact GPU-accelerated workloads for affected users. No confidentiality workaround exists for systems where render group access is legitimately granted to untrusted users; patching is the only complete fix.

Vendor StatusVendor

SUSE

Severity: Important
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-72449 vulnerability details – vuln.today

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