<?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>Tue, 17 Nov 2026 10:13:10 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98999</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98999</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98999</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-392028</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-392028</link>
      <description>EUVD-2026-392028</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-392028</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98999</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98999</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: Fix stale pinned_link entry when fb-pin performs the final unpin&lt;/p&gt;
&lt;p&gt;xe_bo_pin_external() and xe_bo_unpin_external() maintain the bo&amp;#39;s
pinned_link list membership in xe-&amp;gt;pinned.late.external, based on
whether the current call is the outermost pin or the final unpin.
However, the same external bo&amp;#39;s pin_count can also be raised and
lowered directly by __xe_pin_fb_vma()/__xe_unpin_fb_vma(), which pin
the bo as a display scanout buffer without going through
xe_bo_pin_external()/xe_bo_unpin_external() at all, and have no
notion of, or ownership over, pinned_link.&lt;/p&gt;
&lt;p&gt;If a bo is pinned both externally (e.g. dma-buf export) and as an fb,
and the external unpin happens first, xe_bo_unpin_external() correctly
observes pin_count &amp;gt; 1 and leaves the bo on pinned_link. When the fb
unpin later performs the true last unpin (pin_count 1 -&amp;gt; 0), it never
touches pinned_link, leaving the bo linked on xe-&amp;gt;pinned.late.external
indefinitely. Once the bo is subsequently freed, this stale list entry
points into freed memory, corrupting the list and risking a
use-after-free the next time the list is walked or spliced.&lt;/p&gt;
&lt;p&gt;The backup object pin/unpin sites in xe_bo_notifier_prepare_pinned()/
xe_bo_notifier_unprepare_pinned() have the same bypass characteristic,
though they never add their bo to a pinned list, so are not affected
by this particular list-corruption issue.&lt;/p&gt;
&lt;p&gt;Move the pinned_link removal into xe_bo_account_unpin(), which…&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 stale pinned_link entry when fb-pin performs the final unpin&lt;/p&gt;
&lt;p&gt;xe_bo_pin_external() and xe_bo_unpin_external() maintain the bo&amp;#39;s
pinned_link list membership in xe-&amp;gt;pinned.late.external, based on
whether the current call is the outermost pin or the final unpin.
However, the same external bo&amp;#39;s pin_count can also be raised and
lowered directly by __xe_pin_fb_vma()/__xe_unpin_fb_vma(), which pin
the bo as a display scanout buffer without going through
xe_bo_pin_external()/xe_bo_unpin_external() at all, and have no
notion of, or ownership over, pinned_link.&lt;/p&gt;
&lt;p&gt;If a bo is pinned both externally (e.g. dma-buf export) and as an fb,
and the external unpin happens first, xe_bo_unpin_external() correctly
observes pin_count &amp;gt; 1 and leaves the bo on pinned_link. When the fb
unpin later performs the true last unpin (pin_count 1 -&amp;gt; 0), it never
touches pinned_link, leaving the bo linked on xe-&amp;gt;pinned.late.external
indefinitely. Once the bo is subsequently freed, this stale list entry
points into freed memory, corrupting the list and risking a
use-after-free the next time the list is walked or spliced.&lt;/p&gt;
&lt;p&gt;The backup object pin/unpin sites in xe_bo_notifier_prepare_pinned()/
xe_bo_notifier_unprepare_pinned() have the same bypass characteristic,
though they never add their bo to a pinned list, so are not affected
by this particular list-corruption issue.&lt;/p&gt;
&lt;p&gt;Move the pinned_link removal into xe_bo_account_unpin(), which…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98999</guid>
    </item>
    <item>
      <title>GHSA-7j8x-2fgw-fvx8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7j8x-2fgw-fvx8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: Fix stale pinned_link entry when fb-pin performs the final unpin&lt;/p&gt;
&lt;p&gt;xe_bo_pin_external() and xe_bo_unpin_external() maintain the bo&amp;#39;s
pinned_link list membership in xe-&amp;gt;pinned.late.external, based on
whether the current call is the outermost pin or the final unpin.
However, the same external bo&amp;#39;s pin_count can also be raised and
lowered directly by __xe_pin_fb_vma()/__xe_unpin_fb_vma(), which pin
the bo as a display scanout buffer without going through
xe_bo_pin_external()/xe_bo_unpin_external() at all, and have no
notion of, or ownership over, pinned_link.&lt;/p&gt;
&lt;p&gt;If a bo is pinned both externally (e.g. dma-buf export) and as an fb,
and the external unpin happens first, xe_bo_unpin_external() correctly
observes pin_count &amp;gt; 1 and leaves the bo on pinned_link. When the fb
unpin later performs the true last unpin (pin_count 1 -&amp;gt; 0), it never
touches pinned_link, leaving the bo linked on xe-&amp;gt;pinned.late.external
indefinitely. Once the bo is subsequently freed, this stale list entry
points into freed memory, corrupting the list and risking a
use-after-free the next time the list is walked or spliced.&lt;/p&gt;
&lt;p&gt;The backup object pin/unpin sites in xe_bo_notifier_prepare_pinned()/
xe_bo_notifier_unprepare_pinned() have the same bypass characteristic,
though they never add their bo to a pinned list, so are not affected
by this particular list-corruption issue.&lt;/p&gt;
&lt;p&gt;Move the pinned_link removal into xe_bo_account_unpin(), which…&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 stale pinned_link entry when fb-pin performs the final unpin&lt;/p&gt;
&lt;p&gt;xe_bo_pin_external() and xe_bo_unpin_external() maintain the bo&amp;#39;s
pinned_link list membership in xe-&amp;gt;pinned.late.external, based on
whether the current call is the outermost pin or the final unpin.
However, the same external bo&amp;#39;s pin_count can also be raised and
lowered directly by __xe_pin_fb_vma()/__xe_unpin_fb_vma(), which pin
the bo as a display scanout buffer without going through
xe_bo_pin_external()/xe_bo_unpin_external() at all, and have no
notion of, or ownership over, pinned_link.&lt;/p&gt;
&lt;p&gt;If a bo is pinned both externally (e.g. dma-buf export) and as an fb,
and the external unpin happens first, xe_bo_unpin_external() correctly
observes pin_count &amp;gt; 1 and leaves the bo on pinned_link. When the fb
unpin later performs the true last unpin (pin_count 1 -&amp;gt; 0), it never
touches pinned_link, leaving the bo linked on xe-&amp;gt;pinned.late.external
indefinitely. Once the bo is subsequently freed, this stale list entry
points into freed memory, corrupting the list and risking a
use-after-free the next time the list is walked or spliced.&lt;/p&gt;
&lt;p&gt;The backup object pin/unpin sites in xe_bo_notifier_prepare_pinned()/
xe_bo_notifier_unprepare_pinned() have the same bypass characteristic,
though they never add their bo to a pinned list, so are not affected
by this particular list-corruption issue.&lt;/p&gt;
&lt;p&gt;Move the pinned_link removal into xe_bo_account_unpin(), which…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7j8x-2fgw-fvx8</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98999 — drm/xe: Fix stale pinned_link entry when fb-pin performs the final unpin</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98999</link>
      <description>msrc_CVE-2026-98999</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98999</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98999</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98999</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 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix stale pinned_link entry when fb-pin performs the final unpin xe_bo_pin_external() and xe_bo_unpin_external() maintain the bo&amp;#39;s pinned_link list membership in xe-&amp;gt;pinned.late.external, based on whether the current call is the outermost pin or the final unpin. However, the same external bo&amp;#39;s pin_count can also be raised and lowered directly by __xe_pin_fb_vma()/__xe_unpin_fb_vma(), which pin the bo as a display scanout buffer without going through xe_bo_pin_external()/xe_bo_unpin_external() at all, and have no notion of, or ownership over, pinned_link. If a bo is pinned both externally (e.g. dma-buf export) and as an fb, and the external unpin happens first, xe_bo_unpin_external() correctly observes pin_count &amp;gt; 1 and leaves the bo on pinned_link. When the fb unpin later performs the true last unpin (pin_count 1 -&amp;gt; 0), it never touches pinned_link, leaving the bo linked on xe-&amp;gt;pinned.late.external indefinitely. Once the bo is subsequently freed, this stale list entry points into freed memory, corrupting the list and risking a use-after-free the next time the list is walked or spliced. The backup object pin/unpin sites in xe_bo_notifier_prepare_pinned()/ xe_bo_notifier_unprepare_pinned() have the same bypass characteristic, though they never add their bo to a pinned list, so are not affected by this particular list-corruption issue. Move the pinned_link removal into xe_bo_account_unpin(), which alrea…&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 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix stale pinned_link entry when fb-pin performs the final unpin xe_bo_pin_external() and xe_bo_unpin_external() maintain the bo&amp;#39;s pinned_link list membership in xe-&amp;gt;pinned.late.external, based on whether the current call is the outermost pin or the final unpin. However, the same external bo&amp;#39;s pin_count can also be raised and lowered directly by __xe_pin_fb_vma()/__xe_unpin_fb_vma(), which pin the bo as a display scanout buffer without going through xe_bo_pin_external()/xe_bo_unpin_external() at all, and have no notion of, or ownership over, pinned_link. If a bo is pinned both externally (e.g. dma-buf export) and as an fb, and the external unpin happens first, xe_bo_unpin_external() correctly observes pin_count &amp;gt; 1 and leaves the bo on pinned_link. When the fb unpin later performs the true last unpin (pin_count 1 -&amp;gt; 0), it never touches pinned_link, leaving the bo linked on xe-&amp;gt;pinned.late.external indefinitely. Once the bo is subsequently freed, this stale list entry points into freed memory, corrupting the list and risking a use-after-free the next time the list is walked or spliced. The backup object pin/unpin sites in xe_bo_notifier_prepare_pinned()/ xe_bo_notifier_unprepare_pinned() have the same bypass characteristic, though they never add their bo to a pinned list, so are not affected by this particular list-corruption issue. Move the pinned_link removal into xe_bo_account_unpin(), which alrea…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98999</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
