In the Linux kernel, the following vulnerability has been resolved: cpufreq: initialize policy...

zetlyn/cve-ghsa vulnerability ghsa GHSA-73ff-5qgw-vhj7 cve CVE-2026-97904 known 2026-09-25

https://github.com/advisories/GHSA-73ff-5qgw-vhj7

Properties

severityunknown
receipt
Source
GitHub advisories
Its words
unknown
Read by
field:severity
Said since
2026-09-28 11:44 UTC
Last answered
2026-10-06 13:46 UTC
Original
open at the source
What the source handed over
{
  "credits": [],
  "cve_id": "CVE-2026-97904",
  "cvss": {
    "score": null,
    "vector_string": null
  },
  "cvss_severities": {
    "cvss_v3": {
      "score": 0.0,
      "vector_string": null
    },
    "cvss_v4": {
      "score": 0.0,
      "vector_string": null
    }
  },
  "cwes": [],
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: initialize policy rwsem before sysfs publication\n\ncpufreq_policy_alloc() initializes policy->rwsem after\nkobject_init_and_add() has created the policy sysfs directory and its\ndefault attributes. A sysfs access can therefore reach a policy callback\nbefore the semaphore has been initialized.\n\nInitialize policy->rwsem before publishing the policy kobject so sysfs\ncallbacks always see an initialized semaphore.",
  "epss": {
    "percentage": 0.002,
    "percentile": 0.08846
  },
  "ghsa_id": "GHSA-73ff-5qgw-vhj7",
  "github_reviewed_at": null,
  "html_url": "https://github.com/advisories/GHSA-73ff-5qgw-vhj7",
  "identifiers": [
    {
      "type": "GHSA",
      "value": "GHSA-73ff-5qgw-vhj7"
    },
    {
      "type": "CVE",
      "value": "CVE-2026-97904"
    }
  ],
  "nvd_published_at": "2026-09-25T11:17:17Z",
  "published_at": "2026-09-25T12:31:27Z",
  "references": [
    "https://nvd.nist.gov/vuln/detail/CVE-2026-97904",
    "https://git.kernel.org/stable/c/27c9b491bf7604e83b50c3bbfa18a30266ff345f",
    "https://git.kernel.org/stable/c/2cee937f779f69b195b37bbec1e888da9bfe9d58",
    "https://git.kernel.org/stable/c/3e5d1bf4bd687beb2cb4e32a07af695455925588",
    "https://git.kernel.org/stable/c/dc11263cb05ed519758fd135fe08d611bad1f241",
    "https://github.com/advisories/GHSA-73ff-5qgw-vhj7"
  ],
  "repository_advisory_url": null,
  "severity": "unknown",
  "source_code_location": "",
  "summary": "In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: initialize policy...",
  "type": "unreviewed",
  "updated_at": "2026-09-25T12:31:36Z",
  "url": "https://api.github.com/advisories/GHSA-73ff-5qgw-vhj7",
  "vulnerabilities": [],
  "withdrawn_at": null
}

Text

In the Linux kernel, the following vulnerability has been resolved: cpufreq: initialize policy... 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.