diff options
| author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-02-08 18:46:32 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-02-08 18:46:32 +0000 |
| commit | faaf92d8971442ea600e4b76fc4a0c8c49e8902f (patch) | |
| tree | 035db14c3ec54b9a25668587820bccc017530b5b | |
| parent | a4520f48194d05b2425bf6633bd4a7775cb57928 (diff) | |
| download | vulns-faaf92d8971442ea600e4b76fc4a0c8c49e8902f.tar.gz | |
cve/published: update the generated .json and mbox test file
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| -rw-r--r-- | cve/published/2024/CVE-2024-0052.json | 2 | ||||
| -rw-r--r-- | cve/published/2024/CVE-2024-0052.mbox | 34 |
2 files changed, 35 insertions, 1 deletions
diff --git a/cve/published/2024/CVE-2024-0052.json b/cve/published/2024/CVE-2024-0052.json index 2f1660fb..16073c63 100644 --- a/cve/published/2024/CVE-2024-0052.json +++ b/cve/published/2024/CVE-2024-0052.json @@ -43,7 +43,7 @@ ], "title": "mm/memory_hotplug: fix memmap_on_memory sysfs value retrieval", "x_generator": { - "engine": "bippy-a5d23ba552f0" + "engine": "bippy-a4520f48194d" } } }, diff --git a/cve/published/2024/CVE-2024-0052.mbox b/cve/published/2024/CVE-2024-0052.mbox index e69de29b..fa7a1ea0 100644 --- a/cve/published/2024/CVE-2024-0052.mbox +++ b/cve/published/2024/CVE-2024-0052.mbox @@ -0,0 +1,34 @@ +From: Linux Kernel CVE team <cve@kernel.org> +Subject: CVE-2024-0052: mm/memory_hotplug: fix memmap_on_memory sysfs value retrieval + +CVE-2024-0052 has been assigned for the following issue: + +mm/memory_hotplug: fix memmap_on_memory sysfs value retrieval + +set_memmap_mode() stores the kernel parameter memmap mode as an integer. +However, the get_memmap_mode() function utilizes param_get_bool() to fetch +the value as a boolean, leading to potential endianness issue. On +Big-endian architectures, the memmap_on_memory is consistently displayed +as 'N' regardless of its actual status. + +To address this endianness problem, the solution involves obtaining the +mode as an integer. This adjustment ensures the proper display of the +memmap_on_memory parameter, presenting it as one of the following options: +Force, Y, or N. + +Link: https://lkml.kernel.org/r/20240110140127.241451-1-sumanthk@linux.ibm.com +Fixes: 2d1f649c7c08 ("mm/memory_hotplug: support memmap_on_memory when memmap is not aligned to pageblocks") +Signed-off-by: Sumanth Korikkar <sumanthk@linux.ibm.com> +Suggested-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com> +Acked-by: David Hildenbrand <david@redhat.com> +Cc: Alexander Gordeev <agordeev@linux.ibm.com> +Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com> +Cc: Heiko Carstens <hca@linux.ibm.com> +Cc: Michal Hocko <mhocko@suse.com> +Cc: Oscar Salvador <osalvador@suse.de> +Cc: Vasily Gorbik <gor@linux.ibm.com> +Cc: <stable@vger.kernel.org> [6.6+] +Signed-off-by: Andrew Morton <akpm@linux-foundation.org> + +Affected versions: + |