CVE-2024-27002

System hang via inverted probe lock order

Published May 1, 2024 · Updated May 11, 2026

Improper locking in the Linux kernel 5.2 through 6.9-rc4 allows local users to hang systems during MediaTek controller probing. During controller probe, clk_register() takes clk_prepare_lock and then requests runtime power management, while power-off holds genpd_lock and calls clk_unprepare(), producing an inverted lock order. Exploitation requires local low-privilege access and a MediaTek clock controller with the mutual generic-power-domain dependency; the resulting deadlock denies availability.

CVSS severity5.5
Medium
EPSS probability0.17%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper locking in the Linux kernel 5.2 through 6.9-rc4 allows local users to hang systems during MediaTek controller probing. During controller probe, clk_register() takes clk_prepare_lock and then requests runtime power management, while power-off holds genpd_lock and calls clk_unprepare(), producing an inverted lock order. Exploitation requires local low-privilege access and a MediaTek clock controller with the mutual generic-power-domain dependency; the resulting deadlock denies availability.

The record

CVE
CVE-2024-27002
Published
May 1, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-667, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 1, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.2
  2. Affected versionversion=acddfc2c261b3653ab1c1b567a427299bac20d31 <165d226472575b213dd90dfda19d1605dd7c19a8
  3. Affected versionversion=acddfc2c261b3653ab1c1b567a427299bac20d31 <2f7b1d8b5505efb0057cd1ab85fca206063ea4c3
  4. Affected versionversion=acddfc2c261b3653ab1c1b567a427299bac20d31 <b62ed25feb342eab052822eff0c554873799a4f5
  5. Affected versionversion=acddfc2c261b3653ab1c1b567a427299bac20d31 <c0dcd5c072e2a3fff886f673e6a5d9bf8090c4cc

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.2; version=acddfc2c261b3653ab1c1b567a427299bac20d31 <165d226472575b213dd90dfda19d1605dd7c19a8; version=acddfc2c261b3653ab1c1b567a427299bac20d31 <2f7b1d8b5505efb0057cd1ab85fca206063ea4c3; version=acddfc2c261b3653ab1c1b567a427299bac20d31 <b62ed25feb342eab052822eff0c554873799a4f5; version=acddfc2c261b3653ab1c1b567a427299bac20d31 <c0dcd5c072e2a3fff886f673e6a5d9bf8090c4cc

Published CVSS scores

5.5NISTCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-667Improper Locking
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo