Bug 2516740 (CVE-2026-72449)

Summary: CVE-2026-72449 kernel: drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's `drm/amdkfd` component. An unprivileged render-group user can exploit this vulnerability via `/dev/kfd` by repeatedly calling `AMDKFD_IOC_CRIU_OP`. This leads to a use-after-free and double-free condition due to improper list handling during cleanup. Successful exploitation can result in memory corruption, potentially allowing for arbitrary code execution or a denial of service.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-15 06:28:36 UTC 
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)
Comment 1 Keith Grant 2026-08-19 17:02:31 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026081531-CVE-2026-72449-c109@gregkh/T