CVE-2022-50319: coresight: trbe: remove cpuhp instance node before remove cpuhp state
In the Linux kernel, the following vulnerability has been resolved:
coresight: trbe: remove cpuhp instance node before remove cpuhp state
cpuhp_state_add_instance() and cpuhp_state_remove_instance() should
be used in pairs. Or there will lead to the warn on
cpuhp_remove_multi_state() since the cpuhp_step list is not empty.
The following is the error log with 'rmmod coresight-trbe':
Error: Removing state 215 which has instances left.
Call trace:
__cpuhp_remove_state_cpuslocked+0x144/0x160
__cpuhp_remove_state+0xac/0x100
arm_trbe_device_remove+0x2c/0x60 [coresight_trbe]
platform_remove+0x34/0x70
device_remove+0x54/0x90
device_release_driver_internal+0x1e4/0x250
driver_detach+0x5c/0xb0
bus_remove_driver+0x64/0xc0
driver_unregister+0x3c/0x70
platform_driver_unregister+0x20/0x30
arm_trbe_exit+0x1c/0x658 [coresight_trbe]
__arm64_sys_delete_module+0x1ac/0x24c
invoke_syscall+0x50/0x120
el0_svc_common.constprop.0+0x58/0x1a0
do_el0_svc+0x38/0xd0
el0_svc+0x2c/0xc0
el0t_64_sync_handler+0x1ac/0x1b0
el0t_64_sync+0x19c/0x1a0
---[ end trace 0000000000000000 ]---
Security readout for executives and security teams
Plain-English summary
CVE-2022-50319 is a Linux kernel issue in the CoreSight TRBE driver cleanup path. The public record describes a kernel warning when the coresight-trbe module is removed because CPU hotplug state instances remain registered. No CVSS score, CWE, or active exploitation evidence is provided.
Executive priority
Treat as routine kernel maintenance unless your environment relies on ARM64 CoreSight TRBE. There is no cited exploitation and no CVSS score, but fixed kernels should be adopted through normal patch cycles.
Technical view
The fix pairs cpuhp_state_add_instance() with cpuhp_state_remove_instance() before removing the multi-state. Without this, cpuhp_remove_multi_state() warns that instances remain. The observed path is rmmod coresight-trbe on arm64, in arm_trbe_device_remove()/arm_trbe_exit(). Stable kernel commits are referenced as fixes.
Likely exposure
Likely limited to Linux systems with the CoreSight TRBE kernel driver present and removable, especially ARM64 environments. The affected-version data in the provided record is incomplete and should be validated against distribution kernel advisories.
Exploitation context
No source in the bundle states active exploitation, public exploit availability, or remote attackability. The described trigger is module removal, which generally requires local administrative capability. Business impact is unclear from available evidence.
Researcher notes
The CVE record is sparse: no CVSS, CWE, or detailed impact analysis. The available evidence points to an improper CPU hotplug instance cleanup ordering bug in the Linux kernel TRBE driver, fixed by stable commits.
Mitigation direction
Review your Linux vendor’s advisory for CVE-2022-50319.
Update to a kernel build containing the referenced stable commits.
Prioritize ARM64 systems using or loading coresight-trbe.
If unable to update, follow vendor guidance for CoreSight TRBE exposure reduction.
Validation and detection
Inventory Linux kernel versions across ARM64 systems.
Check whether the coresight-trbe driver is present or loaded.
Compare installed kernels against vendor-fixed builds or referenced commits.
Review kernel logs for the documented CPU hotplug warning during module removal.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-50319 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Sep 15, 2025, 14:48 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.