CVE-2025-40130 Details
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.
A data race vulnerability has been identified in the Linux kernel's handling of CPU latency Power Management Quality of Service (PM QoS) requests, specifically within the UFS (Universal Flash Storage) driver. The issue arises because the interfaces for adding, removing, and updating CPU latency QoS requests lack internal synchronization, leaving them vulnerable to concurrent access issues. This flaw has led to data races and corruption of internal data structures. The vulnerability was introduced when CPU latency QoS support was added to the UFS driver, and it has been resolved by implementing a dedicated mutex to synchronize PM QoS operations, ensuring safe access to PM QoS resources and preventing data races.
The vulnerability has been fixed in the Linux kernel. Users should upgrade to the latest version where this issue has been addressed.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Nov 12, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/79dde5f7dc7c038eec903745dc1550cd4139980e | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/d9df61afb8d23c475f1be3c714da2c34c156ab01 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/eee1b13526b8f1e6a2402973d95f9fa854771f57 | kernel.org |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 21, 2026 | CVE Modified | kernel.org |
| Oct 19, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 12, 2025 | New CVE Received | kernel.org |
Volerion