coresight: holding cscfg_csdev_lock while removing cscfg from csdev
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
coresight: holding cscfg_csdev_lock while removing cscfg from csdev
There'll be possible race scenario for coresight config:
CPU0 CPU1 (perf enable) load module cscfg_load_config_sets() activate config. // sysfs (sys_active_cnt == 1) ... cscfg_csdev_enable_active_config() lock(csdev->cscfg_csdev_lock) deactivate config // sysfs (sys_activec_cnt == 0) cscfg_unload_config_sets() <iterating config_csdev_list> cscfg_remove_owned_csdev_configs() // here load config activate by CPU1 unlock(csdev->cscfg_csdev_lock)
iterating config_csdev_list could be raced with config_csdev_list's entry delete.
To resolve this race , hold csdev->cscfg_csdev_lock() while cscfg_remove_owned_csdev_configs()
From the CVE record · Linux
The Linux kernel's CoreSight configuration handling has a race between enabling an active configuration and removing configurations from a device. Concurrent perf enablement and module loading or unloading with sysfs configuration activation or deactivation can cause a configuration list entry to be deleted while it is being iterated. The input does not specify an attacker access level or a resulting impact beyond the race.
Engineers running Linux kernels with CoreSight configuration support should check their kernel versions; affected versions are not specified.