CVE-2024-26646

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

MEDIUM
5.5
CVSS Score
Published: March 26, 2024 at 05:50 PM UTC
Updated: August 5, 2026 at 12:04 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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 ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 6.1.765.18 ≤ v < 6.1.765.18 ≤ v < 6.6.155.18 ≤ v < 6.7.35.18 ≤ v < 6.86.2 ≤ v < 6.6.156.7 ≤ v < 6.7.31cb19cabeb0e187b6c244d0da73d27f7432c40dc5.18
Vendor states this is fixed in 019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee (fixed)
Vendor states this is fixed in 28f010dc50df0f7987c04112114fcfa7e0803566 (fixed)
Vendor states this is fixed in 97566d09fd02d2ab329774bb89a2cdf2267e86d9 (fixed)
Vendor states this is fixed in c9d6d63b6c03afaa6f185df249af693a7939577c (fixed)
Vendor states this is fixed in 5.18 (unaffected)
Vendor states this is fixed in 6.1.76 (unaffected)
Vendor states this is fixed in 6.6.15 (unaffected)
Vendor states this is fixed in 6.7.3 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/28f010dc50df0f7987c04112114fcfa7e0803566
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/97566d09fd02d2ab329774bb89a2cdf2267e86d9
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c9d6d63b6c03afaa6f185df249af693a7939577c

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card