<?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 05:55:00 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07403</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07403</link>
      <description>bdu:2025-07403</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07403</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-309684</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309684</link>
      <description>EUVD-2026-309684</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309684</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47344</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47344</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: zr364xx: fix memory leak in zr364xx_start_readpipe&lt;/p&gt;
&lt;p&gt;syzbot reported memory leak in zr364xx driver.
The problem was in non-freed urb in case of
usb_submit_urb() fail.&lt;/p&gt;
&lt;p&gt;backtrace:
  [&amp;lt;ffffffff82baedf6&amp;gt;] kmalloc include/linux/slab.h:561 [inline]
  [&amp;lt;ffffffff82baedf6&amp;gt;] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
  [&amp;lt;ffffffff82f7cce8&amp;gt;] zr364xx_start_readpipe+0x78/0x130 drivers/media/usb/zr364xx/zr364xx.c:1022
  [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1383 [inline]
  [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_probe+0x6a3/0x851 drivers/media/usb/zr364xx/zr364xx.c:1516
  [&amp;lt;ffffffff82bb6507&amp;gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
  [&amp;lt;ffffffff826018a9&amp;gt;] really_probe+0x159/0x500 drivers/base/dd.c:576&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;media: zr364xx: fix memory leak in zr364xx_start_readpipe&lt;/p&gt;
&lt;p&gt;syzbot reported memory leak in zr364xx driver.
The problem was in non-freed urb in case of
usb_submit_urb() fail.&lt;/p&gt;
&lt;p&gt;backtrace:
  [&amp;lt;ffffffff82baedf6&amp;gt;] kmalloc include/linux/slab.h:561 [inline]
  [&amp;lt;ffffffff82baedf6&amp;gt;] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
  [&amp;lt;ffffffff82f7cce8&amp;gt;] zr364xx_start_readpipe+0x78/0x130 drivers/media/usb/zr364xx/zr364xx.c:1022
  [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1383 [inline]
  [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_probe+0x6a3/0x851 drivers/media/usb/zr364xx/zr364xx.c:1516
  [&amp;lt;ffffffff82bb6507&amp;gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
  [&amp;lt;ffffffff826018a9&amp;gt;] really_probe+0x159/0x500 drivers/base/dd.c:576&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47344</guid>
    </item>
    <item>
      <title>GHSA-hm5p-668j-x4q6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hm5p-668j-x4q6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: zr364xx: fix memory leak in zr364xx_start_readpipe&lt;/p&gt;
&lt;p&gt;syzbot reported memory leak in zr364xx driver.
The problem was in non-freed urb in case of
usb_submit_urb() fail.&lt;/p&gt;
&lt;p&gt;backtrace:
  [&amp;lt;ffffffff82baedf6&amp;gt;] kmalloc include/linux/slab.h:561 [inline]
  [&amp;lt;ffffffff82baedf6&amp;gt;] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
  [&amp;lt;ffffffff82f7cce8&amp;gt;] zr364xx_start_readpipe+0x78/0x130 drivers/media/usb/zr364xx/zr364xx.c:1022
  [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1383 [inline]
  [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_probe+0x6a3/0x851 drivers/media/usb/zr364xx/zr364xx.c:1516
  [&amp;lt;ffffffff82bb6507&amp;gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
  [&amp;lt;ffffffff826018a9&amp;gt;] really_probe+0x159/0x500 drivers/base/dd.c:576&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;media: zr364xx: fix memory leak in zr364xx_start_readpipe&lt;/p&gt;
&lt;p&gt;syzbot reported memory leak in zr364xx driver.
The problem was in non-freed urb in case of
usb_submit_urb() fail.&lt;/p&gt;
&lt;p&gt;backtrace:
  [&amp;lt;ffffffff82baedf6&amp;gt;] kmalloc include/linux/slab.h:561 [inline]
  [&amp;lt;ffffffff82baedf6&amp;gt;] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74
  [&amp;lt;ffffffff82f7cce8&amp;gt;] zr364xx_start_readpipe+0x78/0x130 drivers/media/usb/zr364xx/zr364xx.c:1022
  [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1383 [inline]
  [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_probe+0x6a3/0x851 drivers/media/usb/zr364xx/zr364xx.c:1516
  [&amp;lt;ffffffff82bb6507&amp;gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
  [&amp;lt;ffffffff826018a9&amp;gt;] really_probe+0x159/0x500 drivers/base/dd.c:576&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hm5p-668j-x4q6</guid>
    </item>
    <item>
      <title>OESA-2024-1736 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1736</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
PCI: aardvark: Fix kernel panic during PIO transfer&#13;
&#13;
Trying to start a new PIO transfer by writing value 0 in PIO_START register
when previous transfer has not yet completed (which is indicated by value 1
in PIO_START) causes an External Abort on CPU, which results in kernel
panic:&#13;
&#13;
    SError Interrupt on CPU0, code 0xbf000002 -- SError
    Kernel panic - not syncing: Asynchronous SError Interrupt&#13;
&#13;
To prevent kernel panic, it is required to reject a new PIO transfer when
previous one has not finished yet.&#13;
&#13;
If previous PIO transfer is not finished yet, the kernel may issue a new
PIO request only if the previous PIO transfer timed out.&#13;
&#13;
In the past the root cause of this issue was incorrectly identified (as it
often happens during link retraining or after link down event) and special
hack was implemented in Trusted Firmware to catch all SError events in EL3,
to ignore errors with code 0xbf000002 and not forwarding any other errors
to kernel and instead throw panic from EL3 Trusted Firmware handler.&#13;
&#13;
Links to discussion and patches about this issue:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=3c7dcdac5c50
https://lore.kernel.org/linux-pci/20190316161243.29517-1-repk@triplefau.lt/
https://lore.kernel.org/linux-pci/971be151d24312cc533989a64bd454b4@www.loen.fr/
https://review.trustedfirmware.org/c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
PCI: aardvark: Fix kernel panic during PIO transfer&#13;
&#13;
Trying to start a new PIO transfer by writing value 0 in PIO_START register
when previous transfer has not yet completed (which is indicated by value 1
in PIO_START) causes an External Abort on CPU, which results in kernel
panic:&#13;
&#13;
    SError Interrupt on CPU0, code 0xbf000002 -- SError
    Kernel panic - not syncing: Asynchronous SError Interrupt&#13;
&#13;
To prevent kernel panic, it is required to reject a new PIO transfer when
previous one has not finished yet.&#13;
&#13;
If previous PIO transfer is not finished yet, the kernel may issue a new
PIO request only if the previous PIO transfer timed out.&#13;
&#13;
In the past the root cause of this issue was incorrectly identified (as it
often happens during link retraining or after link down event) and special
hack was implemented in Trusted Firmware to catch all SError events in EL3,
to ignore errors with code 0xbf000002 and not forwarding any other errors
to kernel and instead throw panic from EL3 Trusted Firmware handler.&#13;
&#13;
Links to discussion and patches about this issue:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=3c7dcdac5c50
https://lore.kernel.org/linux-pci/20190316161243.29517-1-repk@triplefau.lt/
https://lore.kernel.org/linux-pci/971be151d24312cc533989a64bd454b4@www.loen.fr/
https://review.trustedfirmware.org/c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1736</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-47344</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47344</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 107 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: zr364xx: fix memory leak in zr364xx_start_readpipe syzbot reported memory leak in zr364xx driver. The problem was in non-freed urb in case of usb_submit_urb() fail. backtrace:   [&amp;lt;ffffffff82baedf6&amp;gt;] kmalloc include/linux/slab.h:561 [inline]   [&amp;lt;ffffffff82baedf6&amp;gt;] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74   [&amp;lt;ffffffff82f7cce8&amp;gt;] zr364xx_start_readpipe+0x78/0x130 drivers/media/usb/zr364xx/zr364xx.c:1022   [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1383 [inline]   [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_probe+0x6a3/0x851 drivers/media/usb/zr364xx/zr364xx.c:1516   [&amp;lt;ffffffff82bb6507&amp;gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396   [&amp;lt;ffffffff826018a9&amp;gt;] really_probe+0x159/0x500 drivers/base/dd.c:576&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 107 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: zr364xx: fix memory leak in zr364xx_start_readpipe syzbot reported memory leak in zr364xx driver. The problem was in non-freed urb in case of usb_submit_urb() fail. backtrace:   [&amp;lt;ffffffff82baedf6&amp;gt;] kmalloc include/linux/slab.h:561 [inline]   [&amp;lt;ffffffff82baedf6&amp;gt;] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74   [&amp;lt;ffffffff82f7cce8&amp;gt;] zr364xx_start_readpipe+0x78/0x130 drivers/media/usb/zr364xx/zr364xx.c:1022   [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1383 [inline]   [&amp;lt;ffffffff84251dfc&amp;gt;] zr364xx_probe+0x6a3/0x851 drivers/media/usb/zr364xx/zr364xx.c:1516   [&amp;lt;ffffffff82bb6507&amp;gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396   [&amp;lt;ffffffff826018a9&amp;gt;] really_probe+0x159/0x500 drivers/base/dd.c:576&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47344</guid>
    </item>
  </channel>
</rss>
