{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-57891 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-57891 is a medium-severity vulnerability in Linux kernel, published on 15 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-57891 and fix it if it is affected.\n\nWhat it is: CVE-2024-57891 is a medium-severity vulnerability in Linux kernel, published on 15 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-57891 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-57891/ (Markdown: https://insights.sbomify.com/CVE-2024-57891/index.md)","id":"CVE-2024-57891","markdown":"https://insights.sbomify.com/CVE-2024-57891/index.md","name":"CVE-2024-57891","record":{"aliases":["BELL-CVE-2024-57891","DEBIAN-CVE-2024-57891","GHSA-4p97-h32p-wgf6","UBUNTU-CVE-2024-57891"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel scheduler","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel scheduler extension allows premature IRQ re-enabling, potentially causing system instability or crashes.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"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): [\u003cffff8000800b699c\u003e] scx_ops_bypass+0x174/0x3b8\n  hardirqs last disabled at (33738): [\u003cffff800080d48ad4\u003e] _raw_spin_lock_irqsave+0xb4/0xd8\n\nDrop the stray _irqrestore().","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"sched_ext: Fix invalid irq restore in scx_ops_bypass()","id":"CVE-2024-57891","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv","id":"CVE-2024-57892"},"packages":[],"prev":{"headline":"RDMA/uverbs: Prevent integer overflow issue","id":"CVE-2024-57890"},"products":["Linux"],"published":"2025-01-15","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A race condition in the Linux kernel scheduler extension allows premature IRQ re-enabling, potentially causing system instability or crashes.","url":"https://insights.sbomify.com/CVE-2024-57891/"}