cpufreq: initialize policy rwsem before sysfs publication
Summary
| CVE | CVE-2026-97904 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-25 11:17:17 UTC |
| Updated | 2026-10-03 11:18:08 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: cpufreq: initialize policy rwsem before sysfs publication cpufreq_policy_alloc() initializes policy->rwsem after kobject_init_and_add() has created the policy sysfs directory and its default attributes. A sysfs access can therefore reach a policy callback before the semaphore has been initialized. Initialize policy->rwsem before publishing the policy kobject so sysfs callbacks always see an initialized semaphore. |
Risk And Classification
EPSS: 0.002100000 probability, percentile 0.102520000 (date 2026-10-05)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 c9d8435814f2ac533c40fe3f35d94235bc3a9443 git | Not specified |
| CNA | Linux | Linux | affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 82a54923700da5de83ce2b26c0b43f6b5005c8f1 git | Not specified |
| CNA | Linux | Linux | affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 b14987a0f73777644099f47f01aba3b0f9dc6c27 git | Not specified |
| CNA | Linux | Linux | affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 b22193eea2ce32c39dda5e09f9c2be2f3fd7eb4a git | Not specified |
| CNA | Linux | Linux | affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 dc11263cb05ed519758fd135fe08d611bad1f241 git | Not specified |
| CNA | Linux | Linux | affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 27c9b491bf7604e83b50c3bbfa18a30266ff345f git | Not specified |
| CNA | Linux | Linux | affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 2cee937f779f69b195b37bbec1e888da9bfe9d58 git | Not specified |
| CNA | Linux | Linux | affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 3e5d1bf4bd687beb2cb4e32a07af695455925588 git | Not specified |
| CNA | Linux | Linux | affected 4.2 | Not specified |
| CNA | Linux | Linux | unaffected 4.2 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.271 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.222 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.189 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.158 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.111 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.7 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/b22193eea2ce32c39dda5e09f9c2be2f3fd7eb4a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/c9d8435814f2ac533c40fe3f35d94235bc3a9443 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/27c9b491bf7604e83b50c3bbfa18a30266ff345f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/82a54923700da5de83ce2b26c0b43f6b5005c8f1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3e5d1bf4bd687beb2cb4e32a07af695455925588 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/dc11263cb05ed519758fd135fe08d611bad1f241 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b14987a0f73777644099f47f01aba3b0f9dc6c27 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2cee937f779f69b195b37bbec1e888da9bfe9d58 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.