| 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: <2025111229-CVE-2025-40111-23d1@gregkh> Date: Wed, 12 Nov 2025 10:07:29 +0900 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-40111: drm/vmwgfx: Fix Use-after-free in validation From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Fix Use-after-free in validation Nodes stored in the validation duplicates hashtable come from an arena allocator that is cleared at the end of vmw_execbuf_process. All nodes are expected to be cleared in vmw_validation_drop_ht but this node escaped because its resource was destroyed prematurely. The Linux kernel CVE team has assigned CVE-2025-40111 to this issue. Affected and fixed versions =========================== Issue introduced in 4.20 with commit 64ad2abfe9a628ce79859d072704bd1ef7682044 and fixed in 5.4.301 with commit 1822e5287b7dfa59d0af966756ebf1dc652b60ee Issue introduced in 4.20 with commit 64ad2abfe9a628ce79859d072704bd1ef7682044 and fixed in 5.10.246 with commit fb7165e5f3b3b10721ff70553583ad12e90e447a Issue introduced in 4.20 with commit 64ad2abfe9a628ce79859d072704bd1ef7682044 and fixed in 5.15.195 with commit 4c918f9d1ccccc0e092f43dcb2d8266f54d7340b Issue introduced in 4.20 with commit 64ad2abfe9a628ce79859d072704bd1ef7682044 and fixed in 6.1.157 with commit 9a8eaca539708ca532747f606d231f70e684e8ca Issue introduced in 4.20 with commit 64ad2abfe9a628ce79859d072704bd1ef7682044 and fixed in 6.6.113 with commit 867bda5d95d36f10da398fd4409e21c7002b2332 Issue introduced in 4.20 with commit 64ad2abfe9a628ce79859d072704bd1ef7682044 and fixed in 6.12.54 with commit 655a2f29bfc21105c80bf8a7d7aafa6eca8b4496 Issue introduced in 4.20 with commit 64ad2abfe9a628ce79859d072704bd1ef7682044 and fixed in 6.17.4 with commit 65608e991c2d771c13404e5c7ae122ac3c3357a4 Issue introduced in 4.20 with commit 64ad2abfe9a628ce79859d072704bd1ef7682044 and fixed in 6.18-rc1 with commit dfe1323ab3c8a4dd5625ebfdba44dc47df84512a 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-40111 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/vmwgfx/vmwgfx_validation.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/1822e5287b7dfa59d0af966756ebf1dc652b60ee https://git.kernel.org/stable/c/fb7165e5f3b3b10721ff70553583ad12e90e447a https://git.kernel.org/stable/c/4c918f9d1ccccc0e092f43dcb2d8266f54d7340b https://git.kernel.org/stable/c/9a8eaca539708ca532747f606d231f70e684e8ca https://git.kernel.org/stable/c/867bda5d95d36f10da398fd4409e21c7002b2332 https://git.kernel.org/stable/c/655a2f29bfc21105c80bf8a7d7aafa6eca8b4496 https://git.kernel.org/stable/c/65608e991c2d771c13404e5c7ae122ac3c3357a4 https://git.kernel.org/stable/c/dfe1323ab3c8a4dd5625ebfdba44dc47df84512a
Powered by blists - more mailing lists