| 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-26817: amdkfd: use calloc instead of kzalloc to avoid integer overflow |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| amdkfd: use calloc instead of kzalloc to avoid integer overflow |
| |
| This uses calloc instead of doing the multiplication which might |
| overflow. |
| |
| The Linux kernel CVE team has assigned CVE-2024-26817 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 4.19.312 with commit e6721ea845fcb93a764a92bd40f1afc0d6c69751 |
| Fixed in 5.4.274 with commit 8b0564704255c6b3c6a7188e86939f754e1577c0 |
| Fixed in 5.10.215 with commit fcbd99b3c73309107e3be71f20dff9414df64f91 |
| Fixed in 5.15.155 with commit cbac7de1d9901521e78cdc34e15451df3611f2ad |
| Fixed in 6.1.86 with commit e6768c6737f4c02cba193a3339f0cc2907f0b86a |
| Fixed in 6.6.27 with commit 315eb3c2df7e4cb18e3eacfa18a53a46f2bf0ef7 |
| Fixed in 6.8.6 with commit 0c33d11153949310d76631d8f4a4736519eacd3a |
| Fixed in 6.9 with commit 3b0daecfeac0103aba8b293df07a0cbaf8b43f29 |
| |
| 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-26817 |
| 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/gpu/drm/amd/amdkfd/kfd_chardev.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/e6721ea845fcb93a764a92bd40f1afc0d6c69751 |
| https://git.kernel.org/stable/c/8b0564704255c6b3c6a7188e86939f754e1577c0 |
| https://git.kernel.org/stable/c/fcbd99b3c73309107e3be71f20dff9414df64f91 |
| https://git.kernel.org/stable/c/cbac7de1d9901521e78cdc34e15451df3611f2ad |
| https://git.kernel.org/stable/c/e6768c6737f4c02cba193a3339f0cc2907f0b86a |
| https://git.kernel.org/stable/c/315eb3c2df7e4cb18e3eacfa18a53a46f2bf0ef7 |
| https://git.kernel.org/stable/c/0c33d11153949310d76631d8f4a4736519eacd3a |
| https://git.kernel.org/stable/c/3b0daecfeac0103aba8b293df07a0cbaf8b43f29 |
