<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T04:32:19.200148+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-93261</id>
    <title>CVE-2026-93261 — locking/lockdep: Fix NULL pointer dereference in __lock_set_class()</title>
    <updated>2026-09-29T04:32:19.237982+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>locking/lockdep: Fix NULL pointer dereference in __lock_set_class()</p>
<p>register_lock_class() can return NULL when the lock class pool is
exhausted, graph_lock() fails, or key validation fails. However,
__lock_set_class() uses the return value directly in pointer arithmetic
without a NULL check:</p>
<p>class = register_lock_class(lock, subclass, 0);
  hlock-&gt;class_idx = class - lock_classes;</p>
<p>If class is NULL, this computes a wild offset that corrupts
hlock-&gt;class_idx. The subsequent reacquire_held_locks() call will
invoke hlock_class() with this corrupted index, leading to a NULL or
out-of-bounds pointer dereference.</p>
<p>Add the missing NULL check, consistent with how __lock_acquire() already
handles this case at the same call site.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-93261"/>
  </entry>
</feed>
