cpufreq: loongson3: Use raw_smp_processor_id() in do_service_request()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2b7ec33e534f7a10033a5cf07794acf48b182bbe and Kernel 2f78e4a6d2702ac03c2bf2ed3a0e344e1fa9f967.
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]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.11, >=ccf51454145bffd98e31cdbe54a4262473c609e2 <2b7ec33e534f7a10033a5cf07794acf48b182bbe, >=ccf51454145bffd98e31cdbe54a4262473c609e2 <2f78e4a6d2702ac03c2bf2ed3a0e344e1fa9f967 | 2b7ec33e534f7a10033a5cf07794acf48b182bbe, 2f78e4a6d2702ac03c2bf2ed3a0e344e1fa9f967 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket