CVE-2026-52987 Details
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: avoid double drm_exec_fini() in userq validate When new_addition is true, amdgpu_userq_vm_validate() calls drm_exec_fini(&exec) before iterating over the collected HMM ranges and calling amdgpu_ttm_tt_get_user_pages(). If amdgpu_ttm_tt_get_user_pages() fails in that path, the code jumps to unlock_all and calls drm_exec_fini(&exec) a second time on the same exec object. drm_exec_fini() is not idempotent: it frees exec->objects and may also drop exec->contended and finalize the ww acquire context. Route that error path directly to the range cleanup once exec has already been finalized. Issue found using a prototype static analysis tool and confirmed by code review. (cherry picked from commit 2802952e4a07306da6ebe813ff1acacc5691851a)
A vulnerability in the Linux kernel's AMD GPU driver can lead to improper handling of execution finalization in user queue validation. The issue arises when the 'new_addition' flag is true. The function 'amdgpu_userq_vm_validate()' first calls 'drm_exec_fini(&exec)' to finalize execution before processing collected HMM ranges and invoking 'amdgpu_ttm_tt_get_user_pages()'. If 'amdgpu_ttm_tt_get_user_pages()' fails, the code returns to 'unlock_all' and erroneously calls 'drm_exec_fini(&exec)' a second time on the same execution object. This double finalization is problematic because 'drm_exec_fini()' is not designed to be idempotent; it deallocates 'exec->objects', potentially clears 'exec->contended', and finalizes the write-write acquisition context. The vulnerability has been addressed by directing the error path to clean up the ranges after the execution has been finalized, rather than re-finalizing the execution object.
Users can apply the latest patches from the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://access.redhat.com/security/cve/CVE-2026-52987 | redhat-SADP | Third Party Advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=2492365 | redhat-SADP | Issue TrackingThird Party Advisory |
| https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52987.json | redhat-SADP | Third Party Advisory |
| https://git.kernel.org/stable/c/508babf310365f1107a2e8831c267c292a286818 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c7c3ae7c01e5a0742b93cb9b40800bdd7f811e38 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
| CWE-1341 | Multiple Releases of Same Resource or Handle | redhat-SADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.19, < 7.0.10 7.1 rc1 |
CPE
Remediation
| |
Change History
8 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 10, 2026 | CVE Modified | redhat-SADP |
| Sep 10, 2026 | CVE Modified | kernel.org |
| Aug 3, 2026 | CVE Modified | redhat-SADP |
| Jul 15, 2026 | CVE Modified | redhat-SADP |
| Jul 14, 2026 | Initial Analysis | [email protected] |
| Jun 30, 2026 | CVE Modified | redhat-SADP |
| Jun 28, 2026 | CVE Modified | kernel.org |
| Jun 24, 2026 | New CVE Received | kernel.org |