| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-53072: platform/x86/amd/pmc: Detect when STB is not available |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| platform/x86/amd/pmc: Detect when STB is not available |
| |
| Loading the amd_pmc module as: |
| |
| amd_pmc enable_stb=1 |
| |
| ...can result in the following messages in the kernel ring buffer: |
| |
| amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff |
| ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff |
| WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340 |
| |
| Further debugging reveals that this occurs when the requests for |
| S2D_PHYS_ADDR_LOW and S2D_PHYS_ADDR_HIGH return a value of 0, |
| indicating that the STB is inaccessible. To prevent the ioremap |
| warning and provide clarity to the user, handle the invalid address |
| and display an error message. |
| |
| The Linux kernel CVE team has assigned CVE-2024-53072 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.18 with commit 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d and fixed in 6.1.117 with commit a50863dd1f92d43c975ab2ecc3476617fe98a66e |
| Issue introduced in 5.18 with commit 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d and fixed in 6.6.61 with commit 7a3ed3f125292bc3398e04d10108124250892e3f |
| Issue introduced in 5.18 with commit 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d and fixed in 6.11.8 with commit 67ff30e24a0466bdd5be1d0b84385ec3c85fdacd |
| Issue introduced in 5.18 with commit 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d and fixed in 6.12 with commit bceec87a73804bb4c33b9a6c96e2d27cd893a801 |
| |
| 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-53072 |
| 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/platform/x86/amd/pmc/pmc.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/a50863dd1f92d43c975ab2ecc3476617fe98a66e |
| https://git.kernel.org/stable/c/7a3ed3f125292bc3398e04d10108124250892e3f |
| https://git.kernel.org/stable/c/67ff30e24a0466bdd5be1d0b84385ec3c85fdacd |
| https://git.kernel.org/stable/c/bceec87a73804bb4c33b9a6c96e2d27cd893a801 |