Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26646thermal: intel: hfi: Add syscore callbacks for system-wide PM

Description

In the Linux kernel, the following vulnerability has been resolved: thermal: intel: hfi: Add syscore callbacks for system-wide PM The kernel allocates a memory buffer and provides its location to the hardware, which uses it to update the HFI table. This allocation occurs during boot and remains constant throughout runtime. When resuming from hibernation, the restore kernel allocates a second memory buffer and reprograms the HFI hardware with the new location as part of a normal boot. The location of the second memory buffer may differ from the one allocated by the image kernel. When the restore kernel transfers control to the image kernel, its HFI buffer becomes invalid, potentially leading to memory corruption if the hardware writes to it (the hardware continues to use the buffer from the restore kernel). It is also possible that the hardware "forgets" the address of the memory buffer when resuming from "deep" suspend. Memory corruption may also occur in such a scenario. To prevent the described memory corruption, disable HFI when preparing to suspend or hibernate. Enable it when resuming. Add syscore callbacks to handle the package of the boot CPU (packages of non-boot CPUs are handled via CPU offline). Syscore ops always run on the boot CPU. Additionally, HFI only needs to be disabled during "deep" suspend and hibernation. Syscore ops only run in these cases. [ rjw: Comment adjustment, subject and changelog edits ]

Timeline

  1. ID reserved

    By Linux

  2. · 36 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26646, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 1cb19cabeb0e187b6c244d0da73d27f7432c40dc – < 28f010dc50df0f7987c04112114fcfa7e0803566
    • affected 1cb19cabeb0e187b6c244d0da73d27f7432c40dc – < 019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee
    • affected 1cb19cabeb0e187b6c244d0da73d27f7432c40dc – < c9d6d63b6c03afaa6f185df249af693a7939577c
    • affected 1cb19cabeb0e187b6c244d0da73d27f7432c40dc – < 97566d09fd02d2ab329774bb89a2cdf2267e86d9
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.76 – ≤ 6.1.*
    • unaffected 6.6.15 – ≤ 6.6.*
    • unaffected 6.7.3 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26646 badge
[![CVE-2024-26646](https://cveledger.app/badge/CVE-2024-26646.svg)](https://cveledger.app/cve/CVE-2024-26646)

Record last updated .