CVEvulnerability
CVE-2024-26646
5.5 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2024-03-26
- Last modified
- 2026-08-04
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-770
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 configurations
• linux linux kernel (< 6.1.76)
• linux linux kernel (>= 6.2 < 6.6.15)
• linux linux kernel (>= 6.7 < 6.7.3)
Related
Weakness · CWE (1)
- CWE-770 Allocation of Resources Without Limits or Throttling weakness
References
- https://git.kernel.org/stable/c/019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee Patch
- https://git.kernel.org/stable/c/28f010dc50df0f7987c04112114fcfa7e0803566 Patch
- https://git.kernel.org/stable/c/97566d09fd02d2ab329774bb89a2cdf2267e86d9 Patch
- https://git.kernel.org/stable/c/c9d6d63b6c03afaa6f185df249af693a7939577c Patch
- https://git.kernel.org/stable/c/019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee Patch
- https://git.kernel.org/stable/c/28f010dc50df0f7987c04112114fcfa7e0803566 Patch
- https://git.kernel.org/stable/c/97566d09fd02d2ab329774bb89a2cdf2267e86d9 Patch
- https://git.kernel.org/stable/c/c9d6d63b6c03afaa6f185df249af693a7939577c Patch