<?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>Wed, 30 Sep 2026 13:56:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23134 — slab: fix kmalloc_nolock() context check for PREEMPT_RT</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23134</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;slab: fix kmalloc_nolock() context check for PREEMPT_RT&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT kernels, local_lock becomes a sleeping lock. The current
check in kmalloc_nolock() only verifies we&amp;#39;re not in NMI or hard IRQ
context, but misses the case where preemption is disabled.&lt;/p&gt;
&lt;p&gt;When a BPF program runs from a tracepoint with preemption disabled
(preempt_count &amp;gt; 0), kmalloc_nolock() proceeds to call
local_lock_irqsave() which attempts to acquire a sleeping lock,
triggering:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 6128
  preempt_count: 2, expected: 0&lt;/p&gt;
&lt;p&gt;Fix this by checking !preemptible() on PREEMPT_RT, which directly
expresses the constraint that we cannot take a sleeping lock when
preemption is disabled. This encompasses the previous checks for NMI
and hard IRQ contexts while also catching cases where preemption is
disabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;slab: fix kmalloc_nolock() context check for PREEMPT_RT&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT kernels, local_lock becomes a sleeping lock. The current
check in kmalloc_nolock() only verifies we&amp;#39;re not in NMI or hard IRQ
context, but misses the case where preemption is disabled.&lt;/p&gt;
&lt;p&gt;When a BPF program runs from a tracepoint with preemption disabled
(preempt_count &amp;gt; 0), kmalloc_nolock() proceeds to call
local_lock_irqsave() which attempts to acquire a sleeping lock,
triggering:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 6128
  preempt_count: 2, expected: 0&lt;/p&gt;
&lt;p&gt;Fix this by checking !preemptible() on PREEMPT_RT, which directly
expresses the constraint that we cannot take a sleeping lock when
preemption is disabled. This encompasses the previous checks for NMI
and hard IRQ contexts while also catching cases where preemption is
disabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23134</guid>
    </item>
  </channel>
</rss>
