cpufreq: initialize policy rwsem before sysfs publication
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2fc3384dc75bf7333384c7a16d12c796f61c3f56 · < 27c9b491bf7604e83b50c3bbfa18a30266ff345f| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's cpufreq code publishes policy sysfs attributes before initializing the policy semaphore. A local sysfs access during that window can reach a policy callback before the semaphore is initialized; the input does not specify the resulting impact or whether authentication is required.
Engineers running the Linux kernel should check affected versions; none are specified in the input.