CVE-2024-27006

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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+ # 6.8+

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

May 1, 2024

Last Modified

November 4, 2025

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-38.38) @ noble2026-05-24ubuntu
ubuntulinux-tools-nvidia-64k (6.8.0-1009.9) @ noble2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1008.8) @ noble2026-05-24ubuntu
ubuntulinux-tools-aws (6.8.0-1011.12) @ noble2026-05-24ubuntu
linuxKernel @ 6.8.8osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 126 total refreshes for this CVE.

  1. 2026-08-06 13:45 UTCEPSS rescore
  2. 2026-08-05 19:15 UTCEPSS rescore
  3. 2026-08-04 15:08 UTCEPSS rescore
  4. 2026-08-04 10:36 UTCEPSS rescore
  5. 2026-08-03 10:34 UTCEPSS rescore
  6. 2026-08-02 02:25 UTCEPSS rescore
  7. 2026-08-02 02:25 UTCEPSS rescore
  8. 2026-08-01 05:36 UTCOSV refresh
  9. 2026-08-01 04:14 UTCEPSS rescore
  10. 2026-07-30 16:26 UTCEPSS rescore
  11. 2026-07-30 01:29 UTCEPSS rescore
  12. 2026-07-28 15:34 UTCEPSS rescore
  13. 2026-07-27 14:11 UTCEPSS rescore
  14. 2026-07-26 14:53 UTCEPSS rescore
  15. 2026-07-25 14:16 UTCEPSS rescore
  16. 2026-07-24 14:16 UTCEPSS rescore
  17. 2026-07-23 14:17 UTCEPSS rescore
  18. 2026-07-23 14:17 UTCEPSS rescore
  19. 2026-07-23 02:35 UTCEG score recompute
  20. 2026-07-22 14:07 UTCEPSS rescore
  21. 2026-07-21 15:23 UTCEPSS rescore
  22. 2026-07-21 15:23 UTCEPSS rescore
  23. 2026-07-20 17:06 UTCEPSS rescore
  24. 2026-07-19 14:30 UTCEPSS rescore
  25. 2026-07-19 14:30 UTCEPSS rescore
Show 75 more
  1. 2026-07-19 02:28 UTCEPSS rescore
  2. 2026-07-19 02:28 UTCEPSS rescore
  3. 2026-07-18 10:03 UTCEPSS rescore
  4. 2026-07-18 10:03 UTCEPSS rescore
  5. 2026-07-15 16:56 UTCEPSS rescore
  6. 2026-07-15 16:56 UTCEPSS rescore
  7. 2026-07-15 01:59 UTCEPSS rescore
  8. 2026-07-15 01:59 UTCEPSS rescore
  9. 2026-07-14 12:55 UTCOSV refresh
  10. 2026-07-13 06:11 UTCEPSS rescore
  11. 2026-07-13 06:11 UTCEPSS rescore
  12. 2026-07-12 05:45 UTCEPSS rescore
  13. 2026-07-11 08:26 UTCEPSS rescore
  14. 2026-07-09 19:09 UTCEPSS rescore
  15. 2026-07-09 19:09 UTCEPSS rescore
  16. 2026-07-08 15:13 UTCEPSS rescore
  17. 2026-07-07 13:45 UTCEPSS rescore
  18. 2026-07-07 13:45 UTCEPSS rescore
  19. 2026-07-06 16:26 UTCEPSS rescore
  20. 2026-07-06 02:22 UTCEPSS rescore
  21. 2026-07-06 02:22 UTCEPSS rescore
  22. 2026-07-05 02:29 UTCEPSS rescore
  23. 2026-07-04 06:30 UTCEPSS rescore
  24. 2026-07-01 15:05 UTCEPSS rescore
  25. 2026-06-30 23:21 UTCEPSS rescore
  26. 2026-06-30 23:21 UTCEPSS rescore
  27. 2026-06-29 14:05 UTCEPSS rescore
  28. 2026-06-28 14:06 UTCEPSS rescore
  29. 2026-06-28 14:06 UTCEPSS rescore
  30. 2026-06-28 04:55 UTCEPSS rescore
  31. 2026-06-28 04:55 UTCEPSS rescore
  32. 2026-06-27 03:07 UTCEPSS rescore
  33. 2026-06-27 03:07 UTCEPSS rescore
  34. 2026-06-26 13:37 UTCOSV refresh
  35. 2026-06-25 13:48 UTCEPSS rescore
  36. 2026-06-25 13:48 UTCEPSS rescore
  37. 2026-06-24 14:04 UTCEPSS rescore
  38. 2026-06-24 14:04 UTCEPSS rescore
  39. 2026-06-23 21:32 UTCEPSS rescore
  40. 2026-06-23 21:32 UTCEPSS rescore
  41. 2026-06-22 14:24 UTCEPSS rescore
  42. 2026-06-22 14:24 UTCEPSS rescore
  43. 2026-06-21 14:55 UTCEPSS rescore
  44. 2026-06-21 14:55 UTCEPSS rescore
  45. 2026-06-21 01:58 UTCEPSS rescore
  46. 2026-06-21 01:58 UTCEPSS rescore
  47. 2026-06-19 19:24 UTCEPSS rescore
  48. 2026-06-19 19:24 UTCEPSS rescore
  49. 2026-06-18 17:51 UTCEPSS rescore
  50. 2026-06-18 17:51 UTCEPSS rescore
  51. 2026-06-17 17:52 UTCEPSS rescore
  52. 2026-06-17 17:52 UTCEPSS rescore
  53. 2026-06-16 17:51 UTCEPSS rescore
  54. 2026-06-16 17:51 UTCEPSS rescore
  55. 2026-06-15 17:47 UTCEPSS rescore
  56. 2026-06-14 23:16 UTCEPSS rescore
  57. 2026-06-13 22:59 UTCEPSS rescore
  58. 2026-06-13 22:59 UTCEPSS rescore
  59. 2026-06-12 23:11 UTCEPSS rescore
  60. 2026-06-11 13:59 UTCEPSS rescore
  61. 2026-06-11 13:59 UTCEPSS rescore
  62. 2026-06-10 22:17 UTCEPSS rescore
  63. 2026-06-10 13:21 UTCEPSS rescore
  64. 2026-06-10 13:21 UTCEPSS rescore
  65. 2026-06-08 20:11 UTCOSV refresh
  66. 2026-06-08 14:16 UTCEPSS rescore
  67. 2026-06-08 14:16 UTCEPSS rescore
  68. 2026-06-07 15:24 UTCEPSS rescore
  69. 2026-06-07 15:24 UTCEPSS rescore
  70. 2026-06-06 13:46 UTCEPSS rescore
  71. 2026-06-06 13:46 UTCEPSS rescore
  72. 2026-06-05 22:46 UTCEPSS rescore
  73. 2026-06-05 22:46 UTCEPSS rescore
  74. 2026-06-05 06:09 UTCEPSS rescore
  75. 2026-06-05 06:09 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-27006?
CVE-2024-27006 is a medium vulnerability published on May 1, 2024. In the Linux kernel, the following vulnerability has been resolved: thermal/debugfs: Add missing count increment to thermaldebugtztripup() 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…
When was CVE-2024-27006 disclosed?
CVE-2024-27006 was first published in the National Vulnerability Database on May 1, 2024, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-27006 actively exploited?
CVE-2024-27006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.6% of all scored CVEs.
What is the CVSS score of CVE-2024-27006?
CVE-2024-27006 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-27006?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-27006, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-27006

Explore →

Is Your Infrastructure Affected by CVE-2024-27006?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.