Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97904cpufreq: initialize policy rwsem before sysfs publication

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < c9d8435814f2ac533c40fe3f35d94235bc3a9443
    • affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < 82a54923700da5de83ce2b26c0b43f6b5005c8f1
    • affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < b14987a0f73777644099f47f01aba3b0f9dc6c27
    • affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < b22193eea2ce32c39dda5e09f9c2be2f3fd7eb4a
    • affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < dc11263cb05ed519758fd135fe08d611bad1f241
    • affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < 27c9b491bf7604e83b50c3bbfa18a30266ff345f
    • affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < 2cee937f779f69b195b37bbec1e888da9bfe9d58
    • affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < 3e5d1bf4bd687beb2cb4e32a07af695455925588
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97904 badge
[![CVE-2026-97904](https://cveledger.app/badge/CVE-2026-97904.svg)](https://cveledger.app/cve/CVE-2026-97904)

Record last updated .