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-44958sched/smt: Fix unbalance sched_smt_present dec/inc

Description

In the Linux kernel, the following vulnerability has been resolved: sched/smt: Fix unbalance sched_smt_present dec/inc I got the following warn report while doing stress test: jump label: negative count! WARNING: CPU: 3 PID: 38 at kernel/jump_label.c:263 static_key_slow_try_dec+0x9d/0xb0 Call Trace: <TASK> __static_key_slow_dec_cpuslocked+0x16/0x70 sched_cpu_deactivate+0x26e/0x2a0 cpuhp_invoke_callback+0x3ad/0x10d0 cpuhp_thread_fun+0x3f5/0x680 smpboot_thread_fn+0x56d/0x8d0 kthread+0x309/0x400 ret_from_fork+0x41/0x70 ret_from_fork_asm+0x1b/0x30 </TASK> Because when cpuset_cpu_inactive() fails in sched_cpu_deactivate(), the cpu offline failed, but sched_smt_present is decremented before calling sched_cpu_deactivate(), it leads to unbalanced dec/inc, so fix it by incrementing sched_smt_present in the error path.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 21 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-44958, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (13 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c5511d03ec090980732e929c318a7a6374b5550e – < 2a3548c7ef2e135aee40e7e5e44e7d11b893e7c4
    • affected c5511d03ec090980732e929c318a7a6374b5550e – < 2cf7665efe451e48d27953e6b5bc627d518c902b
    • affected c5511d03ec090980732e929c318a7a6374b5550e – < 65727331b60197b742089855ac09464c22b96f66
    • affected c5511d03ec090980732e929c318a7a6374b5550e – < d0c87a3c6be10a57aa3463c32c3fc6b2a47c3dab
    • affected c5511d03ec090980732e929c318a7a6374b5550e – < e22f910a26cc2a3ac9c66b8e935ef2a7dd881117
    • affected 01659361c63fdc91c0af239d08cdd211d590a656
    • affected a2c094816f894b7a265851fad858e994fa0f78b3
    • affected 4.14.86 – < 4.15
    • affected 4.19.7 – < 4.20
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.105 – ≤ 6.1.*
    • unaffected 6.6.46 – ≤ 6.6.*
    • unaffected 6.10.5 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .