drm/v3d: Reject invalid indirect BO handle in indirect CSD setup
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/v3d: Reject invalid indirect BO handle in indirect CSD setup
v3d_get_cpu_indirect_csd_params() looks up the indirect buffer object from a userspace-supplied handle but never checks the result. A bogus or stale handle makes drm_gem_object_lookup() return NULL, which is then stored in info->indirect and only dereferenced later when the indirect CSD job runs, turning a userspace mistake into a NULL pointer dereference in the kernel.
Bail out with -ENOENT as soon as the lookup fails, so the bad handle is rejected at submission time.
From the CVE record · Linux
The Linux kernel’s drm/v3d indirect CSD setup does not check whether a userspace-supplied buffer object handle resolves to an object. A local user who submits a bogus or stale handle can trigger a kernel NULL pointer dereference when the indirect CSD job runs.
Engineers running the Linux kernel with drm/v3d should check their systems; affected versions are not specified.