CVE-2024-27006 Details
Description
In the Linux kernel, the following vulnerability has been resolved: thermal/debugfs: Add missing count increment to thermal_debug_tz_trip_up() The count field in struct trip_stats, representing the number of times the zone temperature was above the trip point, needs to be incremented in thermal_debug_tz_trip_up(), for two reasons. First, if a trip point is crossed on the way up for the first time, thermal_debug_update_temp() called from update_temperature() does not see it because it has not been added to trips_crossed[] array in the thermal zone's struct tz_debugfs object yet. Therefore, when thermal_debug_tz_trip_up() is called after that, the trip point's count value is 0, and the attempt to divide by it during the average temperature computation leads to a divide error which causes the kernel to crash. Setting the count to 1 before the division by incrementing it fixes this problem. Second, if a trip point is crossed on the way up, but it has been crossed on the way up already before, its count value needs to be incremented to make a record of the fact that the zone temperature is above the trip now. Without doing that, if the mitigations applied after crossing the trip cause the zone temperature to drop below its threshold, the count will not be updated for this episode at all and the average temperature in the trip statistics record will be somewhat higher than it should be. Cc :6.8+ <[email protected]> # 6.8+
A vulnerability exists in the Linux kernel's thermal debug filesystem that can lead to a kernel crash. The issue arises because the count of how many times a thermal zone's temperature has exceeded a trip point is not properly updated. When the temperature crosses a trip point for the first time, the corresponding count is zero. This causes a division error during temperature average calculations, leading to a kernel crash. Additionally, the lack of proper count management can result in inaccurate temperature statistics, as episodes of temperature fluctuations may not be recorded correctly.
Users can upgrade to the latest Fedora kernel version to address this vulnerability. Instructions for upgrading are available in the Fedora update notifications for versions 38, 39, and 40.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 14, 2024References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.8, < 6.8.8 6.9 rc1 6.9 rc2 6.9 rc3 6.9 rc4 |
CPE
Remediation
| |
Change History
10 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 4, 2025 | CVE Modified | CVE |
| Sep 18, 2025 | Initial Analysis | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| May 29, 2024 | CVE Modified | kernel.org |
| May 14, 2024 | CVE Modified | kernel.org |
| May 13, 2024 | CVE Modified | kernel.org |
| May 3, 2024 | CVE Modified | kernel.org |
| May 1, 2024 | New CVE Received | kernel.org |