# CVE-2024-50178: cpufreq: loongson3: Use raw_smp_processor_id() in do_service_request()

> A bug in the Loongson3 cpufreq driver causes kernel errors when using smp_processor_id in preemptible code, potentially leading to system instability or crashes.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-53549, AZL-53796, BELL-CVE-2024-50178, DEBIAN-CVE-2024-50178, GHSA-jggr-hhvm-4c9f, ROOT-OS-UBUNTU-2204-CVE-2024-50178, UBUNTU-CVE-2024-50178

## What is CVE-2024-50178?

CVE-2024-50178 is a medium-severity denial of service vulnerability in Linux kernel, published on 8 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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]

## Which versions are affected by CVE-2024-50178?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-50178?

Apply the vendor's patch.

## Is CVE-2024-50178 being exploited?

There is no known exploitation of CVE-2024-50178 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50178 and fix it if it is affected.

What it is: CVE-2024-50178 is a medium-severity denial of service vulnerability in Linux kernel, published on 8 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50178 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-50178/ (Markdown: https://insights.sbomify.com/CVE-2024-50178/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50178
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50178
- OSV: https://osv.dev/vulnerability/CVE-2024-50178

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50178/
Summaries are generated and may contain mistakes; the official description above is the record.