CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev
In the Linux kernel, the following vulnerability has been resolved:
coresight: holding cscfgcsdevlock while removing cscfg from csdev
There'll be possible race scenario for coresight config:
CPU0 CPU1 (perf enable) load module cscfgloadconfigsets() activate config. // sysfs (sysactivecnt == 1) ... cscfgcsdevenableactiveconfig() lock(csdev->cscfgcsdevlock) deactivate config // sysfs (sysactiveccnt == 0) cscfgunloadconfigsets() <iterating configcsdevlist> cscfgremoveownedcsdevconfigs() // here load config activate by CPU1 unlock(csdev->cscfgcsdevlock)
iterating configcsdevlist could be raced with configcsdevlist's entry delete.
To resolve this race , hold csdev->cscfgcsdevlock() while cscfgremoveownedcsdevconfigs()
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38132?
The severity of CVE-2025-38132 has been classified as medium due to the potential for race conditions affecting the coresight configuration.
How do I fix CVE-2025-38132?
To fix CVE-2025-38132, upgrade to the latest version of the Linux kernel where this vulnerability has been patched.
Which systems are affected by CVE-2025-38132?
CVE-2025-38132 affects the Linux kernel across various versions that implement coresight functionality.
What are the symptoms of CVE-2025-38132 exploitation?
Exploitation of CVE-2025-38132 may lead to unexpected behavior in coresight configurations and potential system instability.
Is there a workaround for CVE-2025-38132?
Currently, there are no recommended workarounds for CVE-2025-38132 other than applying the security patch.