# CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev

> A race condition in the Linux kernel Coresight driver allows concurrent access to configuration lists, potentially causing system instability or crashes.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jul 2025
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2025-38132, DEBIAN-CVE-2025-38132, GHSA-gqgv-qr8f-vwmq, ROOT-OS-DEBIAN-12-CVE-2025-38132, ROOT-OS-DEBIAN-13-CVE-2025-38132, ROOT-OS-UBUNTU-2404-CVE-2025-38132, UBUNTU-CVE-2025-38132

## What is CVE-2025-38132?

CVE-2025-38132 is a medium-severity vulnerability in Linux kernel, published on 3 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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()

## Which versions are affected by CVE-2025-38132?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-38132?

Apply the vendor's patch.

## Is CVE-2025-38132 being exploited?

There is no known exploitation of CVE-2025-38132 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-38132 and fix it if it is affected.

What it is: CVE-2025-38132 is a medium-severity vulnerability in Linux kernel, published on 3 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-38132 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-38132/ (Markdown: https://insights.sbomify.com/CVE-2025-38132/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-38132
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-38132
- OSV: https://osv.dev/vulnerability/CVE-2025-38132

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-38132/
Summaries are generated and may contain mistakes; the official description above is the record.