linux-cve-announce - CVE-2025-40060: coresight: trbe: Return NULL pointer for allocation failures

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025102816-CVE-2025-40060-eb50@gregkh>
Date: Tue, 28 Oct 2025 12:48:37 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40060: coresight: trbe: Return NULL pointer for allocation failures

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

coresight: trbe: Return NULL pointer for allocation failures

When the TRBE driver fails to allocate a buffer, it currently returns
the error code "-ENOMEM". However, the caller etm_setup_aux() only
checks for a NULL pointer, so it misses the error. As a result, the
driver continues and eventually causes a kernel panic.

Fix this by returning a NULL pointer from arm_trbe_alloc_buffer() on
allocation failures. This allows that the callers can properly handle
the failure.

The Linux kernel CVE team has assigned CVE-2025-40060 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.13 with commit 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and fixed in 5.15.195 with commit cef047e0a55cb07906fcaae99170f19a9c0bb6c2
	Issue introduced in 5.13 with commit 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and fixed in 6.1.156 with commit fe53a726d5edf864e80b490780cc135fc1adece9
	Issue introduced in 5.13 with commit 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and fixed in 6.6.112 with commit 9768536f82600a05ce901e31ccfabd92c027ff71
	Issue introduced in 5.13 with commit 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and fixed in 6.12.53 with commit 296da78494633e1ab5e2e74173a9c8683b04aa6b
	Issue introduced in 5.13 with commit 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and fixed in 6.17.3 with commit f505a165f1c7cd37b4cb6952042a5984693a4067
	Issue introduced in 5.13 with commit 3fbf7f011f2426dac8c982f1d2ef469a7959a524 and fixed in 6.18-rc1 with commit 8a55c161f7f9c1aa1c70611b39830d51c83ef36d

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-40060
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/hwtracing/coresight/coresight-trbe.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/cef047e0a55cb07906fcaae99170f19a9c0bb6c2
	https://git.kernel.org/stable/c/fe53a726d5edf864e80b490780cc135fc1adece9
	https://git.kernel.org/stable/c/9768536f82600a05ce901e31ccfabd92c027ff71
	https://git.kernel.org/stable/c/296da78494633e1ab5e2e74173a9c8683b04aa6b
	https://git.kernel.org/stable/c/f505a165f1c7cd37b4cb6952042a5984693a4067
	https://git.kernel.org/stable/c/8a55c161f7f9c1aa1c70611b39830d51c83ef36d