| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025022605-CVE-2022-49488-5f36@gregkh> Date: Wed, 26 Feb 2025 03:12:42 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49488: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected There is a possibility for mdp5_get_global_state to return -EDEADLK when acquiring the modeset lock, but currently global_state in mdp5_mixer_release doesn't check for if an error is returned. To avoid a NULL dereference error, let's have mdp5_mixer_release check if an error is returned and propagate that error. Patchwork: https://patchwork.freedesktop.org/patch/485181/ The Linux kernel CVE team has assigned CVE-2022-49488 to this issue. Affected and fixed versions =========================== Issue introduced in 4.18 with commit 7907a0d77cb461f58045763c205a5830be72e97c and fixed in 4.19.247 with commit 1a5d1474026ea4f1a6f931075ca2adb884af39cf Issue introduced in 4.18 with commit 7907a0d77cb461f58045763c205a5830be72e97c and fixed in 5.4.198 with commit 22d8424913b1348c6324916745fadaeea5273f0e Issue introduced in 4.18 with commit 7907a0d77cb461f58045763c205a5830be72e97c and fixed in 5.10.121 with commit 883f1d52a57bf51e1d7a80c432345e2c6222477e Issue introduced in 4.18 with commit 7907a0d77cb461f58045763c205a5830be72e97c and fixed in 5.15.46 with commit 09bdeedc1fc53e64b8282e1de67752c69e43bdba Issue introduced in 4.18 with commit 7907a0d77cb461f58045763c205a5830be72e97c and fixed in 5.17.14 with commit 47e393061049aff6818d1b9fdca7351411a23fc2 Issue introduced in 4.18 with commit 7907a0d77cb461f58045763c205a5830be72e97c and fixed in 5.18.3 with commit 46e5ce63924a96af452c4fc5ee0bb3b241e1b9f4 Issue introduced in 4.18 with commit 7907a0d77cb461f58045763c205a5830be72e97c and fixed in 5.19 with commit ca75f6f7c6f89365e40f10f641b15981b1f07c31 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2022-49488 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c drivers/gpu/drm/msm/disp/mdp5/mdp5_mixer.c drivers/gpu/drm/msm/disp/mdp5/mdp5_mixer.h Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/1a5d1474026ea4f1a6f931075ca2adb884af39cf https://git.kernel.org/stable/c/22d8424913b1348c6324916745fadaeea5273f0e https://git.kernel.org/stable/c/883f1d52a57bf51e1d7a80c432345e2c6222477e https://git.kernel.org/stable/c/09bdeedc1fc53e64b8282e1de67752c69e43bdba https://git.kernel.org/stable/c/47e393061049aff6818d1b9fdca7351411a23fc2 https://git.kernel.org/stable/c/46e5ce63924a96af452c4fc5ee0bb3b241e1b9f4 https://git.kernel.org/stable/c/ca75f6f7c6f89365e40f10f641b15981b1f07c31
Powered by blists - more mailing lists