| 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: <2025072557-CVE-2025-38363-122c@gregkh> Date: Fri, 25 Jul 2025 14:48:04 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38363: drm/tegra: Fix a possible null pointer dereference From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/tegra: Fix a possible null pointer dereference In tegra_crtc_reset(), new memory is allocated with kzalloc(), but no check is performed. Before calling __drm_atomic_helper_crtc_reset, state should be checked to prevent possible null pointer dereference. The Linux kernel CVE team has assigned CVE-2025-38363 to this issue. Affected and fixed versions =========================== Issue introduced in 5.3 with commit b7e0b04ae450a0f2f73c376c3057fb05d798e33c and fixed in 5.10.240 with commit ab390ab81241cf8bf37c0a0ac2e9c6606bf3e991 Issue introduced in 5.3 with commit b7e0b04ae450a0f2f73c376c3057fb05d798e33c and fixed in 5.15.187 with commit c7fc459ae6f988e0d5045a270bd600ab08bc61f1 Issue introduced in 5.3 with commit b7e0b04ae450a0f2f73c376c3057fb05d798e33c and fixed in 6.1.143 with commit 99a25fc7933b88d5e16668bf6ba2d098e1754406 Issue introduced in 5.3 with commit b7e0b04ae450a0f2f73c376c3057fb05d798e33c and fixed in 6.6.96 with commit 5ff3636bcc32e1cb747f6f820bcf2bb6990a7d41 Issue introduced in 5.3 with commit b7e0b04ae450a0f2f73c376c3057fb05d798e33c and fixed in 6.12.36 with commit 31ac2c680a8ac11dc54a5b339a07e138bcedd924 Issue introduced in 5.3 with commit b7e0b04ae450a0f2f73c376c3057fb05d798e33c and fixed in 6.15.5 with commit ac4ca634f0c9f227538711d725339293f7047b02 Issue introduced in 5.3 with commit b7e0b04ae450a0f2f73c376c3057fb05d798e33c and fixed in 6.16-rc1 with commit 780351a5f61416ed2ba1199cc57e4a076fca644d 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-2025-38363 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/tegra/dc.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/ab390ab81241cf8bf37c0a0ac2e9c6606bf3e991 https://git.kernel.org/stable/c/c7fc459ae6f988e0d5045a270bd600ab08bc61f1 https://git.kernel.org/stable/c/99a25fc7933b88d5e16668bf6ba2d098e1754406 https://git.kernel.org/stable/c/5ff3636bcc32e1cb747f6f820bcf2bb6990a7d41 https://git.kernel.org/stable/c/31ac2c680a8ac11dc54a5b339a07e138bcedd924 https://git.kernel.org/stable/c/ac4ca634f0c9f227538711d725339293f7047b02 https://git.kernel.org/stable/c/780351a5f61416ed2ba1199cc57e4a076fca644d
Powered by blists - more mailing lists