- Vulnerability/
- CVE-2024-57917
CVE-2024-57917: topology: Keep the cpumask unchanged when printing cpumap
First published: Sun Jan 19 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: topology: Keep the cpumask unchanged when printing cpumap During fuzz testing, the following warning was discovered: different return values (15 and 11) from vsnprintf("%*pbl ", ...) test:keyward is WARNING in kvasprintf WARNING: CPU: 55 PID: 1168477 at lib/kasprintf.c:30 kvasprintf+0x121/0x130 Call Trace: kvasprintf+0x121/0x130 kasprintf+0xa6/0xe0 bitmap_print_to_buf+0x89/0x100 core_siblings_list_read+0x7e/0xb0 kernfs_file_read_iter+0x15b/0x270 new_sync_read+0x153/0x260 vfs_read+0x215/0x290 ksys_read+0xb9/0x160 do_syscall_64+0x56/0x100 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The call trace shows that kvasprintf() reported this warning during the printing of core_siblings_list. kvasprintf() has several steps: (1) First, calculate the length of the resulting formatted string. (2) Allocate a buffer based on the returned length. (3) Then, perform the actual string formatting. (4) Check whether the lengths of the formatted strings returned in steps (1) and (2) are consistent. If the core_cpumask is modified between steps (1) and (3), the lengths obtained in these two steps may not match. Indeed our test includes cpu hotplugging, which should modify core_cpumask while printing. To fix this issue, cache the cpumask into a temporary variable before calling cpumap_print_{list, cpumask}_to_buf(), to keep it unchanged during the printing process.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.128-1 6.12.20-1 6.12.21-1 | |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/1c7818e2746e747838a3de1687e89eac7b947f08
- https://git.kernel.org/stable/c/360596e7fe319a5db1b5fb34a3952862ae53c924
- https://git.kernel.org/stable/c/b02cf1d27e460ab2b3e1c8c9ce472d562cad2e8d
- https://git.kernel.org/stable/c/ca47e933a900492d89dcf5db18a99c28bd4a742d
- https://git.kernel.org/stable/c/cbd399f78e23ad4492c174fc5e6b3676dba74a52
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57917
- https://nvd.nist.gov/vuln/detail/CVE-2024-57917
- https://launchpad.net/bugs/cve/CVE-2024-57917
- https://security-tracker.debian.org/tracker/CVE-2024-57917
- https://ubuntu.com/security/CVE-2024-57917
- https://git.kernel.org/linus/cbd399f78e23ad4492c174fc5e6b3676dba74a52
Frequently Asked Questions
What is the severity of CVE-2024-57917?
The severity of CVE-2024-57917 is currently rated as low due to its limited impact.
How do I fix CVE-2024-57917?
To fix CVE-2024-57917, update your Linux kernel to the latest patched version that resolves this vulnerability.
Which versions of Linux Kernel are affected by CVE-2024-57917?
CVE-2024-57917 affects various versions of the Linux Kernel, and it is best to check your specific version against the advisory.
What impact does CVE-2024-57917 have on system performance?
CVE-2024-57917 has no significant impact on system performance as it primarily addresses a warning during fuzz testing.
Is CVE-2024-57917 publicly known?
Yes, CVE-2024-57917 is a publicly known vulnerability in the Linux kernel.
- agent/type
- agent/first-publish-date
- agent/title
- agent/author
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- collector/mitre-cve
- source/MITRE
- collector/usn-cve
- source/Ubuntu
- agent/guess-ai
- agent/software-canonical-lookup
- collector/nvd-cve
- collector/security-tracker-debian
- source/Debian
- agent/references
- agent/source
- agent/softwarecombine
- agent/description
- agent/event
- agent/tags
- collector/launchpad-cve
- source/Launchpad
- vendor/linux
- canonical/linux kernel
- package-manager/debian