linux-cve-announce - CVE-2025-68370: coresight: tmc: add the handle of the event to the path

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2025122400-CVE-2025-68370-d381@gregkh>
Date: Wed, 24 Dec 2025 11:35:15 +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-68370: coresight: tmc: add the handle of the event to the path

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

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

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

coresight: tmc: add the handle of the event to the path

The handle is essential for retrieving the AUX_EVENT of each CPU and is
required in perf mode. It has been added to the coresight_path so that
dependent devices can access it from the path when needed.

The existing bug can be reproduced with:
perf record -e cs_etm//k -C 0-9 dd if=/dev/zero of=/dev/null

Showing an oops as follows:
Unable to handle kernel paging request at virtual address 000f6e84934ed19e

Call trace:
 tmc_etr_get_buffer+0x30/0x80 [coresight_tmc] (P)
 catu_enable_hw+0xbc/0x3d0 [coresight_catu]
 catu_enable+0x70/0xe0 [coresight_catu]
 coresight_enable_path+0xb0/0x258 [coresight]

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


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

	Issue introduced in 6.15 with commit 080ee83cc361451a7de7b5486c7f96ce454f7203 and fixed in 6.17.13 with commit faa8f38f7ccb344ace2c1f364efc70e3a12d32f3
	Issue introduced in 6.15 with commit 080ee83cc361451a7de7b5486c7f96ce454f7203 and fixed in 6.18.2 with commit d0c9effd82f2c19b92acd07d357fac5f392d549a
	Issue introduced in 6.15 with commit 080ee83cc361451a7de7b5486c7f96ce454f7203 and fixed in 6.19-rc1 with commit aaa5abcc9d44d2c8484f779ab46d242d774cabcb

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-68370
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-etm-perf.c
	drivers/hwtracing/coresight/coresight-tmc-etr.c
	include/linux/coresight.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/faa8f38f7ccb344ace2c1f364efc70e3a12d32f3
	https://git.kernel.org/stable/c/d0c9effd82f2c19b92acd07d357fac5f392d549a
	https://git.kernel.org/stable/c/aaa5abcc9d44d2c8484f779ab46d242d774cabcb