coresight: tmc: add the handle of the event to the path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.17.136.18.26.19In 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]
From the CVE record · Linux
A missing event handle in the Linux kernel’s CoreSight path can cause a kernel oops in TMC when perf records CoreSight events across CPUs. The reported trigger is a locally run perf command; the input does not specify whether authentication or elevated privileges are required.
Engineers running Linux kernels with CoreSight TMC should check their systems; affected versions were not specified.