CVE-2024-50178: cpufreq: loongson3: Use raw_smp_processor_id() in do_service_request()
First published: Fri Nov 08 2024(Updated: )
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]
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | <6.11.3 | |
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.15-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/2f78e4a6d2702ac03c2bf2ed3a0e344e1fa9f967
- https://git.kernel.org/stable/c/2b7ec33e534f7a10033a5cf07794acf48b182bbe
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50178
- https://nvd.nist.gov/vuln/detail/CVE-2024-50178
- https://launchpad.net/bugs/cve/CVE-2024-50178
- https://security-tracker.debian.org/tracker/CVE-2024-50178
- https://ubuntu.com/security/CVE-2024-50178
- https://git.kernel.org/linus/2b7ec33e534f7a10033a5cf07794acf48b182bbe
Frequently Asked Questions
What is the severity of CVE-2024-50178?
CVE-2024-50178 has been classified as a medium severity vulnerability.
How do I fix CVE-2024-50178?
To fix CVE-2024-50178, update your Linux kernel to version 6.11.3 or later.
Which versions of the Linux kernel are affected by CVE-2024-50178?
CVE-2024-50178 affects all versions of the Linux kernel prior to 6.11.3.
What component of the Linux kernel is impacted by CVE-2024-50178?
CVE-2024-50178 impacts the cpufreq subsystem specifically related to the loongson3 architecture.
Is there a workaround for CVE-2024-50178 before patching?
There are no known workarounds for CVE-2024-50178; upgrading the kernel is recommended.
- agent/title
- agent/references
- agent/first-publish-date
- agent/type
- agent/description
- agent/author
- agent/event
- agent/remedy
- agent/severity
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- collector/nvd-cve
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- package-manager/debian