CVE-2024-26646
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2024-26646
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26646.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2024-26646
- Downstream
- Related
- Published
- 2024-03-26T17:50:00Z
- Modified
- 2025-10-21T19:18:06.493955Z
- Summary
- thermal: intel: hfi: Add syscore callbacks for system-wide PM
- Details
-
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 ]
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee
- https://git.kernel.org/stable/c/28f010dc50df0f7987c04112114fcfa7e0803566
- https://git.kernel.org/stable/c/97566d09fd02d2ab329774bb89a2cdf2267e86d9
- https://git.kernel.org/stable/c/c9d6d63b6c03afaa6f185df249af693a7939577c
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1cb19cabeb0e187b6c244d0da73d27f7432c40dcFixed28f010dc50df0f7987c04112114fcfa7e0803566
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1cb19cabeb0e187b6c244d0da73d27f7432c40dcFixed019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1cb19cabeb0e187b6c244d0da73d27f7432c40dcFixedc9d6d63b6c03afaa6f185df249af693a7939577c
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1cb19cabeb0e187b6c244d0da73d27f7432c40dcFixed97566d09fd02d2ab329774bb89a2cdf2267e86d9