drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3bacf814b6a61cc683c68465f175ebd938f09c52, Kernel 3fb61718bcbe309279205d1cc275a6435611dc77 and Kernel aedf02e46eb549dac8db4821a6b9f0c6bf6e3990.
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() For cases where the crtc's connectors_changed was set without enable/active getting toggled , there is an atomic_enable() call followed by an atomic_disable() but without an atomic_mode_set(). This results in a NULL ptr access for the dpu_encoder_get_drm_fmt() call in the atomic_enable() as the dpu_encoder's connector was cleared in the atomic_disable() but not re-assigned as there was no atomic_mode_set() call. Fix the NULL ptr access by moving the assignment for atomic_enable() and also use drm_atomic_get_new_connector_for_encoder() to get the connector from the atomic_state. Patchwork: https://patchwork.freedesktop.org/patch/606729/
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.19, >=25fdd5933e4c0f5fe2ea5cd59994f8ac5fbe90ef <3bacf814b6a61cc683c68465f175ebd938f09c52, >=25fdd5933e4c0f5fe2ea5cd59994f8ac5fbe90ef <3fb61718bcbe309279205d1cc275a6435611dc77, >=25fdd5933e4c0f5fe2ea5cd59994f8ac5fbe90ef <aedf02e46eb549dac8db4821a6b9f0c6bf6e3990 | 3bacf814b6a61cc683c68465f175ebd938f09c52, 3fb61718bcbe309279205d1cc275a6435611dc77, aedf02e46eb549dac8db4821a6b9f0c6bf6e3990 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket