https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 20:09:59 +0000 https://db.gcve.eu/vuln/cve-2026-90432 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sched_ext: Abort directly from the hardlockup handler</p> <p>scx_hardlockup() defers the abort to an irq_work because exit claiming used to take scx_sched_lock and couldn&#39;t run from NMI. The deferral is now unnecessary - claiming is NMI-safe and asserting -&gt;aborting is exactly what breaks the live-locks that hard-lock CPUs. Call handle_lockup() directly and drop the irq_work. This also makes the self-detected case recoverable: the perf watchdog fires on the hard-locked CPU itself, where a queued irq_work never runs with IRQs off.</p> <p>Also fix the return value: %true used to be returned whenever sched_ext was loaded, suppressing the kernel&#39;s hardlockup report even when the abort was refused. Return %true only when this call initiated the abort.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sched_ext: Abort directly from the hardlockup handler</p> <p>scx_hardlockup() defers the abort to an irq_work because exit claiming used to take scx_sched_lock and couldn&#39;t run from NMI. The deferral is now unnecessary - claiming is NMI-safe and asserting -&gt;aborting is exactly what breaks the live-locks that hard-lock CPUs. Call handle_lockup() directly and drop the irq_work. This also makes the self-detected case recoverable: the perf watchdog fires on the hard-locked CPU itself, where a queued irq_work never runs with IRQs off.</p> <p>Also fix the return value: %true used to be returned whenever sched_ext was loaded, suppressing the kernel&#39;s hardlockup report even when the abort was refused. Return %true only when this call initiated the abort.</p> https://db.gcve.eu/vuln/cve-2026-90432