Bug 2513321 (CVE-2026-68232)

Summary: CVE-2026-68232 kernel: drm/gpusvm: Fix MM reference leak in drm_gpusvm_range_evict
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: akhatavk, aos-team-art-private, asdas, dpaolell, jdelft, jupierce, lgarciaa, mbiarnes, ppalepu, ppostler, prdhamdh, rhel-process-autobot, sghai, sidsharm, suppawar, vlaad, 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/gpusvm` component. When the `kvmalloc_array()` function fails within `drm_gpusvm_range_evict()`, a previously acquired memory management (MM) reference is not properly released. This oversight leads to a reference leak, which can result in resource exhaustion and a Denial of Service (DoS) condition for the system.
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-10 12:30:52 UTC
In the Linux kernel, the following vulnerability has been resolved:

drm/gpusvm: Fix MM reference leak in drm_gpusvm_range_evict

If kvmalloc_array() fails in drm_gpusvm_range_evict(), the MM
reference acquired earlier is not released, resulting in a reference
leak.

Fix this by dropping the MM reference on the kvmalloc_array()
failure path.

Comment 6 Yadnyawalk Tale 2026-08-13 10:52:12 UTC
.

Comment 7 Yadnyawalk Tale 2026-08-13 10:52:14 UTC
.

Comment 8 Yadnyawalk Tale 2026-08-13 10:53:12 UTC
.

Comment 9 Yadnyawalk Tale 2026-08-13 10:54:31 UTC
.

Comment 10 Yadnyawalk Tale 2026-08-13 10:56:07 UTC
.

Comment 11 Yadnyawalk Tale 2026-08-13 10:56:09 UTC
.