| 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: <2025052047-CVE-2025-37938-30a4@gregkh> Date: Tue, 20 May 2025 17:34:46 +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-37938: tracing: Verify event formats that have "%*p.." From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: tracing: Verify event formats that have "%*p.." The trace event verifier checks the formats of trace events to make sure that they do not point at memory that is not in the trace event itself or in data that will never be freed. If an event references data that was allocated when the event triggered and that same data is freed before the event is read, then the kernel can crash by reading freed memory. The verifier runs at boot up (or module load) and scans the print formats of the events and checks their arguments to make sure that dereferenced pointers are safe. If the format uses "%*p.." the verifier will ignore it, and that could be dangerous. Cover this case as well. Also add to the sample code a use case of "%*pbl". The Linux kernel CVE team has assigned CVE-2025-37938 to this issue. Affected and fixed versions =========================== Issue introduced in 5.13 with commit 5013f454a352cce8e62162976026a9c472595e42 and fixed in 6.1.136 with commit 6854c87ac823181c810f8c07489ba543260c0023 Issue introduced in 5.13 with commit 5013f454a352cce8e62162976026a9c472595e42 and fixed in 6.6.89 with commit 4d11fac941d83509be4e6a21038281d6d96da50c Issue introduced in 5.13 with commit 5013f454a352cce8e62162976026a9c472595e42 and fixed in 6.12.26 with commit 03127354027508d076073b020d3070990fd6a958 Issue introduced in 5.13 with commit 5013f454a352cce8e62162976026a9c472595e42 and fixed in 6.13.11 with commit 04b80d45ecfaf780981d6582899e3ab205e4aa08 Issue introduced in 5.13 with commit 5013f454a352cce8e62162976026a9c472595e42 and fixed in 6.14.2 with commit c7204fd1758c0caf1938e8a59809a1fdf28a8114 Issue introduced in 5.13 with commit 5013f454a352cce8e62162976026a9c472595e42 and fixed in 6.15-rc1 with commit ea8d7647f9ddf1f81e2027ed305299797299aa03 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-37938 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: kernel/trace/trace_events.c samples/trace_events/trace-events-sample.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/6854c87ac823181c810f8c07489ba543260c0023 https://git.kernel.org/stable/c/4d11fac941d83509be4e6a21038281d6d96da50c https://git.kernel.org/stable/c/03127354027508d076073b020d3070990fd6a958 https://git.kernel.org/stable/c/04b80d45ecfaf780981d6582899e3ab205e4aa08 https://git.kernel.org/stable/c/c7204fd1758c0caf1938e8a59809a1fdf28a8114 https://git.kernel.org/stable/c/ea8d7647f9ddf1f81e2027ed305299797299aa03
Powered by blists - more mailing lists