CVE-2024-27002: clk: mediatek: Do a runtime PM get on controllers during probe
Published May 1, 2024
·Updated
clk: mediatek: Do a runtime PM get on controllers during probe
Affected Software
10 affected componentsFixes available
Linux Linux kernel>=5.2<6.1.88
Linux Linux kernel>=6.2<6.6.29
Linux Linux kernel>=6.7<6.8.8
Linux Linux kernel=6.9-rc1
Linux Linux kernel=6.9-rc2
Linux Linux kernel=6.9-rc3
Linux Linux kernel=6.9-rc4
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.22-16.12.25-1
Microsoft azl3 hyperv-daemons 6.6.22.1-2
Microsoft azl3 hyperv-daemons 6.6.35.1-1
Remediation
Event History
May 1, 2024
CVE Published
via MITRE·05:28 AM
Data Sourced
via MITRE·05:28 AM
Description
Data Sourced
via NVD·06:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
May 13, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
Description
Jul 11, 2024
Data Sourced
via Launchpad·07:45 PM
Description
Apr 27, 2025
Data Sourced
via Ubuntu·12:16 AM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-27002?
CVE-2024-27002 is classified as a vulnerability that can cause a deadlock during the probing stage of the Linux kernel.
2
How do I fix CVE-2024-27002?
To fix CVE-2024-27002, upgrade to a patched version of the Linux kernel, such as 6.1.123-1 or later.
3
Which Linux kernel versions are affected by CVE-2024-27002?
CVE-2024-27002 affects Linux kernel versions from 5.2 up to but not including 6.1.
4
What components of the Linux kernel are involved in CVE-2024-27002?
CVE-2024-27002 involves the clk subsystem and specifically the mediatek platform, which experiences a deadlock.
5
Is there a known mitigation for CVE-2024-27002?
There is no specific mitigation for CVE-2024-27002 other than applying the recommended kernel upgrades.