{"id":65546,"date":"2025-07-04T19:31:42","date_gmt":"2025-07-04T16:01:42","guid":{"rendered":"https:\/\/afaghhosting.net\/blog\/cve-2025-38234-linux-kernel-sched-rt-push-rt-task-race-vulnerability\/"},"modified":"2025-07-04T19:31:42","modified_gmt":"2025-07-04T16:01:42","slug":"cve-2025-38234-linux-kernel-sched-rt-push-rt-task-race-vulnerability","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/cve-2025-38234-linux-kernel-sched-rt-push-rt-task-race-vulnerability\/","title":{"rendered":"CVE-2025-38234 &#8211; Linux Kernel Sched\/rt: Push Rt Task Race Vulnerability"},"content":{"rendered":"<p><strong>CVE ID : <\/strong>CVE-2025-38234<br \/>\n<br \/>\n<strong>Published : <\/strong> July 4, 2025, 2:15 p.m. | 44\u00a0minutes ago<br \/>\n<br \/>\n<strong>Description : <\/strong>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>sched\/rt: Fix race in push_rt_task<\/p>\n<p>Overview<br \/>\n========<br \/>\nWhen a CPU chooses to call push_rt_task and picks a task to push to<br \/>\nanother CPU&#8217;s runqueue then it will call find_lock_lowest_rq method<br \/>\nwhich would take a double lock on both CPUs&#8217; runqueues. If one of the<br \/>\nlocks aren&#8217;t readily available, it may lead to dropping the current<br \/>\nrunqueue lock and reacquiring both the locks at once. During this window<br \/>\nit is possible that the task is already migrated and is running on some<br \/>\nother CPU. These cases are already handled. However, if the task is<br \/>\nmigrated and has already been executed and another CPU is now trying to<br \/>\nwake it up (ttwu) such that it is queued again on the runqeue<br \/>\n(on_rq is 1) and also if the task was run by the same CPU, then the<br \/>\ncurrent checks will pass even though the task was migrated out and is no<br \/>\nlonger in the pushable tasks list.<\/p>\n<p>Crashes<br \/>\n=======<br \/>\nThis bug resulted in quite a few flavors of crashes triggering kernel<br \/>\npanics with various crash signatures such as assert failures, page<br \/>\nfaults, null pointer dereferences, and queue corruption errors all<br \/>\ncoming from scheduler itself.<\/p>\n<p>Some of the crashes:<br \/>\n-&gt; kernel BUG at kernel\/sched\/rt.c:1616! BUG_ON(idx &gt;= MAX_RT_PRIO)<br \/>\n   Call Trace:<br \/>\n   ? __die_body+0x1a\/0x60<br \/>\n   ? die+0x2a\/0x50<br \/>\n   ? do_trap+0x85\/0x100<br \/>\n   ? pick_next_task_rt+0x6e\/0x1d0<br \/>\n   ? do_error_trap+0x64\/0xa0<br \/>\n   ? pick_next_task_rt+0x6e\/0x1d0<br \/>\n   ? exc_invalid_op+0x4c\/0x60<br \/>\n   ? pick_next_task_rt+0x6e\/0x1d0<br \/>\n   ? asm_exc_invalid_op+0x12\/0x20<br \/>\n   ? pick_next_task_rt+0x6e\/0x1d0<br \/>\n   __schedule+0x5cb\/0x790<br \/>\n   ? update_ts_time_stats+0x55\/0x70<br \/>\n   schedule_idle+0x1e\/0x40<br \/>\n   do_idle+0x15e\/0x200<br \/>\n   cpu_startup_entry+0x19\/0x20<br \/>\n   start_secondary+0x117\/0x160<br \/>\n   secondary_startup_64_no_verify+0xb0\/0xbb<\/p>\n<p>-&gt; BUG: kernel NULL pointer dereference, address: 00000000000000c0<br \/>\n   Call Trace:<br \/>\n   ? __die_body+0x1a\/0x60<br \/>\n   ? no_context+0x183\/0x350<br \/>\n   ? __warn+0x8a\/0xe0<br \/>\n   ? exc_page_fault+0x3d6\/0x520<br \/>\n   ? asm_exc_page_fault+0x1e\/0x30<br \/>\n   ? pick_next_task_rt+0xb5\/0x1d0<br \/>\n   ? pick_next_task_rt+0x8c\/0x1d0<br \/>\n   __schedule+0x583\/0x7e0<br \/>\n   ? update_ts_time_stats+0x55\/0x70<br \/>\n   schedule_idle+0x1e\/0x40<br \/>\n   do_idle+0x15e\/0x200<br \/>\n   cpu_startup_entry+0x19\/0x20<br \/>\n   start_secondary+0x117\/0x160<br \/>\n   secondary_startup_64_no_verify+0xb0\/0xbb<\/p>\n<p>-&gt; BUG: unable to handle page fault for address: ffff9464daea5900<br \/>\n   kernel BUG at kernel\/sched\/rt.c:1861! BUG_ON(rq-&gt;cpu != task_cpu(p))<\/p>\n<p>-&gt; kernel BUG at kernel\/sched\/rt.c:1055! BUG_ON(!rq-&gt;nr_running)<br \/>\n   Call Trace:<br \/>\n   ? __die_body+0x1a\/0x60<br \/>\n   ? die+0x2a\/0x50<br \/>\n   ? do_trap+0x85\/0x100<br \/>\n   ? dequeue_top_rt_rq+0xa2\/0xb0<br \/>\n   ? do_error_trap+0x64\/0xa0<br \/>\n   ? dequeue_top_rt_rq+0xa2\/0xb0<br \/>\n   ? exc_invalid_op+0x4c\/0x60<br \/>\n   ? dequeue_top_rt_rq+0xa2\/0xb0<br \/>\n   ? asm_exc_invalid_op+0x12\/0x20<br \/>\n   ? dequeue_top_rt_rq+0xa2\/0xb0<br \/>\n   dequeue_rt_entity+0x1f\/0x70<br \/>\n   dequeue_task_rt+0x2d\/0x70<br \/>\n   __schedule+0x1a8\/0x7e0<br \/>\n   ? blk_finish_plug+0x25\/0x40<br \/>\n   schedule+0x3c\/0xb0<br \/>\n   futex_wait_queue_me+0xb6\/0x120<br \/>\n   futex_wait+0xd9\/0x240<br \/>\n   do_futex+0x344\/0xa90<br \/>\n   ? get_mm_exe_file+0x30\/0x60<br \/>\n   ? audit_exe_compare+0x58\/0x70<br \/>\n   ? audit_filter_rules.constprop.26+0x65e\/0x1220<br \/>\n   __x64_sys_futex+0x148\/0x1f0<br \/>\n   do_syscall_64+0x30\/0x80<br \/>\n   entry_SYSCALL_64_after_hwframe+0x62\/0xc7<\/p>\n<p>-&gt; BUG: unable to handle page fault for address: ffff8cf3608bc2c0<br \/>\n   Call Trace:<br \/>\n   ? __die_body+0x1a\/0x60<br \/>\n   ? no_context+0x183\/0x350<br \/>\n   ? spurious_kernel_fault+0x171\/0x1c0<br \/>\n   ? exc_page_fault+0x3b6\/0x520<br \/>\n   ? plist_check_list+0x15\/0x40<br \/>\n   ? plist_check_list+0x2e\/0x40<br \/>\n   ? asm_exc_page_fault+0x1e\/0x30<br \/>\n   ? _cond_resched+0x15\/0x30<br \/>\n   ? futex_wait_queue_me+0xc8\/0x120<br \/>\n   ? futex_wait+0xd9\/0x240<br \/>\n   ? try_to_wake_up+0x1b8\/0x490<br \/>\n   ? futex_wake+0x78\/0x160<br \/>\n   ? do_futex+0xcd\/0xa90<br \/>\n   ? plist_check_list+0x15\/0x40<br \/>\n   ? plist_check_list+0x2e\/0x40<br \/>\n   ? plist_del+0x6a\/0xd0<br \/>\n   ? plist_check_list+0x15\/0x40<br \/>\n   ? plist_check_list+0x2e\/0x40<br \/>\n   ? dequeue_pushable_task+0x20\/0x70<br \/>\n   ? __schedule+0x382\/0x7e0<br \/>\n   ? asm_sysvec_reschedule_i<br \/>\n&#8212;truncated&#8212;<br \/>\n<br \/>\n<strong>Severity:<\/strong> 0.0 | NA<br \/>\n<br \/>\nVisit the link for more details, such as CVSS details, affected products, timeline, and more&#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CVE ID : CVE-2025-38234 Published : July 4, 2025, 2:15 p.m. | 44\u00a0minutes ago Description : In the Linux kernel, the following vulnerability has been resolved: sched\/rt: Fix race in push_rt_task Overview ======== When a CPU chooses to call push_rt_task and picks a task to push to another CPU&#8217;s runqueue then it will call find_lock_lowest_rq &hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-65546","post","type-post","status-publish","format-standard","hentry","category-vulnerability"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/65546","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=65546"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/65546\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=65546"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=65546"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=65546"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}