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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-44958 is a Linux kernel scheduler bug involving SMT state accounting during CPU offline handling. The public record shows a kernel warning from stress testing, not confirmed attacker exploitation. Business urgency is highest for systems that rely on affected Linux kernels and perform CPU hotplug, cpuset, or virtualization operations.
Executive priority
Schedule remediation through normal kernel patching unless local evidence shows scheduler warnings or critical hosts match affected versions. There is no source-backed evidence of active exploitation, but kernel defects can affect availability and should not be ignored.
Technical view
The flaw is an unbalanced decrement/increment of sched_smt_present in sched_cpu_deactivate(). If cpuset_cpu_inactive() fails, CPU offline fails after the SMT static key was decremented, causing a negative jump-label count warning. Kernel stable commits restore the increment on the error path.
Likely exposure
Exposure depends on running affected Linux kernel versions listed in the CVE record, including ranges around 5.15.165, 6.1.105, 6.6.46, 6.10.5, and 6.11. Confirm with distribution advisories because packaged kernel backports may differ from upstream version numbers.
Exploitation context
The source bundle does not show CISA KEV listing, public exploitation, exploit code, or attacker prerequisites. Evidence is limited to a stress-test warning and the upstream kernel fix. Treat this as a kernel stability issue unless vendor guidance states broader impact.
Researcher notes
Avoid overstating impact: the record does not provide CVSS, CWE, exploit status, or a demonstrated security outcome beyond the kernel warning. The key validation point is whether the kernel has the stable commit that rebalances sched_smt_present on sched_cpu_deactivate() failure.
Mitigation direction
Check your distribution’s advisory for CVE-2024-44958 and affected kernel packages.
Update to a kernel containing the referenced stable fixes or vendor backport.
Prioritize hosts using CPU hotplug, cpuset changes, SMT, or dense virtualization workloads.
Monitor kernel logs for related jump-label negative count warnings.
Validation and detection
Inventory kernel versions and map them against vendor advisories for this CVE.
Confirm the installed kernel includes the sched/smt error-path fix.
Review dmesg or central logs for static_key_slow_try_dec warnings.
Track Debian LTS and upstream Linux stable references for package-specific status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-44958 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.