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 ]
Author | Note |
---|---|
rodrigo-zaiden | USN-6765-1 for linux-oem-6.5 wrongly stated that this CVE was fixed in version 6.5.0-1022.23. The mentioned notice was revoked and the state of the fix for linux-oem-6.5 was recovered to the previous state. |
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 20.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux | < 6.5.0-41.41 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux-aws | < 6.5.0-1021.21 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws-5.15 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws-6.5 | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-azure | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-azure | < any | UNKNOWN |
git.kernel.org/linus/97566d09fd02d2ab329774bb89a2cdf2267e86d9 (6.8-rc1)
git.kernel.org/stable/c/019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee
git.kernel.org/stable/c/28f010dc50df0f7987c04112114fcfa7e0803566
git.kernel.org/stable/c/97566d09fd02d2ab329774bb89a2cdf2267e86d9
git.kernel.org/stable/c/c9d6d63b6c03afaa6f185df249af693a7939577c
launchpad.net/bugs/cve/CVE-2024-26646
nvd.nist.gov/vuln/detail/CVE-2024-26646
security-tracker.debian.org/tracker/CVE-2024-26646
ubuntu.com/security/notices/USN-6818-1
ubuntu.com/security/notices/USN-6818-2
ubuntu.com/security/notices/USN-6818-3
ubuntu.com/security/notices/USN-6818-4
ubuntu.com/security/notices/USN-6819-1
ubuntu.com/security/notices/USN-6819-2
ubuntu.com/security/notices/USN-6819-3
ubuntu.com/security/notices/USN-6819-4
www.cve.org/CVERecord?id=CVE-2024-26646