drm/msm/dpu: don't mix devm and drmm functions
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 |
|
|
6.18.347.0.117.1In the Linux kernel, the following vulnerability has been resolved:
drm/msm/dpu: don't mix devm and drmm functions
Mixing devm and drmm functions will result in a use-after-free on msm driver teardown if userspace keeps a reference on the drm device: The WB connector data will be destroyed because of the use of devm_kzalloc()), while the usersoace still can try interacting with the WB connector (which uses drmm_ functions).
Change dpu_writeback_init() to use drmm_.
Patchwork: https://patchwork.freedesktop.org/patch/722656/
From the CVE record · Linux
The Linux kernel’s msm display driver mixes device-managed cleanup mechanisms, causing a use-after-free during driver teardown. This can occur if local userspace retains a reference to the DRM device and interacts with the writeback connector after its data is freed. The input does not specify authentication requirements.
Engineers running Linux kernels with the affected msm display driver should check their kernel vendor’s advisory; affected versions were not specified.