CVE-2026-97904 json
cpufreq: initialize policy rwsem before sysfs publication
published last mo. modified 24d ago also EUVD-2026-86758
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2.7, 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.7-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-97904
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-97904
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.9-1.1
opensuse advisories openSUSE-SU-2026:12074-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-104262
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/c9d8435814f2ac533c40fe3f35d94235bc3a9443 commit
- git.kernel.org/stable/c/82a54923700da5de83ce2b26c0b43f6b5005c8f1 commit
- git.kernel.org/stable/c/b14987a0f73777644099f47f01aba3b0f9dc6c27 commit
- git.kernel.org/stable/c/b22193eea2ce32c39dda5e09f9c2be2f3fd7eb4a commit
- git.kernel.org/stable/c/dc11263cb05ed519758fd135fe08d611bad1f241 commit
- git.kernel.org/stable/c/27c9b491bf7604e83b50c3bbfa18a30266ff345f commit
- git.kernel.org/stable/c/2cee937f779f69b195b37bbec1e888da9bfe9d58 commit
- git.kernel.org/stable/c/3e5d1bf4bd687beb2cb4e32a07af695455925588 commit
Is CVE-2026-97904 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-97904 updated cvss 5.5
kernel: cpufreq: initialize policy rwsem before sysfs publication
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/c9d8435814f2ac533c40fe3f35d94235bc3a9443
- git.kernel.org /stable/c/82a54923700da5de83ce2b26c0b43f6b5005c8f1
- git.kernel.org /stable/c/b14987a0f73777644099f47f01aba3b0f9dc6c27
- git.kernel.org /stable/c/b22193eea2ce32c39dda5e09f9c2be2f3fd7eb4a
- git.kernel.org /stable/c/dc11263cb05ed519758fd135fe08d611bad1f241
- git.kernel.org /stable/c/27c9b491bf7604e83b50c3bbfa18a30266ff345f
- git.kernel.org /stable/c/2cee937f779f69b195b37bbec1e888da9bfe9d58
- git.kernel.org /stable/c/3e5d1bf4bd687beb2cb4e32a07af695455925588
Sources
- CVE List CVE-2026-97904
- NVD CVE-2026-97904
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.