<?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>Sat, 03 Oct 2026 21:13:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53095 — drm/ttm: Fix a NULL pointer dereference</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53095</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;drm/ttm: Fix a NULL pointer dereference&lt;/p&gt;
&lt;p&gt;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-&amp;gt;bo assignment is protected by the LRU lock, whereas
bo-&amp;gt;resource is protected by the object lock, while *clearing* of
bo-&amp;gt;resource is also protected by the LRU lock. This means that if
we check that bo-&amp;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-&amp;gt;resource in ttm_bo_swapout().&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;drm/ttm: Fix a NULL pointer dereference&lt;/p&gt;
&lt;p&gt;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-&amp;gt;bo assignment is protected by the LRU lock, whereas
bo-&amp;gt;resource is protected by the object lock, while *clearing* of
bo-&amp;gt;resource is also protected by the LRU lock. This means that if
we check that bo-&amp;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-&amp;gt;resource in ttm_bo_swapout().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53095</guid>
    </item>
  </channel>
</rss>
