Description
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()
Affected products
linux: linux kernel
References5
- git.kernel.org/stable/c/42f8afb0b161631fd1d814d017f75f955475ad41 Patch
- git.kernel.org/stable/c/53b9e2659719b04f5ba7593f2af0f2335f75e94a Patch
- git.kernel.org/stable/c/18a3a21c39cca593762aa90f322bd74c18ec59d4
- git.kernel.org/stable/c/1cd09aaf47a570bf6b05a7cd06b98e9d35fe82c7
- git.kernel.org/stable/c/8f16b9caf0bdba46044e1d3727ee78291aa36347
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 14 · as of 7 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.