<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 22:30:05 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-90432 — CVE-2026-90432 does not affect BellSoft software</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-90432</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-90432</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90432</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-90432</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Abort directly from the hardlockup handler&lt;/p&gt;
&lt;p&gt;scx_hardlockup() defers the abort to an irq_work because exit claiming used
to take scx_sched_lock and couldn&amp;#39;t run from NMI. The deferral is now
unnecessary - claiming is NMI-safe and asserting -&amp;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.&lt;/p&gt;
&lt;p&gt;Also fix the return value: %true used to be returned whenever sched_ext was
loaded, suppressing the kernel&amp;#39;s hardlockup report even when the abort was
refused. Return %true only when this call initiated the abort.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Abort directly from the hardlockup handler&lt;/p&gt;
&lt;p&gt;scx_hardlockup() defers the abort to an irq_work because exit claiming used
to take scx_sched_lock and couldn&amp;#39;t run from NMI. The deferral is now
unnecessary - claiming is NMI-safe and asserting -&amp;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.&lt;/p&gt;
&lt;p&gt;Also fix the return value: %true used to be returned whenever sched_ext was
loaded, suppressing the kernel&amp;#39;s hardlockup report even when the abort was
refused. Return %true only when this call initiated the abort.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-90432</guid>
    </item>
    <item>
      <title>GHSA-3xgc-q8gm-m2rg</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-3xgc-q8gm-m2rg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Abort directly from the hardlockup handler&lt;/p&gt;
&lt;p&gt;scx_hardlockup() defers the abort to an irq_work because exit claiming used
to take scx_sched_lock and couldn&amp;#39;t run from NMI. The deferral is now
unnecessary - claiming is NMI-safe and asserting -&amp;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.&lt;/p&gt;
&lt;p&gt;Also fix the return value: %true used to be returned whenever sched_ext was
loaded, suppressing the kernel&amp;#39;s hardlockup report even when the abort was
refused. Return %true only when this call initiated the abort.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Abort directly from the hardlockup handler&lt;/p&gt;
&lt;p&gt;scx_hardlockup() defers the abort to an irq_work because exit claiming used
to take scx_sched_lock and couldn&amp;#39;t run from NMI. The deferral is now
unnecessary - claiming is NMI-safe and asserting -&amp;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.&lt;/p&gt;
&lt;p&gt;Also fix the return value: %true used to be returned whenever sched_ext was
loaded, suppressing the kernel&amp;#39;s hardlockup report even when the abort was
refused. Return %true only when this call initiated the abort.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-3xgc-q8gm-m2rg</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11893-1 — kernel-devel-7.2.8-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11893-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11893-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90432</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90432</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched_ext: Abort directly from the hardlockup handler scx_hardlockup() defers the abort to an irq_work because exit claiming used to take scx_sched_lock and couldn&amp;#39;t run from NMI. The deferral is now unnecessary - claiming is NMI-safe and asserting -&amp;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. Also fix the return value: %true used to be returned whenever sched_ext was loaded, suppressing the kernel&amp;#39;s hardlockup report even when the abort was refused. Return %true only when this call initiated the abort.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched_ext: Abort directly from the hardlockup handler scx_hardlockup() defers the abort to an irq_work because exit claiming used to take scx_sched_lock and couldn&amp;#39;t run from NMI. The deferral is now unnecessary - claiming is NMI-safe and asserting -&amp;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. Also fix the return value: %true used to be returned whenever sched_ext was loaded, suppressing the kernel&amp;#39;s hardlockup report even when the abort was refused. Return %true only when this call initiated the abort.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90432</guid>
    </item>
  </channel>
</rss>
