drm/xe: free madvise VMA array on L2 flush failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: free madvise VMA array on L2 flush failure
xe_vm_madvise_ioctl() allocates madvise_range.vmas in get_vmas(). After get_vmas() succeeds with at least one VMA, error paths must go through free_vmas so the array is released before the madvise details are destroyed.
The L2 flush validation path added for PAT madvise rejects some SVM/userptr ranges after get_vmas() has succeeded, but jumps directly to madv_fini. This skips kfree(madvise_range.vmas), leaking the VMA array on each failed ioctl.
Jump to free_vmas instead, matching the other validation failure paths after get_vmas() has succeeded.
(cherry picked from commit c3a1c3579b1250060da73507a4acef712974c78a)
From the CVE record · Linux
The Linux kernel’s drm/xe madvise ioctl leaks a VMA array when L2 flush validation rejects certain SVM/userptr ranges after the array is allocated. A local caller who can invoke the ioctl can trigger the leak on each failed call; the input does not specify additional authentication requirements.
Engineers running Linux kernels with the affected drm/xe code should check their kernel versions; affected versions are not specified.