<?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>Sat, 03 Oct 2026 20:37:44 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72484</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72484</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-2026-72484</guid>
    </item>
    <item>
      <title>EUVD-2026-353793</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353793</link>
      <description>EUVD-2026-353793</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353793</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72484</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72484</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;staging: most: video: avoid double free on video register failure&lt;/p&gt;
&lt;p&gt;comp_register_videodev() allocates a video_device with
video_device_alloc() and releases it if video_register_device() fails.&lt;/p&gt;
&lt;p&gt;This can double free the video_device when __video_register_device()
reaches device_register() and that call fails:&lt;/p&gt;
&lt;p&gt;video_register_device()
    -&amp;gt; __video_register_device()
       -&amp;gt; device_register() fails
          -&amp;gt; put_device(&amp;amp;vdev-&amp;gt;dev)
             -&amp;gt; v4l2_device_release()
                -&amp;gt; vdev-&amp;gt;release(vdev)
                   -&amp;gt; video_device_release(vdev)&lt;/p&gt;
&lt;p&gt;comp_register_videodev()
    -&amp;gt; video_device_release(mdev-&amp;gt;vdev)&lt;/p&gt;
&lt;p&gt;Use video_device_release_empty() while registering the device so that
registration failure paths do not free mdev-&amp;gt;vdev through vdev-&amp;gt;release().
comp_register_videodev() then releases mdev-&amp;gt;vdev exactly once on failure.
Restore video_device_release() after successful registration so the
registered device keeps its normal lifetime handling.&lt;/p&gt;
&lt;p&gt;This issue was found by a static analysis tool I am developing.&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;staging: most: video: avoid double free on video register failure&lt;/p&gt;
&lt;p&gt;comp_register_videodev() allocates a video_device with
video_device_alloc() and releases it if video_register_device() fails.&lt;/p&gt;
&lt;p&gt;This can double free the video_device when __video_register_device()
reaches device_register() and that call fails:&lt;/p&gt;
&lt;p&gt;video_register_device()
    -&amp;gt; __video_register_device()
       -&amp;gt; device_register() fails
          -&amp;gt; put_device(&amp;amp;vdev-&amp;gt;dev)
             -&amp;gt; v4l2_device_release()
                -&amp;gt; vdev-&amp;gt;release(vdev)
                   -&amp;gt; video_device_release(vdev)&lt;/p&gt;
&lt;p&gt;comp_register_videodev()
    -&amp;gt; video_device_release(mdev-&amp;gt;vdev)&lt;/p&gt;
&lt;p&gt;Use video_device_release_empty() while registering the device so that
registration failure paths do not free mdev-&amp;gt;vdev through vdev-&amp;gt;release().
comp_register_videodev() then releases mdev-&amp;gt;vdev exactly once on failure.
Restore video_device_release() after successful registration so the
registered device keeps its normal lifetime handling.&lt;/p&gt;
&lt;p&gt;This issue was found by a static analysis tool I am developing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72484</guid>
    </item>
    <item>
      <title>GHSA-79gv-9p52-g5cr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-79gv-9p52-g5cr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;staging: most: video: avoid double free on video register failure&lt;/p&gt;
&lt;p&gt;comp_register_videodev() allocates a video_device with
video_device_alloc() and releases it if video_register_device() fails.&lt;/p&gt;
&lt;p&gt;This can double free the video_device when __video_register_device()
reaches device_register() and that call fails:&lt;/p&gt;
&lt;p&gt;video_register_device()
    -&amp;gt; __video_register_device()
       -&amp;gt; device_register() fails
          -&amp;gt; put_device(&amp;amp;vdev-&amp;gt;dev)
             -&amp;gt; v4l2_device_release()
                -&amp;gt; vdev-&amp;gt;release(vdev)
                   -&amp;gt; video_device_release(vdev)&lt;/p&gt;
&lt;p&gt;comp_register_videodev()
    -&amp;gt; video_device_release(mdev-&amp;gt;vdev)&lt;/p&gt;
&lt;p&gt;Use video_device_release_empty() while registering the device so that
registration failure paths do not free mdev-&amp;gt;vdev through vdev-&amp;gt;release().
comp_register_videodev() then releases mdev-&amp;gt;vdev exactly once on failure.
Restore video_device_release() after successful registration so the
registered device keeps its normal lifetime handling.&lt;/p&gt;
&lt;p&gt;This issue was found by a static analysis tool I am developing.&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;staging: most: video: avoid double free on video register failure&lt;/p&gt;
&lt;p&gt;comp_register_videodev() allocates a video_device with
video_device_alloc() and releases it if video_register_device() fails.&lt;/p&gt;
&lt;p&gt;This can double free the video_device when __video_register_device()
reaches device_register() and that call fails:&lt;/p&gt;
&lt;p&gt;video_register_device()
    -&amp;gt; __video_register_device()
       -&amp;gt; device_register() fails
          -&amp;gt; put_device(&amp;amp;vdev-&amp;gt;dev)
             -&amp;gt; v4l2_device_release()
                -&amp;gt; vdev-&amp;gt;release(vdev)
                   -&amp;gt; video_device_release(vdev)&lt;/p&gt;
&lt;p&gt;comp_register_videodev()
    -&amp;gt; video_device_release(mdev-&amp;gt;vdev)&lt;/p&gt;
&lt;p&gt;Use video_device_release_empty() while registering the device so that
registration failure paths do not free mdev-&amp;gt;vdev through vdev-&amp;gt;release().
comp_register_videodev() then releases mdev-&amp;gt;vdev exactly once on failure.
Restore video_device_release() after successful registration so the
registered device keeps its normal lifetime handling.&lt;/p&gt;
&lt;p&gt;This issue was found by a static analysis tool I am developing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-79gv-9p52-g5cr</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72484</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72484</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: staging: most: video: avoid double free on video register failure comp_register_videodev() allocates a video_device with video_device_alloc() and releases it if video_register_device() fails. This can double free the video_device when __video_register_device() reaches device_register() and that call fails:   video_register_device()     -&amp;gt; __video_register_device()        -&amp;gt; device_register() fails           -&amp;gt; put_device(&amp;amp;vdev-&amp;gt;dev)              -&amp;gt; v4l2_device_release()                 -&amp;gt; vdev-&amp;gt;release(vdev)                    -&amp;gt; video_device_release(vdev)   comp_register_videodev()     -&amp;gt; video_device_release(mdev-&amp;gt;vdev) Use video_device_release_empty() while registering the device so that registration failure paths do not free mdev-&amp;gt;vdev through vdev-&amp;gt;release(). comp_register_videodev() then releases mdev-&amp;gt;vdev exactly once on failure. Restore video_device_release() after successful registration so the registered device keeps its normal lifetime handling. This issue was found by a static analysis tool I am developing.&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: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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: staging: most: video: avoid double free on video register failure comp_register_videodev() allocates a video_device with video_device_alloc() and releases it if video_register_device() fails. This can double free the video_device when __video_register_device() reaches device_register() and that call fails:   video_register_device()     -&amp;gt; __video_register_device()        -&amp;gt; device_register() fails           -&amp;gt; put_device(&amp;amp;vdev-&amp;gt;dev)              -&amp;gt; v4l2_device_release()                 -&amp;gt; vdev-&amp;gt;release(vdev)                    -&amp;gt; video_device_release(vdev)   comp_register_videodev()     -&amp;gt; video_device_release(mdev-&amp;gt;vdev) Use video_device_release_empty() while registering the device so that registration failure paths do not free mdev-&amp;gt;vdev through vdev-&amp;gt;release(). comp_register_videodev() then releases mdev-&amp;gt;vdev exactly once on failure. Restore video_device_release() after successful registration so the registered device keeps its normal lifetime handling. This issue was found by a static analysis tool I am developing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72484</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
