{"vulnerability": "CVE-2024-44958", "sightings": [{"uuid": "1a5f180a-3289-4971-bcea-5effe9a264bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-44958", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "6d0240d5-1cff-4263-bb57-6aa9e81d2957", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44958", "type": "seen", "source": "https://t.me/cvedetector/4838", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44958 - Linux Kernel SMT sched vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-44958 \nPublished : Sept. 4, 2024, 7:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsched/smt: Fix unbalance sched_smt_present dec/inc  \n  \nI got the following warn report while doing stress test:  \n  \njump label: negative count!  \nWARNING: CPU: 3 PID: 38 at kernel/jump_label.c:263 static_key_slow_try_dec+0x9d/0xb0  \nCall Trace:  \n   \n __static_key_slow_dec_cpuslocked+0x16/0x70  \n sched_cpu_deactivate+0x26e/0x2a0  \n cpuhp_invoke_callback+0x3ad/0x10d0  \n cpuhp_thread_fun+0x3f5/0x680  \n smpboot_thread_fn+0x56d/0x8d0  \n kthread+0x309/0x400  \n ret_from_fork+0x41/0x70  \n ret_from_fork_asm+0x1b/0x30  \n   \n  \nBecause when cpuset_cpu_inactive() fails in sched_cpu_deactivate(),  \nthe cpu offline failed, but sched_smt_present is decremented before  \ncalling sched_cpu_deactivate(), it leads to unbalanced dec/inc, so  \nfix it by incrementing sched_smt_present in the error path. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"04 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-04T21:56:13.000000Z"}]}