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: <2025030708-CVE-2025-21843-4385@gregkh> Date: Fri, 7 Mar 2025 10:10:13 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2025-21843: drm/panthor: avoid garbage value in panthor_ioctl_dev_query() Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/panthor: avoid garbage value in panthor_ioctl_dev_query() 'priorities_info' is uninitialized, and the uninitialized value is copied to user object when calling PANTHOR_UOBJ_SET(). Using memset to initialize 'priorities_info' to avoid this garbage value problem. The Linux kernel CVE team has assigned CVE-2025-21843 to this issue. Affected and fixed versions =========================== Issue introduced in 6.13 with commit f70000ef23527f6d928d1175c66c5fafa968814b and fixed in 6.13.4 with commit 64b95bbc08bacf3e4b05c8604e6a4fec43bb712a Issue introduced in 6.13 with commit f70000ef23527f6d928d1175c66c5fafa968814b and fixed in 6.14-rc3 with commit 3b32b7f638fe61e9d29290960172f4e360e38233 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-21843 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/panthor/panthor_drv.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/64b95bbc08bacf3e4b05c8604e6a4fec43bb712a https://git.kernel.org/stable/c/3b32b7f638fe61e9d29290960172f4e360e38233
Powered by blists - more mailing lists