| 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: <2025100118-CVE-2022-50454-9c7d@gregkh> Date: Wed, 1 Oct 2025 13:45:24 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2022-50454: drm/nouveau: fix a use-after-free in nouveau_gem_prime_import_sg_table() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix a use-after-free in nouveau_gem_prime_import_sg_table() nouveau_bo_init() is backed by ttm_bo_init() and ferries its return code back to the caller. On failures, ttm will call nouveau_bo_del_ttm() and free the memory.Thus, when nouveau_bo_init() returns an error, the gem object has already been released. Then the call to nouveau_bo_ref() will use the freed "nvbo->bo" and lead to a use-after-free bug. We should delete the call to nouveau_bo_ref() to avoid the use-after-free. The Linux kernel CVE team has assigned CVE-2022-50454 to this issue. Affected and fixed versions =========================== Issue introduced in 5.4 with commit 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and fixed in 5.4.220 with commit 56ee9577915dc06f55309901012a9ef68dbdb5a8 Issue introduced in 5.4 with commit 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and fixed in 5.10.150 with commit 5d6093c49c098d86c7b136aba9922df44aeb6944 Issue introduced in 5.4 with commit 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and fixed in 5.15.75 with commit 861f085f81fd569b02cc2c11165a9e6cca144424 Issue introduced in 5.4 with commit 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and fixed in 5.19.17 with commit 3aeda2fe6517cc52663d4ce3588dd43f0d4124a7 Issue introduced in 5.4 with commit 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and fixed in 6.0.3 with commit 7d80473e9f12548ac05b36af4fb9ce80f2f73509 Issue introduced in 5.4 with commit 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and fixed in 6.1 with commit 540dfd188ea2940582841c1c220bd035a7db0e51 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-50454 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/nouveau/nouveau_prime.c 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/56ee9577915dc06f55309901012a9ef68dbdb5a8 https://git.kernel.org/stable/c/5d6093c49c098d86c7b136aba9922df44aeb6944 https://git.kernel.org/stable/c/861f085f81fd569b02cc2c11165a9e6cca144424 https://git.kernel.org/stable/c/3aeda2fe6517cc52663d4ce3588dd43f0d4124a7 https://git.kernel.org/stable/c/7d80473e9f12548ac05b36af4fb9ce80f2f73509 https://git.kernel.org/stable/c/540dfd188ea2940582841c1c220bd035a7db0e51
Powered by blists - more mailing lists