<?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 22:01:28 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-14082</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-14082</link>
      <description>bdu:2026-14082</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-14082</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-53293</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53293</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-53293</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0866 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoque…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0866</link>
      <description>certfr-2026-avi-0866</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0866</guid>
    </item>
    <item>
      <title>EUVD-2026-330786</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-330786</link>
      <description>EUVD-2026-330786</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-330786</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53293</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53293</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG&lt;/p&gt;
&lt;p&gt;There were multiple issues in that code.&lt;/p&gt;
&lt;p&gt;First of all the order between the reset semaphore and the mm_lock was
wrong (e.g. copy_to_user) was called while holding the lock.&lt;/p&gt;
&lt;p&gt;Then we allocated memory while holding the reset semaphore which is also
a pretty big bug and can deadlock.&lt;/p&gt;
&lt;p&gt;Then we used down_read_trylock() instead of waiting for the reset to
finish.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)&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/amdgpu: fix AMDGPU_INFO_READ_MMR_REG&lt;/p&gt;
&lt;p&gt;There were multiple issues in that code.&lt;/p&gt;
&lt;p&gt;First of all the order between the reset semaphore and the mm_lock was
wrong (e.g. copy_to_user) was called while holding the lock.&lt;/p&gt;
&lt;p&gt;Then we allocated memory while holding the reset semaphore which is also
a pretty big bug and can deadlock.&lt;/p&gt;
&lt;p&gt;Then we used down_read_trylock() instead of waiting for the reset to
finish.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53293</guid>
    </item>
    <item>
      <title>GHSA-qxgc-w63m-xvqr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qxgc-w63m-xvqr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG&lt;/p&gt;
&lt;p&gt;There were multiple issues in that code.&lt;/p&gt;
&lt;p&gt;First of all the order between the reset semaphore and the mm_lock was
wrong (e.g. copy_to_user) was called while holding the lock.&lt;/p&gt;
&lt;p&gt;Then we allocated memory while holding the reset semaphore which is also
a pretty big bug and can deadlock.&lt;/p&gt;
&lt;p&gt;Then we used down_read_trylock() instead of waiting for the reset to
finish.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)&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/amdgpu: fix AMDGPU_INFO_READ_MMR_REG&lt;/p&gt;
&lt;p&gt;There were multiple issues in that code.&lt;/p&gt;
&lt;p&gt;First of all the order between the reset semaphore and the mm_lock was
wrong (e.g. copy_to_user) was called while holding the lock.&lt;/p&gt;
&lt;p&gt;Then we allocated memory while holding the reset semaphore which is also
a pretty big bug and can deadlock.&lt;/p&gt;
&lt;p&gt;Then we used down_read_trylock() instead of waiting for the reset to
finish.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qxgc-w63m-xvqr</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-53293 — drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-53293</link>
      <description>msrc_CVE-2026-53293</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-53293</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21555-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-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/opensuse-su-2026:21555-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-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-2026:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53293</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53293</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 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG There were multiple issues in that code. First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the lock. Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can deadlock. Then we used down_read_trylock() instead of waiting for the reset to finish. (cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)&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 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG There were multiple issues in that code. First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the lock. Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can deadlock. Then we used down_read_trylock() instead of waiting for the reset to finish. (cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53293</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2119 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2119</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, einen Denial of Service zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, einen Denial of Service zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2119</guid>
    </item>
  </channel>
</rss>
