<?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>Sun, 04 Oct 2026 16:05:35 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-06370</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-06370</link>
      <description>bdu:2025-06370</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-06370</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-21996</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-21996</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-21996</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0333 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0333</link>
      <description>certfr-2025-avi-0333</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0333</guid>
    </item>
    <item>
      <title>EUVD-2026-314138</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314138</link>
      <description>EUVD-2026-314138</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314138</guid>
    </item>
    <item>
      <title>fkie_cve-2025-21996</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-21996</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse()&lt;/p&gt;
&lt;p&gt;On the off chance that command stream passed from userspace via
ioctl() call to radeon_vce_cs_parse() is weirdly crafted and
first command to execute is to encode (case 0x03000001), the function
in question will attempt to call radeon_vce_cs_reloc() with size
argument that has not been properly initialized. Specifically, &amp;#39;size&amp;#39;
will point to &amp;#39;tmp&amp;#39; variable before the latter had a chance to be
assigned any value.&lt;/p&gt;
&lt;p&gt;Play it safe and init &amp;#39;tmp&amp;#39; with 0, thus ensuring that
radeon_vce_cs_reloc() will catch an early error in cases like these.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with static
analysis tool SVACE.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 2d52de55f9ee7aaee0e09ac443f77855989c6b68)&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/radeon: fix uninitialized size issue in radeon_vce_cs_parse()&lt;/p&gt;
&lt;p&gt;On the off chance that command stream passed from userspace via
ioctl() call to radeon_vce_cs_parse() is weirdly crafted and
first command to execute is to encode (case 0x03000001), the function
in question will attempt to call radeon_vce_cs_reloc() with size
argument that has not been properly initialized. Specifically, &amp;#39;size&amp;#39;
will point to &amp;#39;tmp&amp;#39; variable before the latter had a chance to be
assigned any value.&lt;/p&gt;
&lt;p&gt;Play it safe and init &amp;#39;tmp&amp;#39; with 0, thus ensuring that
radeon_vce_cs_reloc() will catch an early error in cases like these.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with static
analysis tool SVACE.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 2d52de55f9ee7aaee0e09ac443f77855989c6b68)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-21996</guid>
    </item>
    <item>
      <title>GHSA-p42v-4mrm-3j3g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p42v-4mrm-3j3g</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse()&lt;/p&gt;
&lt;p&gt;On the off chance that command stream passed from userspace via
ioctl() call to radeon_vce_cs_parse() is weirdly crafted and
first command to execute is to encode (case 0x03000001), the function
in question will attempt to call radeon_vce_cs_reloc() with size
argument that has not been properly initialized. Specifically, &amp;#39;size&amp;#39;
will point to &amp;#39;tmp&amp;#39; variable before the latter had a chance to be
assigned any value.&lt;/p&gt;
&lt;p&gt;Play it safe and init &amp;#39;tmp&amp;#39; with 0, thus ensuring that
radeon_vce_cs_reloc() will catch an early error in cases like these.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with static
analysis tool SVACE.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 2d52de55f9ee7aaee0e09ac443f77855989c6b68)&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/radeon: fix uninitialized size issue in radeon_vce_cs_parse()&lt;/p&gt;
&lt;p&gt;On the off chance that command stream passed from userspace via
ioctl() call to radeon_vce_cs_parse() is weirdly crafted and
first command to execute is to encode (case 0x03000001), the function
in question will attempt to call radeon_vce_cs_reloc() with size
argument that has not been properly initialized. Specifically, &amp;#39;size&amp;#39;
will point to &amp;#39;tmp&amp;#39; variable before the latter had a chance to be
assigned any value.&lt;/p&gt;
&lt;p&gt;Play it safe and init &amp;#39;tmp&amp;#39; with 0, thus ensuring that
radeon_vce_cs_reloc() will catch an early error in cases like these.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with static
analysis tool SVACE.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 2d52de55f9ee7aaee0e09ac443f77855989c6b68)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p42v-4mrm-3j3g</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-21996 — drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-21996</link>
      <description>msrc_CVE-2025-21996</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-21996</guid>
    </item>
    <item>
      <title>OESA-2025-1729 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1729</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:genirq/irqdesc: Prevent use-after-free in irq_find_at_or_after()irq_find_at_or_after() dereferences the interrupt descriptor which isreturned by mt_find() while neither holding sparse_irq_lock nor RCU readlock, which means the descriptor can be freed between mt_find() and thedereference:    CPU0                            CPU1    desc = mt_find()                                    delayed_free_desc(desc)    irq_desc_get_irq(desc)The use-after-free is reported by KASAN:    Call trace:     irq_get_next_irq+0x58/0x84     show_stat+0x638/0x824     seq_read_iter+0x158/0x4ec     proc_reg_read_iter+0x94/0x12c     vfs_read+0x1e0/0x2c8    Freed by task 4471:     slab_free_freelist_hook+0x174/0x1e0     __kmem_cache_free+0xa4/0x1dc     kfree+0x64/0x128     irq_kobj_release+0x28/0x3c     kobject_put+0xcc/0x1e0     delayed_free_desc+0x14/0x2c     rcu_do_batch+0x214/0x720Guard the access with a RCU read lock section.(CVE-2024-38385)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/lima: fix shared irq handling on driver remove&lt;/p&gt;
&lt;p&gt;lima uses a shared interrupt, so the interrupt handlers must be prepared
to be called at any time. At driver removal time, the clocks are
disabled early and the interrupts stay registered until the very end of
the remove process due to the devm usage.
This is potentially a bug as the interrupts access…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:genirq/irqdesc: Prevent use-after-free in irq_find_at_or_after()irq_find_at_or_after() dereferences the interrupt descriptor which isreturned by mt_find() while neither holding sparse_irq_lock nor RCU readlock, which means the descriptor can be freed between mt_find() and thedereference:    CPU0                            CPU1    desc = mt_find()                                    delayed_free_desc(desc)    irq_desc_get_irq(desc)The use-after-free is reported by KASAN:    Call trace:     irq_get_next_irq+0x58/0x84     show_stat+0x638/0x824     seq_read_iter+0x158/0x4ec     proc_reg_read_iter+0x94/0x12c     vfs_read+0x1e0/0x2c8    Freed by task 4471:     slab_free_freelist_hook+0x174/0x1e0     __kmem_cache_free+0xa4/0x1dc     kfree+0x64/0x128     irq_kobj_release+0x28/0x3c     kobject_put+0xcc/0x1e0     delayed_free_desc+0x14/0x2c     rcu_do_batch+0x214/0x720Guard the access with a RCU read lock section.(CVE-2024-38385)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/lima: fix shared irq handling on driver remove&lt;/p&gt;
&lt;p&gt;lima uses a shared interrupt, so the interrupt handlers must be prepared
to be called at any time. At driver removal time, the clocks are
disabled early and the interrupts stay registered until the very end of
the remove process due to the devm usage.
This is potentially a bug as the interrupts access…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1729</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01614-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01614-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-2025:01614-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21996</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21996</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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:16.04:LTS: linux-hwe-edge and 200 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse() On the off chance that command stream passed from userspace via ioctl() call to radeon_vce_cs_parse() is weirdly crafted and first command to execute is to encode (case 0x03000001), the function in question will attempt to call radeon_vce_cs_reloc() with size argument that has not been properly initialized. Specifically, &amp;#39;size&amp;#39; will point to &amp;#39;tmp&amp;#39; variable before the latter had a chance to be assigned any value. Play it safe and init &amp;#39;tmp&amp;#39; with 0, thus ensuring that radeon_vce_cs_reloc() will catch an early error in cases like these. Found by Linux Verification Center (linuxtesting.org) with static analysis tool SVACE. (cherry picked from commit 2d52de55f9ee7aaee0e09ac443f77855989c6b68)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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:16.04:LTS: linux-hwe-edge and 200 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse() On the off chance that command stream passed from userspace via ioctl() call to radeon_vce_cs_parse() is weirdly crafted and first command to execute is to encode (case 0x03000001), the function in question will attempt to call radeon_vce_cs_reloc() with size argument that has not been properly initialized. Specifically, &amp;#39;size&amp;#39; will point to &amp;#39;tmp&amp;#39; variable before the latter had a chance to be assigned any value. Play it safe and init &amp;#39;tmp&amp;#39; with 0, thus ensuring that radeon_vce_cs_reloc() will catch an early error in cases like these. Found by Linux Verification Center (linuxtesting.org) with static analysis tool SVACE. (cherry picked from commit 2d52de55f9ee7aaee0e09ac443f77855989c6b68)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21996</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0698 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0698</link>
      <description>&lt;p&gt;Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen &amp;#39;Denial of Service&amp;#39;-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen &amp;#39;Denial of Service&amp;#39;-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0698</guid>
    </item>
  </channel>
</rss>
