{"uuid": "9955a59c-ec56-4175-bc9d-5b82b743bd25", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57891", "type": "seen", "source": "https://t.me/cvedetector/15458", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57891 - Linux Kernel - Unpredictable IRQ Restoration Vulnerability in Sched Ext\", \n  \"Content\": \"CVE ID : CVE-2024-57891 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsched_ext: Fix invalid irq restore in scx_ops_bypass()  \n  \nWhile adding outer irqsave/restore locking, 0e7ffff1b811 (\"scx: Fix raciness  \nin scx_ops_bypass()\") forgot to convert an inner rq_unlock_irqrestore() to  \nrq_unlock() which could re-enable IRQ prematurely leading to the following  \nwarning:  \n  \n  raw_local_irq_restore() called with IRQs enabled  \n  WARNING: CPU: 1 PID: 96 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40  \n  ...  \n  Sched_ext: create_dsq (enabling)  \n  pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  \n  pc : warn_bogus_irq_restore+0x30/0x40  \n  lr : warn_bogus_irq_restore+0x30/0x40  \n  ...  \n  Call trace:  \n   warn_bogus_irq_restore+0x30/0x40 (P)  \n   warn_bogus_irq_restore+0x30/0x40 (L)  \n   scx_ops_bypass+0x224/0x3b8  \n   scx_ops_enable.isra.0+0x2c8/0xaa8  \n   bpf_scx_reg+0x18/0x30  \n  ...  \n  irq event stamp: 33739  \n  hardirqs last  enabled at (33739): [] scx_ops_bypass+0x174/0x3b8  \n  hardirqs last disabled at (33738): [] _raw_spin_lock_irqsave+0xb4/0xd8  \n  \nDrop the stray _irqrestore(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:07:04.000000Z"}