| 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-53107: fs/proc/task_mmu: prevent integer overflow in pagemap_scan_get_args() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| fs/proc/task_mmu: prevent integer overflow in pagemap_scan_get_args() |
| |
| The "arg->vec_len" variable is a u64 that comes from the user at the start |
| of the function. The "arg->vec_len * sizeof(struct page_region))" |
| multiplication can lead to integer wrapping. Use size_mul() to avoid |
| that. |
| |
| Also the size_add/mul() functions work on unsigned long so for 32bit |
| systems we need to ensure that "arg->vec_len" fits in an unsigned long. |
| |
| The Linux kernel CVE team has assigned CVE-2024-53107 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.7 with commit 52526ca7fdb905a768a93f8faa418e9b988fc34b and fixed in 6.11.10 with commit adee03f8903c58a6a559f21388a430211fac8ce9 |
| Issue introduced in 6.7 with commit 52526ca7fdb905a768a93f8faa418e9b988fc34b and fixed in 6.12 with commit 669b0cb81e4e4e78cff77a5b367c7f70c0c6c05e |
| |
| 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-53107 |
| 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: |
| fs/proc/task_mmu.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/adee03f8903c58a6a559f21388a430211fac8ce9 |
| https://git.kernel.org/stable/c/669b0cb81e4e4e78cff77a5b367c7f70c0c6c05e |
