<?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>Sun, 04 Oct 2026 14:36:21 +0000</lastBuildDate>
    <item>
      <title>CERTFR-2025-AVI-0529 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0529</link>
      <description>CERTFR-2025-AVI-0529</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0529</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53095</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2023-53095</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2023-53095</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53095</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2023-53095</link>
      <description>&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;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/fkie_cve-2023-53095</guid>
    </item>
    <item>
      <title>GHSA-qq4h-f4qp-wr7q</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-qq4h-f4qp-wr7q</link>
      <description>&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;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/ghsa-qq4h-f4qp-wr7q</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — security update for kernel</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;security update for kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;security update for kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01966-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2025:01966-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/suse-su-2025:01966-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53095</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53095</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 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix a NULL pointer dereference 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; 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 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix a NULL pointer dereference 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/ubuntu-cve-2023-53095</guid>
    </item>
  </channel>
</rss>
