{"uuid": "cdb479af-7834-4503-97d5-93caef63b7f7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21657", "type": "seen", "source": "https://t.me/cvedetector/15940", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21657 - Linux Kernel Sched Ext rq_lock Raw Spin Lock RQ Locking Weakness\", \n  \"Content\": \"CVE ID : CVE-2025-21657 \nPublished : Jan. 21, 2025, 1:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsched_ext: Replace rq_lock() to raw_spin_rq_lock() in scx_ops_bypass()  \n  \nscx_ops_bypass() iterates all CPUs to re-enqueue all the scx tasks.  \nFor each CPU, it acquires a lock using rq_lock() regardless of whether  \na CPU is offline or the CPU is currently running a task in a higher  \nscheduler class (e.g., deadline). The rq_lock() is supposed to be used  \nfor online CPUs, and the use of rq_lock() may trigger an unnecessary  \nwarning in rq_pin_lock(). Therefore, replace rq_lock() to  \nraw_spin_rq_lock() in scx_ops_bypass().  \n  \nWithout this change, we observe the following warning:  \n  \n===== START =====  \n[    6.615205] rq->balance_callback && rq->balance_callback != &balance_push_callback  \n[    6.615208] WARNING: CPU: 2 PID: 0 at kernel/sched/sched.h:1730 __schedule+0x1130/0x1c90  \n=====  END  ===== \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T15:17:21.000000Z"}