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

> A race condition in the Linux kernel cpufreq subsystem allows local attackers to trigger a denial of service by accessing uninitialized sysfs attributes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104262, BELL-CVE-2026-97904, DEBIAN-CVE-2026-97904, GHSA-73ff-5qgw-vhj7, UBUNTU-CVE-2026-97904

## What is CVE-2026-97904?

CVE-2026-97904 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-97904?


## How do I fix CVE-2026-97904?

Apply the vendor's patch.

## Is CVE-2026-97904 being exploited?

There is no known exploitation of CVE-2026-97904 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97904 and fix it if it is affected.

What it is: CVE-2026-97904 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97904 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97904/ (Markdown: https://insights.sbomify.com/CVE-2026-97904/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97904
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97904
- OSV: https://osv.dev/vulnerability/CVE-2026-97904

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97904/
Summaries are generated and may contain mistakes; the official description above is the record.