| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-26646: thermal: 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 ] |
| |
| The Linux kernel CVE team has assigned CVE-2024-26646 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.18 with commit 1cb19cabeb0e187b6c244d0da73d27f7432c40dc and fixed in 6.1.76 with commit 28f010dc50df0f7987c04112114fcfa7e0803566 |
| Issue introduced in 5.18 with commit 1cb19cabeb0e187b6c244d0da73d27f7432c40dc and fixed in 6.6.15 with commit 019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee |
| Issue introduced in 5.18 with commit 1cb19cabeb0e187b6c244d0da73d27f7432c40dc and fixed in 6.7.3 with commit c9d6d63b6c03afaa6f185df249af693a7939577c |
| Issue introduced in 5.18 with commit 1cb19cabeb0e187b6c244d0da73d27f7432c40dc and fixed in 6.8 with commit 97566d09fd02d2ab329774bb89a2cdf2267e86d9 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-26646 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/thermal/intel/intel_hfi.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/28f010dc50df0f7987c04112114fcfa7e0803566 |
| https://git.kernel.org/stable/c/019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee |
| https://git.kernel.org/stable/c/c9d6d63b6c03afaa6f185df249af693a7939577c |
| https://git.kernel.org/stable/c/97566d09fd02d2ab329774bb89a2cdf2267e86d9 |
