CVE-2025-40130: scsi: ufs: core: Fix data race in CPU latency PM QoS request handling
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Fixed version: Linux Linux 79dde5f7dc7c038eec903745dc1550cd4139980e, d9df61afb8d23c475f1be3c714da2c34c156ab01, eee1b13526b8f1e6a2402973d95f9fa854771f57.
Low priority for now. Upgrade to Linux Linux 79dde5f7dc7c038eec903745dc1550cd4139980e, d9df61afb8d23c475f1be3c714da2c34c156ab01, eee1b13526b8f1e6a2402973d95f9fa854771f57 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2025-15300
- openSUSE-SU-2026:20145-1
- openSUSE-SU-2026:20311-1
- openSUSE-SU-2026:20314-1
- SUSE-SU-2026:20207-1
- SUSE-SU-2026:20220-1
- SUSE-SU-2026:20228-1
- SUSE-SU-2026:20564-1
- SUSE-SU-2026:20634-1
- SUSE-SU-2026:20635-1
- SUSE-SU-2026:20636-1
- SUSE-SU-2026:20637-1
- SUSE-SU-2026:20643-1
- SUSE-SU-2026:20644-1
- SUSE-SU-2026:20646-1
- SUSE-SU-2026:20648-1
- Published
- Nov 12, 2025
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.9affected
- 2777e73fc154e2e87233bdcc0e2402b33815198e and later · before eee1b13526b8f1e6a2402973d95f9fa854771f57affected · git
- 2777e73fc154e2e87233bdcc0e2402b33815198e and later · before d9df61afb8d23c475f1be3c714da2c34c156ab01affected · git
- 2777e73fc154e2e87233bdcc0e2402b33815198e and later · before 79dde5f7dc7c038eec903745dc1550cd4139980eaffected · git
- before 6.9not affected · semver
- 6.12.114 and later · up to and including 6.12.*not affected · semver
- 6.17.3 and later · up to and including 6.17.*not affected · semver
- 6.18 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | from 0 | — |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.9.1.160000.2.6 | 6.12.0-160000.9.1.160000.2.6 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-azure | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-livepatch-SLE16_Update_0 | before 7-160000.4.3 | 7-160000.4.3 |
| SUSE:Linux Enterprise Server 16.0 | kernel-livepatch-SLE16_Update_1 | before 5-160000.1.1 | 5-160000.1.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-livepatch-SLE16_Update_2 | before 3-160000.1.1 | 3-160000.1.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-livepatch-SLE16_Update_3 | before 2-160000.1.1 | 2-160000.1.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-syms | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
+7
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40127Nov 12, 2025 · hwrng: ks-sa - fix division by zero in ks_sa_rng_init0Monitor
- ← EarlierCVE-2025-40129Nov 12, 2025 · sunrpc: fix null pointer dereference on zero-length checksum30Monitor
- Later →CVE-2025-40131Nov 12, 2025 · wifi: ath12k: Fix peer lookup in ath12k_dp_mon_rx_deliver_msdu()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 79dde5f7dc7c038eec903745dc1550cd4139980e | Vendor (CNA) |
| Linux Linux | d9df61afb8d23c475f1be3c714da2c34c156ab01 | Vendor (CNA) |
| Linux Linux | eee1b13526b8f1e6a2402973d95f9fa854771f57 | Vendor (CNA) |
| debian:linux | 6.17.6-1 · Debian:14 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.9.1.160000.2.6 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.9.1.160000.2.6 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.9.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.