drm/msm: Only fini scheduler after successful init
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 · < e2332abed2a4d3caa59052095dc16e4ce44791ea| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/msm: Only fini scheduler after successful init
msm_ringbuffer_new() destroys a partially initialized ring through msm_ringbuffer_destroy() when an allocation or scheduler setup step fails.
If drm_sched_init() fails before it finishes initializing the scheduler, the failure path still calls drm_sched_fini(). That teardown path assumes the scheduler work items, lists, and workqueue state were initialized.
Track successful scheduler initialization and call drm_sched_fini() only after drm_sched_init() returned 0.
This issue was found by a static analysis checker and confirmed by manual source review.
Patchwork: https://patchwork.freedesktop.org/patch/738905/
From the CVE record · Linux
The Linux kernel’s drm/msm ring-buffer failure path can call drm_sched_fini() even when scheduler initialization failed. This may tear down uninitialized scheduler state. The input does not establish an attacker capability or specify network access, authentication requirements, or user interaction.
Engineers running Linux kernels with the drm/msm component should check their builds; affected versions are not specified.