| From bippy-1.1.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-2022-49885: ACPI: APEI: Fix integer overflow in ghes_estatus_pool_init() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ACPI: APEI: Fix integer overflow in ghes_estatus_pool_init() |
| |
| Change num_ghes from int to unsigned int, preventing an overflow |
| and causing subsequent vmalloc() to fail. |
| |
| The overflow happens in ghes_estatus_pool_init() when calculating |
| len during execution of the statement below as both multiplication |
| operands here are signed int: |
| |
| len += (num_ghes * GHES_ESOURCE_PREALLOC_MAX_SIZE); |
| |
| The following call trace is observed because of this bug: |
| |
| [ 9.317108] swapper/0: vmalloc error: size 18446744071562596352, exceeds total pages, mode:0xcc0(GFP_KERNEL), nodemask=(null),cpuset=/,mems_allowed=0-1 |
| [ 9.317131] Call Trace: |
| [ 9.317134] <TASK> |
| [ 9.317137] dump_stack_lvl+0x49/0x5f |
| [ 9.317145] dump_stack+0x10/0x12 |
| [ 9.317146] warn_alloc.cold+0x7b/0xdf |
| [ 9.317150] ? __device_attach+0x16a/0x1b0 |
| [ 9.317155] __vmalloc_node_range+0x702/0x740 |
| [ 9.317160] ? device_add+0x17f/0x920 |
| [ 9.317164] ? dev_set_name+0x53/0x70 |
| [ 9.317166] ? platform_device_add+0xf9/0x240 |
| [ 9.317168] __vmalloc_node+0x49/0x50 |
| [ 9.317170] ? ghes_estatus_pool_init+0x43/0xa0 |
| [ 9.317176] vmalloc+0x21/0x30 |
| [ 9.317177] ghes_estatus_pool_init+0x43/0xa0 |
| [ 9.317179] acpi_hest_init+0x129/0x19c |
| [ 9.317185] acpi_init+0x434/0x4a4 |
| [ 9.317188] ? acpi_sleep_proc_init+0x2a/0x2a |
| [ 9.317190] do_one_initcall+0x48/0x200 |
| [ 9.317195] kernel_init_freeable+0x221/0x284 |
| [ 9.317200] ? rest_init+0xe0/0xe0 |
| [ 9.317204] kernel_init+0x1a/0x130 |
| [ 9.317205] ret_from_fork+0x22/0x30 |
| [ 9.317208] </TASK> |
| |
| [ rjw: Subject and changelog edits ] |
| |
| The Linux kernel CVE team has assigned CVE-2022-49885 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.10.154 with commit 9edf20e5a1d805855e78f241cf221d741b50d482 |
| Fixed in 5.15.78 with commit c50ec15725e005e9fb20bce69b6c23b135a4a9b7 |
| Fixed in 6.0.8 with commit 4c10c854113720cbfe75d4f51db79b700a629e73 |
| Fixed in 6.1 with commit 43d2748394c3feb86c0c771466f5847e274fc043 |
| |
| 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-2022-49885 |
| 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/acpi/apei/ghes.c |
| include/acpi/ghes.h |
| |
| |
| 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/9edf20e5a1d805855e78f241cf221d741b50d482 |
| https://git.kernel.org/stable/c/c50ec15725e005e9fb20bce69b6c23b135a4a9b7 |
| https://git.kernel.org/stable/c/4c10c854113720cbfe75d4f51db79b700a629e73 |
| https://git.kernel.org/stable/c/43d2748394c3feb86c0c771466f5847e274fc043 |
