<?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-10-03T11:57:23.911106+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-2023-53095</id>
    <title>CVE-2023-53095 — drm/ttm: Fix a NULL pointer dereference</title>
    <updated>2026-10-03T11:57:24.379934+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>drm/ttm: Fix a NULL pointer dereference</p>
<p>The LRU mechanism may look up a resource in the process of being removed
from an object. The locking rules here are a bit unclear but it looks
currently like res-&gt;bo assignment is protected by the LRU lock, whereas
bo-&gt;resource is protected by the object lock, while *clearing* of
bo-&gt;resource is also protected by the LRU lock. This means that if
we check that bo-&gt;resource points to the LRU resource under the LRU
lock we should be safe.
So perform that check before deciding to swap out a bo. That avoids
dereferencing a NULL bo-&gt;resource in ttm_bo_swapout().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-53095"/>
  </entry>
</feed>
