Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 22 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-57917, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 – < 1c7818e2746e747838a3de1687e89eac7b947f08
    • affected bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 – < ca47e933a900492d89dcf5db18a99c28bd4a742d
    • affected bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 – < b02cf1d27e460ab2b3e1c8c9ce472d562cad2e8d
    • affected bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 – < 360596e7fe319a5db1b5fb34a3952862ae53c924
    • affected bb9ec13d156e85dfd6a8afd0bb61ccf5736ed257 – < cbd399f78e23ad4492c174fc5e6b3676dba74a52
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.177 – ≤ 5.15.*
    • unaffected 6.1.125 – ≤ 6.1.*
    • unaffected 6.6.72 – ≤ 6.6.*
    • unaffected 6.12.10 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-57917 badge
[![CVE-2024-57917](https://cveledger.app/badge/CVE-2024-57917.svg)](https://cveledger.app/cve/CVE-2024-57917)

Record last updated .