<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T10:17:06.495007+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bell-cve-2026-99147</id>
    <title>BELL-CVE-2026-99147</title>
    <updated>2026-11-17T10:17:06.502578+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-99147"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</id>
    <title>certfr-2026-avi-1473 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
    <updated>2026-11-17T10:17:06.502625+00:00</updated>
    <content>certfr-2026-avi-1473</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-396199</id>
    <title>EUVD-2026-396199</title>
    <updated>2026-11-17T10:17:06.502644+00:00</updated>
    <content>EUVD-2026-396199</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-396199"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99147</id>
    <title>fkie_cve-2026-99147</title>
    <updated>2026-11-17T10:17:06.502655+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/exec: don't immediately add prelocked obj to array of locked objs</p>
<p>When a contention is detected the drm_exec object grabs a reference to
the contended object, unlocks all other objects and pre-locks the
contended one before anything else.</p>
<p>The problem is that it is possible that this pre-locked object was about
to be destroyed and drm_exec is now holding the last reference to it.</p>
<p>So we never actually see this pre-locked object again to be explicitly
locked and so also never reserve a slot for a dma_fence object on it.</p>
<p>Should the driver now use drm_exec_for_each_locked_object() to add a new
fence to all locked objects we eventually see a warning or even a
BUG_ON() to prevent random memory corruption.</p>
<p>Fix this by keeping the prelocked object out of the array of locked objs
until it was explicitly mentioned by the driver again.</p>
<p>If the prelocked object is never mentioned again by the driver
just unlock and drop the reference at the end of the locking loop.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99147"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-f9vc-r5f2-m3x9</id>
    <title>GHSA-f9vc-r5f2-m3x9</title>
    <updated>2026-11-17T10:17:06.502689+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/exec: don't immediately add prelocked obj to array of locked objs</p>
<p>When a contention is detected the drm_exec object grabs a reference to
the contended object, unlocks all other objects and pre-locks the
contended one before anything else.</p>
<p>The problem is that it is possible that this pre-locked object was about
to be destroyed and drm_exec is now holding the last reference to it.</p>
<p>So we never actually see this pre-locked object again to be explicitly
locked and so also never reserve a slot for a dma_fence object on it.</p>
<p>Should the driver now use drm_exec_for_each_locked_object() to add a new
fence to all locked objects we eventually see a warning or even a
BUG_ON() to prevent random memory corruption.</p>
<p>Fix this by keeping the prelocked object out of the array of locked objs
until it was explicitly mentioned by the driver again.</p>
<p>If the prelocked object is never mentioned again by the driver
just unlock and drop the reference at the end of the locking loop.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-f9vc-r5f2-m3x9"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99147</id>
    <title>msrc_CVE-2026-99147 — drm/exec: don't immediately add prelocked obj to array of locked objs</title>
    <updated>2026-11-17T10:17:06.502713+00:00</updated>
    <content>msrc_CVE-2026-99147</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99147"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99147</id>
    <title>UBUNTU-CVE-2026-99147</title>
    <updated>2026-11-17T10:17:06.502729+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 165 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: drm/exec: don't immediately add prelocked obj to array of locked objs When a contention is detected the drm_exec object grabs a reference to the contended object, unlocks all other objects and pre-locks the contended one before anything else. The problem is that it is possible that this pre-locked object was about to be destroyed and drm_exec is now holding the last reference to it. So we never actually see this pre-locked object again to be explicitly locked and so also never reserve a slot for a dma_fence object on it. Should the driver now use drm_exec_for_each_locked_object() to add a new fence to all locked objects we eventually see a warning or even a BUG_ON() to prevent random memory corruption. Fix this by keeping the prelocked object out of the array of locked objs until it was explicitly mentioned by the driver again. If the prelocked object is never mentioned again by the driver just unlock and drop the reference at the end of the locking loop.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99147"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224</id>
    <title>WID-SEC-W-2026-4224 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-17T10:17:06.502908+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224"/>
  </entry>
</feed>
