<?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://cve.radiocsirt.org</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 17:13:54 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-72359 — CVE-2026-72359 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72359</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-72359</guid>
    </item>
    <item>
      <title>EUVD-2026-353750</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353750</link>
      <description>EUVD-2026-353750</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353750</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72359</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72359</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: fix NPD in bo_meminfo()&lt;/p&gt;
&lt;p&gt;When a buffer object is purged, its ttm.resource is set to NULL via the
TTM pipeline gutting flow. However, the BO remains in the client&amp;#39;s
object list until userspace explicitly closes the GEM handle. If memory
stats are queried during this time, accessing bo-&amp;gt;ttm.resource-&amp;gt;mem_type
will result in a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Fix this by safely skipping purged BOs in bo_meminfo, as they no longer
consume any memory.&lt;/p&gt;
&lt;p&gt;User is getting NPD on device resume, and possible theory is that in
bo_move(), if we need to evict something to SYSTEM to save the CCS state,
but the BO is marked as dontneed, this won&amp;#39;t trigger a move but will
nuke the pages, leaving us with a NULL bo resource. And the meminfo()
doesn&amp;#39;t look ready to handle a NULL resource.&lt;/p&gt;
&lt;p&gt;v2 (Sashiko):
 - There could potentially be other cases where we might end up with a
   NULL resource, so make this a general NULL check for now.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)&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/xe: fix NPD in bo_meminfo()&lt;/p&gt;
&lt;p&gt;When a buffer object is purged, its ttm.resource is set to NULL via the
TTM pipeline gutting flow. However, the BO remains in the client&amp;#39;s
object list until userspace explicitly closes the GEM handle. If memory
stats are queried during this time, accessing bo-&amp;gt;ttm.resource-&amp;gt;mem_type
will result in a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Fix this by safely skipping purged BOs in bo_meminfo, as they no longer
consume any memory.&lt;/p&gt;
&lt;p&gt;User is getting NPD on device resume, and possible theory is that in
bo_move(), if we need to evict something to SYSTEM to save the CCS state,
but the BO is marked as dontneed, this won&amp;#39;t trigger a move but will
nuke the pages, leaving us with a NULL bo resource. And the meminfo()
doesn&amp;#39;t look ready to handle a NULL resource.&lt;/p&gt;
&lt;p&gt;v2 (Sashiko):
 - There could potentially be other cases where we might end up with a
   NULL resource, so make this a general NULL check for now.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72359</guid>
    </item>
    <item>
      <title>GHSA-r35w-2gcj-cx97</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r35w-2gcj-cx97</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: fix NPD in bo_meminfo()&lt;/p&gt;
&lt;p&gt;When a buffer object is purged, its ttm.resource is set to NULL via the
TTM pipeline gutting flow. However, the BO remains in the client&amp;#39;s
object list until userspace explicitly closes the GEM handle. If memory
stats are queried during this time, accessing bo-&amp;gt;ttm.resource-&amp;gt;mem_type
will result in a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Fix this by safely skipping purged BOs in bo_meminfo, as they no longer
consume any memory.&lt;/p&gt;
&lt;p&gt;User is getting NPD on device resume, and possible theory is that in
bo_move(), if we need to evict something to SYSTEM to save the CCS state,
but the BO is marked as dontneed, this won&amp;#39;t trigger a move but will
nuke the pages, leaving us with a NULL bo resource. And the meminfo()
doesn&amp;#39;t look ready to handle a NULL resource.&lt;/p&gt;
&lt;p&gt;v2 (Sashiko):
 - There could potentially be other cases where we might end up with a
   NULL resource, so make this a general NULL check for now.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)&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/xe: fix NPD in bo_meminfo()&lt;/p&gt;
&lt;p&gt;When a buffer object is purged, its ttm.resource is set to NULL via the
TTM pipeline gutting flow. However, the BO remains in the client&amp;#39;s
object list until userspace explicitly closes the GEM handle. If memory
stats are queried during this time, accessing bo-&amp;gt;ttm.resource-&amp;gt;mem_type
will result in a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Fix this by safely skipping purged BOs in bo_meminfo, as they no longer
consume any memory.&lt;/p&gt;
&lt;p&gt;User is getting NPD on device resume, and possible theory is that in
bo_move(), if we need to evict something to SYSTEM to save the CCS state,
but the BO is marked as dontneed, this won&amp;#39;t trigger a move but will
nuke the pages, leaving us with a NULL bo resource. And the meminfo()
doesn&amp;#39;t look ready to handle a NULL resource.&lt;/p&gt;
&lt;p&gt;v2 (Sashiko):
 - There could potentially be other cases where we might end up with a
   NULL resource, so make this a general NULL check for now.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r35w-2gcj-cx97</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72359</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72359</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 93 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: fix NPD in bo_meminfo() When a buffer object is purged, its ttm.resource is set to NULL via the TTM pipeline gutting flow. However, the BO remains in the client&amp;#39;s object list until userspace explicitly closes the GEM handle. If memory stats are queried during this time, accessing bo-&amp;gt;ttm.resource-&amp;gt;mem_type will result in a NULL pointer dereference. Fix this by safely skipping purged BOs in bo_meminfo, as they no longer consume any memory. User is getting NPD on device resume, and possible theory is that in bo_move(), if we need to evict something to SYSTEM to save the CCS state, but the BO is marked as dontneed, this won&amp;#39;t trigger a move but will nuke the pages, leaving us with a NULL bo resource. And the meminfo() doesn&amp;#39;t look ready to handle a NULL resource. v2 (Sashiko):  - There could potentially be other cases where we might end up with a    NULL resource, so make this a general NULL check for now. (cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)&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 93 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: fix NPD in bo_meminfo() When a buffer object is purged, its ttm.resource is set to NULL via the TTM pipeline gutting flow. However, the BO remains in the client&amp;#39;s object list until userspace explicitly closes the GEM handle. If memory stats are queried during this time, accessing bo-&amp;gt;ttm.resource-&amp;gt;mem_type will result in a NULL pointer dereference. Fix this by safely skipping purged BOs in bo_meminfo, as they no longer consume any memory. User is getting NPD on device resume, and possible theory is that in bo_move(), if we need to evict something to SYSTEM to save the CCS state, but the BO is marked as dontneed, this won&amp;#39;t trigger a move but will nuke the pages, leaving us with a NULL bo resource. And the meminfo() doesn&amp;#39;t look ready to handle a NULL resource. v2 (Sashiko):  - There could potentially be other cases where we might end up with a    NULL resource, so make this a general NULL check for now. (cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72359</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
