<?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 03:13:54 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-06808</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-06808</link>
      <description>bdu:2025-06808</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-06808</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53178</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53178</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-2024-53178</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>EUVD-2026-346434</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346434</link>
      <description>EUVD-2026-346434</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346434</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53178</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53178</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: Don&amp;#39;t leak cfid when reconnect races with open_cached_dir&lt;/p&gt;
&lt;p&gt;open_cached_dir() may either race with the tcon reconnection even before
compound_send_recv() or directly trigger a reconnection via
SMB2_open_init() or SMB_query_info_init().&lt;/p&gt;
&lt;p&gt;The reconnection process invokes invalidate_all_cached_dirs() via
cifs_mark_open_files_invalid(), which removes all cfids from the
cfids-&amp;gt;entries list but doesn&amp;#39;t drop a ref if has_lease isn&amp;#39;t true. This
results in the currently-being-constructed cfid not being on the list,
but still having a refcount of 2. It leaks if returned from
open_cached_dir().&lt;/p&gt;
&lt;p&gt;Fix this by setting cfid-&amp;gt;has_lease when the ref is actually taken; the
cfid will not be used by other threads until it has a valid time.&lt;/p&gt;
&lt;p&gt;Addresses these kmemleaks:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881090c4000 (size 1024):
  comm &amp;#34;bash&amp;#34;, pid 1860, jiffies 4295126592
  hex dump (first 32 bytes):
    00 01 00 00 00 00 ad de 22 01 00 00 00 00 ad de  ........&amp;#34;.......
    00 ca 45 22 81 88 ff ff f8 dc 4f 04 81 88 ff ff  ..E&amp;#34;......O.....
  backtrace (crc 6f58c20f):
    [&amp;lt;ffffffff8b895a1e&amp;gt;] __kmalloc_cache_noprof+0x2be/0x350
    [&amp;lt;ffffffff8bda06e3&amp;gt;] open_cached_dir+0x993/0x1fb0
    [&amp;lt;ffffffff8bdaa750&amp;gt;] cifs_readdir+0x15a0/0x1d50
    [&amp;lt;ffffffff8b9a853f&amp;gt;] iterate_dir+0x28f/0x4b0
    [&amp;lt;ffffffff8b9a9aed&amp;gt;] __x64_sys_getdents64+0xfd/0x200
    [&amp;lt;ffffffff8cf6da05&amp;gt;] do_syscall_64+0x95/0x1a0
    [&amp;lt;ffffffff8d00012f&amp;gt;] entry_SYSCALL_64_after_hwfr…&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;smb: Don&amp;#39;t leak cfid when reconnect races with open_cached_dir&lt;/p&gt;
&lt;p&gt;open_cached_dir() may either race with the tcon reconnection even before
compound_send_recv() or directly trigger a reconnection via
SMB2_open_init() or SMB_query_info_init().&lt;/p&gt;
&lt;p&gt;The reconnection process invokes invalidate_all_cached_dirs() via
cifs_mark_open_files_invalid(), which removes all cfids from the
cfids-&amp;gt;entries list but doesn&amp;#39;t drop a ref if has_lease isn&amp;#39;t true. This
results in the currently-being-constructed cfid not being on the list,
but still having a refcount of 2. It leaks if returned from
open_cached_dir().&lt;/p&gt;
&lt;p&gt;Fix this by setting cfid-&amp;gt;has_lease when the ref is actually taken; the
cfid will not be used by other threads until it has a valid time.&lt;/p&gt;
&lt;p&gt;Addresses these kmemleaks:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881090c4000 (size 1024):
  comm &amp;#34;bash&amp;#34;, pid 1860, jiffies 4295126592
  hex dump (first 32 bytes):
    00 01 00 00 00 00 ad de 22 01 00 00 00 00 ad de  ........&amp;#34;.......
    00 ca 45 22 81 88 ff ff f8 dc 4f 04 81 88 ff ff  ..E&amp;#34;......O.....
  backtrace (crc 6f58c20f):
    [&amp;lt;ffffffff8b895a1e&amp;gt;] __kmalloc_cache_noprof+0x2be/0x350
    [&amp;lt;ffffffff8bda06e3&amp;gt;] open_cached_dir+0x993/0x1fb0
    [&amp;lt;ffffffff8bdaa750&amp;gt;] cifs_readdir+0x15a0/0x1d50
    [&amp;lt;ffffffff8b9a853f&amp;gt;] iterate_dir+0x28f/0x4b0
    [&amp;lt;ffffffff8b9a9aed&amp;gt;] __x64_sys_getdents64+0xfd/0x200
    [&amp;lt;ffffffff8cf6da05&amp;gt;] do_syscall_64+0x95/0x1a0
    [&amp;lt;ffffffff8d00012f&amp;gt;] entry_SYSCALL_64_after_hwfr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53178</guid>
    </item>
    <item>
      <title>GHSA-cg3f-qqrv-qxm5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cg3f-qqrv-qxm5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: Don&amp;#39;t leak cfid when reconnect races with open_cached_dir&lt;/p&gt;
&lt;p&gt;open_cached_dir() may either race with the tcon reconnection even before
compound_send_recv() or directly trigger a reconnection via
SMB2_open_init() or SMB_query_info_init().&lt;/p&gt;
&lt;p&gt;The reconnection process invokes invalidate_all_cached_dirs() via
cifs_mark_open_files_invalid(), which removes all cfids from the
cfids-&amp;gt;entries list but doesn&amp;#39;t drop a ref if has_lease isn&amp;#39;t true. This
results in the currently-being-constructed cfid not being on the list,
but still having a refcount of 2. It leaks if returned from
open_cached_dir().&lt;/p&gt;
&lt;p&gt;Fix this by setting cfid-&amp;gt;has_lease when the ref is actually taken; the
cfid will not be used by other threads until it has a valid time.&lt;/p&gt;
&lt;p&gt;Addresses these kmemleaks:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881090c4000 (size 1024):
  comm &amp;#34;bash&amp;#34;, pid 1860, jiffies 4295126592
  hex dump (first 32 bytes):
    00 01 00 00 00 00 ad de 22 01 00 00 00 00 ad de  ........&amp;#34;.......
    00 ca 45 22 81 88 ff ff f8 dc 4f 04 81 88 ff ff  ..E&amp;#34;......O.....
  backtrace (crc 6f58c20f):
    [&amp;lt;ffffffff8b895a1e&amp;gt;] __kmalloc_cache_noprof+0x2be/0x350
    [&amp;lt;ffffffff8bda06e3&amp;gt;] open_cached_dir+0x993/0x1fb0
    [&amp;lt;ffffffff8bdaa750&amp;gt;] cifs_readdir+0x15a0/0x1d50
    [&amp;lt;ffffffff8b9a853f&amp;gt;] iterate_dir+0x28f/0x4b0
    [&amp;lt;ffffffff8b9a9aed&amp;gt;] __x64_sys_getdents64+0xfd/0x200
    [&amp;lt;ffffffff8cf6da05&amp;gt;] do_syscall_64+0x95/0x1a0
    [&amp;lt;ffffffff8d00012f&amp;gt;] entry_SYSCALL_64_after_hwfr…&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;smb: Don&amp;#39;t leak cfid when reconnect races with open_cached_dir&lt;/p&gt;
&lt;p&gt;open_cached_dir() may either race with the tcon reconnection even before
compound_send_recv() or directly trigger a reconnection via
SMB2_open_init() or SMB_query_info_init().&lt;/p&gt;
&lt;p&gt;The reconnection process invokes invalidate_all_cached_dirs() via
cifs_mark_open_files_invalid(), which removes all cfids from the
cfids-&amp;gt;entries list but doesn&amp;#39;t drop a ref if has_lease isn&amp;#39;t true. This
results in the currently-being-constructed cfid not being on the list,
but still having a refcount of 2. It leaks if returned from
open_cached_dir().&lt;/p&gt;
&lt;p&gt;Fix this by setting cfid-&amp;gt;has_lease when the ref is actually taken; the
cfid will not be used by other threads until it has a valid time.&lt;/p&gt;
&lt;p&gt;Addresses these kmemleaks:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881090c4000 (size 1024):
  comm &amp;#34;bash&amp;#34;, pid 1860, jiffies 4295126592
  hex dump (first 32 bytes):
    00 01 00 00 00 00 ad de 22 01 00 00 00 00 ad de  ........&amp;#34;.......
    00 ca 45 22 81 88 ff ff f8 dc 4f 04 81 88 ff ff  ..E&amp;#34;......O.....
  backtrace (crc 6f58c20f):
    [&amp;lt;ffffffff8b895a1e&amp;gt;] __kmalloc_cache_noprof+0x2be/0x350
    [&amp;lt;ffffffff8bda06e3&amp;gt;] open_cached_dir+0x993/0x1fb0
    [&amp;lt;ffffffff8bdaa750&amp;gt;] cifs_readdir+0x15a0/0x1d50
    [&amp;lt;ffffffff8b9a853f&amp;gt;] iterate_dir+0x28f/0x4b0
    [&amp;lt;ffffffff8b9a9aed&amp;gt;] __x64_sys_getdents64+0xfd/0x200
    [&amp;lt;ffffffff8cf6da05&amp;gt;] do_syscall_64+0x95/0x1a0
    [&amp;lt;ffffffff8d00012f&amp;gt;] entry_SYSCALL_64_after_hwfr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cg3f-qqrv-qxm5</guid>
    </item>
    <item>
      <title>OESA-2025-1286 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1286</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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:&lt;/p&gt;
&lt;p&gt;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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:&lt;/p&gt;
&lt;p&gt;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1286</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01919-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01919-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:01919-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53178</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53178</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: Don&amp;#39;t leak cfid when reconnect races with open_cached_dir open_cached_dir() may either race with the tcon reconnection even before compound_send_recv() or directly trigger a reconnection via SMB2_open_init() or SMB_query_info_init(). The reconnection process invokes invalidate_all_cached_dirs() via cifs_mark_open_files_invalid(), which removes all cfids from the cfids-&amp;gt;entries list but doesn&amp;#39;t drop a ref if has_lease isn&amp;#39;t true. This results in the currently-being-constructed cfid not being on the list, but still having a refcount of 2. It leaks if returned from open_cached_dir(). Fix this by setting cfid-&amp;gt;has_lease when the ref is actually taken; the cfid will not be used by other threads until it has a valid time. Addresses these kmemleaks: unreferenced object 0xffff8881090c4000 (size 1024):   comm &amp;#34;bash&amp;#34;, pid 1860, jiffies 4295126592   hex dump (first 32 bytes):     00 01 00 00 00 00 ad de 22 01 00 00 00 00 ad de  ........&amp;#34;.......     00 ca 45 22 81 88 ff ff f8 dc 4f 04 81 88 ff ff  ..E&amp;#34;......O.....   backtrace (crc 6f58c20f):     [&amp;lt;ffffffff8b895a1e&amp;gt;] __kmalloc_cache_noprof+0x2be/0x350     [&amp;lt;ffffffff8bda06e3&amp;gt;] open_cached_dir+0x993/0x1fb0     [&amp;lt;ffffffff8bdaa750&amp;gt;] cifs_readdir+0x15a0/0x1d50     [&amp;lt;ffffffff8b9a853f&amp;gt;] iterate_dir+0x28f/0x4b0     [&amp;lt;ffffffff8b9a9aed&amp;gt;] __x64_sys_getdents64+0xfd/0x200     [&amp;lt;ffffffff8cf6da05&amp;gt;] do_syscall_64+0x95/0x1a0     [&amp;lt;ffffffff8d00012f&amp;gt;] entry_SYSCALL_64_after_hwframe+0x…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: Don&amp;#39;t leak cfid when reconnect races with open_cached_dir open_cached_dir() may either race with the tcon reconnection even before compound_send_recv() or directly trigger a reconnection via SMB2_open_init() or SMB_query_info_init(). The reconnection process invokes invalidate_all_cached_dirs() via cifs_mark_open_files_invalid(), which removes all cfids from the cfids-&amp;gt;entries list but doesn&amp;#39;t drop a ref if has_lease isn&amp;#39;t true. This results in the currently-being-constructed cfid not being on the list, but still having a refcount of 2. It leaks if returned from open_cached_dir(). Fix this by setting cfid-&amp;gt;has_lease when the ref is actually taken; the cfid will not be used by other threads until it has a valid time. Addresses these kmemleaks: unreferenced object 0xffff8881090c4000 (size 1024):   comm &amp;#34;bash&amp;#34;, pid 1860, jiffies 4295126592   hex dump (first 32 bytes):     00 01 00 00 00 00 ad de 22 01 00 00 00 00 ad de  ........&amp;#34;.......     00 ca 45 22 81 88 ff ff f8 dc 4f 04 81 88 ff ff  ..E&amp;#34;......O.....   backtrace (crc 6f58c20f):     [&amp;lt;ffffffff8b895a1e&amp;gt;] __kmalloc_cache_noprof+0x2be/0x350     [&amp;lt;ffffffff8bda06e3&amp;gt;] open_cached_dir+0x993/0x1fb0     [&amp;lt;ffffffff8bdaa750&amp;gt;] cifs_readdir+0x15a0/0x1d50     [&amp;lt;ffffffff8b9a853f&amp;gt;] iterate_dir+0x28f/0x4b0     [&amp;lt;ffffffff8b9a9aed&amp;gt;] __x64_sys_getdents64+0xfd/0x200     [&amp;lt;ffffffff8cf6da05&amp;gt;] do_syscall_64+0x95/0x1a0     [&amp;lt;ffffffff8d00012f&amp;gt;] entry_SYSCALL_64_after_hwframe+0x…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53178</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3762 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</guid>
    </item>
  </channel>
</rss>
