LiveActive security incident?Get immediate response
CVE Record

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

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 ]

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel flaw can corrupt memory when an affected Intel Hardware Feedback Interface system returns from hibernation or deep suspend. The hardware may retain or lose an invalid buffer address and write to unintended memory. This can threaten system confidentiality, integrity, and availability, but requires local access and a qualifying power-management transition.

Executive priority

Prioritize affected Intel Linux endpoints and servers that use hibernation or deep suspend, especially multi-user systems where untrusted local accounts exist. Internet-facing status alone does not drive this risk because the stated attack vector is local. Patch through normal vendor channels promptly, with accelerated handling for systems repeatedly entering affected power states.

Technical view

During resume, the restore kernel can give Intel HFI a newly allocated table buffer. Control then returns to the image kernel while hardware may continue using the restore kernel’s now-invalid buffer. Deep suspend can produce a related address-loss condition. The kernel fix adds syscore callbacks that disable HFI before deep suspend or hibernation and re-enable it during resume.

Likely exposure

Exposure is limited to Linux systems using the affected Intel HFI kernel functionality and deep suspend or hibernation. The supplied record identifies affected kernel releases including 5.18, 6.1.76, 6.6.15, 6.7.3, and 6.8, but does not provide clear distribution-specific package boundaries. Vendor backports may change actual exposure.

Exploitation context

The CVSS 3.1 score is 7.8 with a local, low-privilege vector and no user interaction. The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit. Practical exploitability is not established by these sources.

Researcher notes

The failure is a stale or forgotten hardware buffer address across system-wide power transitions, creating hardware-initiated writes into invalid memory. The record supplies four stable-kernel commits but no CWE, public proof of concept, observed exploitation, or reliable distribution package mapping. Review the relevant branch-specific commit and downstream backport before declaring a system fixed.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix.
  • Check distribution advisories for backported fixes and precise package versions.
  • Until patched, consider avoiding hibernation and deep suspend on potentially affected HFI systems.
  • Follow vendor guidance before changing or disabling production power-management behavior.

Validation and detection

  • Inventory Linux kernel and distribution package versions on Intel systems.
  • Determine whether Intel HFI functionality is present and active.
  • Identify systems permitted to enter hibernation or deep suspend.
  • Confirm the installed kernel includes the applicable stable fix or vendor backport.
  • After updating, test suspend and resume stability under controlled conditions.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26646 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-26646Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1cb19cabeb0e187b6c244d0da73d27f7432c40dc, 1cb19cabeb0e187b6c244d0da73d27f7432c40dc, 1cb19cabeb0e187b6c244d0da73d27f7432c40dc, 1cb19cabeb0e187b6c244d0da73d27f7432c40dcunaffected
LinuxLinux5.18, 0, 6.1.76, 6.6.15, 6.7.3, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.