In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix lock leak on ENOMEM in AMDGPU_GEM_OP_GET_MAPPING_INFO The… (CVE-2026-63880)
A vulnerability in the Linux kernel's AMDGPU driver causes a lock leak on memory allocation failure in the AMDGPU_GEM_OP_GET_MAPPING_INFO ioctl call. This leak results in a denial of service condition where subsequent GPU operations block indefinitely, potentially leaving processes in an uninterruptible state until reboot. The issue affects unprivileged local users with access to /dev/dri/renderD* devices.
AI Analysis
Technical Summary
The vulnerability occurs in the drm/amdgpu driver within the Linux kernel, specifically in the AMDGPU_GEM_OP_GET_MAPPING_INFO branch of the amdgpu_gem_op_ioctl() function. When kvcalloc() fails with -ENOMEM, the code path incorrectly bypasses the cleanup label 'out_exec', causing a lock leak of three resources including the per-process VM root page directory dma_resv lock. This leaked lock blocks further operations on the same VM, leading to a local denial of service for any process with access to the GPU rendering device. The issue was reproduced on Linux kernel 7.0.0-10 with Ryzen 7 5700U / Radeon Vega hardware. The fix involves routing the failure path through the cleanup label to properly release all held locks and references.
Potential Impact
An unprivileged local user with access to /dev/dri/renderD* can trigger a denial of service against their own GPU context by causing the lock leak. Subsequent GPU operations block indefinitely, and the affected process may enter an uninterruptible sleep state (D state) that is not resolved even by SIGKILL, requiring a system reboot to recover. This impacts system stability and availability of GPU resources for the affected user.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to route the failure path through the proper cleanup code, preventing the lock leak. Users should update their Linux kernel to a version that includes this patch. Since this is not a cloud service, remediation depends on applying the updated kernel. Patch status is not explicitly stated in the input data; users should consult the official Linux kernel advisories or distribution updates for the fixed version.
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix lock leak on ENOMEM in AMDGPU_GEM_OP_GET_MAPPING_INFO The… (CVE-2026-63880)
Description
A vulnerability in the Linux kernel's AMDGPU driver causes a lock leak on memory allocation failure in the AMDGPU_GEM_OP_GET_MAPPING_INFO ioctl call. This leak results in a denial of service condition where subsequent GPU operations block indefinitely, potentially leaving processes in an uninterruptible state until reboot. The issue affects unprivileged local users with access to /dev/dri/renderD* devices.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability occurs in the drm/amdgpu driver within the Linux kernel, specifically in the AMDGPU_GEM_OP_GET_MAPPING_INFO branch of the amdgpu_gem_op_ioctl() function. When kvcalloc() fails with -ENOMEM, the code path incorrectly bypasses the cleanup label 'out_exec', causing a lock leak of three resources including the per-process VM root page directory dma_resv lock. This leaked lock blocks further operations on the same VM, leading to a local denial of service for any process with access to the GPU rendering device. The issue was reproduced on Linux kernel 7.0.0-10 with Ryzen 7 5700U / Radeon Vega hardware. The fix involves routing the failure path through the cleanup label to properly release all held locks and references.
Potential Impact
An unprivileged local user with access to /dev/dri/renderD* can trigger a denial of service against their own GPU context by causing the lock leak. Subsequent GPU operations block indefinitely, and the affected process may enter an uninterruptible sleep state (D state) that is not resolved even by SIGKILL, requiring a system reboot to recover. This impacts system stability and availability of GPU resources for the affected user.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to route the failure path through the proper cleanup code, preventing the lock leak. Users should update their Linux kernel to a version that includes this patch. Since this is not a cloud service, remediation depends on applying the updated kernel. Patch status is not explicitly stated in the input data; users should consult the official Linux kernel advisories or distribution updates for the fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-5vfp-rcpc-cr39
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63880"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ac2a4a8d59891302de
Added to database: 07/19/2026, 19:38:20 UTC
Last enriched: 07/19/2026, 20:13:22 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.