<?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>Fri, 02 Oct 2026 12:46:16 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04681</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04681</link>
      <description>bdu:2025-04681</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04681</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0496 — 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://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>EUVD-2026-309641</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309641</link>
      <description>EUVD-2026-309641</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309641</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47280</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47280</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm: Fix use-after-free read in drm_getunique()&lt;/p&gt;
&lt;p&gt;There is a time-of-check-to-time-of-use error in drm_getunique() due
to retrieving file_priv-&amp;gt;master prior to locking the device&amp;#39;s master
mutex.&lt;/p&gt;
&lt;p&gt;An example can be seen in the crash report of the use-after-free error
found by Syzbot:
https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803&lt;/p&gt;
&lt;p&gt;In the report, the master pointer was used after being freed. This is
because another process had acquired the device&amp;#39;s master mutex in
drm_setmaster_ioctl(), then overwrote fpriv-&amp;gt;master in
drm_new_set_master(). The old value of fpriv-&amp;gt;master was subsequently
freed before the mutex was unlocked.&lt;/p&gt;
&lt;p&gt;To fix this, we lock the device&amp;#39;s master mutex before retrieving the
pointer from from fpriv-&amp;gt;master. This patch passes the Syzbot
reproducer test.&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: Fix use-after-free read in drm_getunique()&lt;/p&gt;
&lt;p&gt;There is a time-of-check-to-time-of-use error in drm_getunique() due
to retrieving file_priv-&amp;gt;master prior to locking the device&amp;#39;s master
mutex.&lt;/p&gt;
&lt;p&gt;An example can be seen in the crash report of the use-after-free error
found by Syzbot:
https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803&lt;/p&gt;
&lt;p&gt;In the report, the master pointer was used after being freed. This is
because another process had acquired the device&amp;#39;s master mutex in
drm_setmaster_ioctl(), then overwrote fpriv-&amp;gt;master in
drm_new_set_master(). The old value of fpriv-&amp;gt;master was subsequently
freed before the mutex was unlocked.&lt;/p&gt;
&lt;p&gt;To fix this, we lock the device&amp;#39;s master mutex before retrieving the
pointer from from fpriv-&amp;gt;master. This patch passes the Syzbot
reproducer test.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47280</guid>
    </item>
    <item>
      <title>GHSA-rcjv-j3v6-r6cv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rcjv-j3v6-r6cv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm: Fix use-after-free read in drm_getunique()&lt;/p&gt;
&lt;p&gt;There is a time-of-check-to-time-of-use error in drm_getunique() due
to retrieving file_priv-&amp;gt;master prior to locking the device&amp;#39;s master
mutex.&lt;/p&gt;
&lt;p&gt;An example can be seen in the crash report of the use-after-free error
found by Syzbot:
https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803&lt;/p&gt;
&lt;p&gt;In the report, the master pointer was used after being freed. This is
because another process had acquired the device&amp;#39;s master mutex in
drm_setmaster_ioctl(), then overwrote fpriv-&amp;gt;master in
drm_new_set_master(). The old value of fpriv-&amp;gt;master was subsequently
freed before the mutex was unlocked.&lt;/p&gt;
&lt;p&gt;To fix this, we lock the device&amp;#39;s master mutex before retrieving the
pointer from from fpriv-&amp;gt;master. This patch passes the Syzbot
reproducer test.&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: Fix use-after-free read in drm_getunique()&lt;/p&gt;
&lt;p&gt;There is a time-of-check-to-time-of-use error in drm_getunique() due
to retrieving file_priv-&amp;gt;master prior to locking the device&amp;#39;s master
mutex.&lt;/p&gt;
&lt;p&gt;An example can be seen in the crash report of the use-after-free error
found by Syzbot:
https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803&lt;/p&gt;
&lt;p&gt;In the report, the master pointer was used after being freed. This is
because another process had acquired the device&amp;#39;s master mutex in
drm_setmaster_ioctl(), then overwrote fpriv-&amp;gt;master in
drm_new_set_master(). The old value of fpriv-&amp;gt;master was subsequently
freed before the mutex was unlocked.&lt;/p&gt;
&lt;p&gt;To fix this, we lock the device&amp;#39;s master mutex before retrieving the
pointer from from fpriv-&amp;gt;master. This patch passes the Syzbot
reproducer test.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rcjv-j3v6-r6cv</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1979-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1979-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://cve.radiocsirt.org/vuln/suse-su-2024:1979-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47280</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47280</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm: Fix use-after-free read in drm_getunique() There is a time-of-check-to-time-of-use error in drm_getunique() due to retrieving file_priv-&amp;gt;master prior to locking the device&amp;#39;s master mutex. An example can be seen in the crash report of the use-after-free error found by Syzbot: https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803 In the report, the master pointer was used after being freed. This is because another process had acquired the device&amp;#39;s master mutex in drm_setmaster_ioctl(), then overwrote fpriv-&amp;gt;master in drm_new_set_master(). The old value of fpriv-&amp;gt;master was subsequently freed before the mutex was unlocked. To fix this, we lock the device&amp;#39;s master mutex before retrieving the pointer from from fpriv-&amp;gt;master. This patch passes the Syzbot reproducer test.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm: Fix use-after-free read in drm_getunique() There is a time-of-check-to-time-of-use error in drm_getunique() due to retrieving file_priv-&amp;gt;master prior to locking the device&amp;#39;s master mutex. An example can be seen in the crash report of the use-after-free error found by Syzbot: https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803 In the report, the master pointer was used after being freed. This is because another process had acquired the device&amp;#39;s master mutex in drm_setmaster_ioctl(), then overwrote fpriv-&amp;gt;master in drm_new_set_master(). The old value of fpriv-&amp;gt;master was subsequently freed before the mutex was unlocked. To fix this, we lock the device&amp;#39;s master mutex before retrieving the pointer from from fpriv-&amp;gt;master. This patch passes the Syzbot reproducer test.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47280</guid>
    </item>
  </channel>
</rss>
