Cyber Resilience

CVE-2024-44958

Linux Kernel 4.14.86 – 4.15

Published
04 September 2024
Modified
03 November 2025
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0021 12th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2024-44958 is a medium-severity an unspecified weakness vulnerability in Linux Linux Kernel. Its CVSS base score is 5.5 (Medium).

Operationally, ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

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>…

more

__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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-49994Same product: Linux Linux Kernel
CVE-2024-39509Same product: Linux Linux Kernel
CVE-2024-40969Same product: Linux Linux Kernel
CVE-2024-50238Same product: Linux Linux Kernel
CVE-2024-43863Same product: Linux Linux Kernel
CVE-2024-53147Same product: Linux Linux Kernel
CVE-2024-50056Same product: Linux Linux Kernel
CVE-2024-35841Same product: Linux Linux Kernel
CVE-2024-47726Same product: Linux Linux Kernel
CVE-2024-56579Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
6.11 · 4.14.86 — 4.15 · 4.19.7 — 4.20 · 4.20 — 5.15.165

Mitigating Controls

No mitigating controls mapped yet. The per-CVE control annotator has not reached this CVE.

References