# CVE-2024-27002: clk: mediatek: Do a runtime PM get on controllers during probe

> A deadlock in the MediaTek clock driver during probe causes a system hang, requiring a kernel patch to resolve the locking order issue.

- **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:** 1 May 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-54592, BELL-CVE-2024-27002, DEBIAN-CVE-2024-27002, GHSA-437h-4cv6-6q92, ROOT-OS-DEBIAN-11-CVE-2024-27002, ROOT-OS-UBUNTU-2204-CVE-2024-27002, UBUNTU-CVE-2024-27002

## What is CVE-2024-27002?

CVE-2024-27002 is a medium-severity vulnerability in Linux kernel, published on 1 May 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:

clk: mediatek: Do a runtime PM get on controllers during probe

mt8183-mfgcfg has a mutual dependency with genpd during the probing
stage, which leads to a deadlock in the following call stack:

CPU0:  genpd_lock --> clk_prepare_lock
genpd_power_off_work_fn()
 genpd_lock()
 generic_pm_domain::power_off()
    clk_unprepare()
      clk_prepare_lock()

CPU1: clk_prepare_lock --> genpd_lock
clk_register()
  __clk_core_init()
    clk_prepare_lock()
    clk_pm_runtime_get()
      genpd_lock()

Do a runtime PM get at the probe function to make sure clk_register()
won't acquire the genpd lock. Instead of only modifying mt8183-mfgcfg,
do this on all mediatek clock controller probings because we don't
believe this would cause any regression.

Verified on MT8183 and MT8192 Chromebooks.

Weakness: CWE-667 (Improper Locking)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-27002 being exploited?

There is no known exploitation of CVE-2024-27002 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-27002 and fix it if it is affected.

What it is: CVE-2024-27002 is a medium-severity vulnerability in Linux kernel, published on 1 May 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-27002 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-27002/ (Markdown: https://insights.sbomify.com/CVE-2024-27002/index.md)
```

## Sources

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

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