cpufreq: loongson3: Use raw_smp_processor_id() in do_service_request()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: loongson3: Use raw_smp_processor_id() in do_service_request()
Use raw_smp_processor_id() instead of plain smp_processor_id() in do_service_request(), otherwise we may get some errors with the driver enabled:
BUG: using smp_processor_id() in preemptible [00000000] code: (udev-worker)/208 caller is loongson3_cpufreq_probe+0x5c/0x250 [loongson3_cpufreq]
From the CVE record · Linux
The Linux kernel's loongson3 cpufreq driver can report an smp_processor_id() error during driver probing when the driver is enabled. The input does not describe an attacker capability or specify network access, authentication, or user interaction conditions.
Engineers running the Linux kernel with the loongson3 cpufreq driver enabled should check their systems; affected versions are not specified.