<?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 15:40:47 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07861</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07861</link>
      <description>bdu:2025-07861</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07861</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-56613</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-56613</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-2024-56613</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0254 — 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-0254</link>
      <description>certfr-2025-avi-0254</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0254</guid>
    </item>
    <item>
      <title>EUVD-2026-313759</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313759</link>
      <description>EUVD-2026-313759</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313759</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56613</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56613</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/numa: fix memory leak due to the overwritten vma-&amp;gt;numab_state&lt;/p&gt;
&lt;p&gt;[Problem Description]
When running the hackbench program of LTP, the following memory leak is
reported by kmemleak.&lt;/p&gt;
&lt;p&gt;# /opt/ltp/testcases/bin/hackbench 20 thread 1000
  Running with 20*40 (== 800) tasks.&lt;/p&gt;
&lt;p&gt;# dmesg | grep kmemleak
  ...
  kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
  kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kmemleak
  unreferenced object 0xffff888cd8ca2c40 (size 64):
    comm &amp;#34;hackbench&amp;#34;, pid 17142, jiffies 4299780315
    hex dump (first 32 bytes):
      ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    backtrace (crc bff18fd4):
      [&amp;lt;ffffffff81419a89&amp;gt;] __kmalloc_cache_noprof+0x2f9/0x3f0
      [&amp;lt;ffffffff8113f715&amp;gt;] task_numa_work+0x725/0xa00
      [&amp;lt;ffffffff8110f878&amp;gt;] task_work_run+0x58/0x90
      [&amp;lt;ffffffff81ddd9f8&amp;gt;] syscall_exit_to_user_mode+0x1c8/0x1e0
      [&amp;lt;ffffffff81dd78d5&amp;gt;] do_syscall_64+0x85/0x150
      [&amp;lt;ffffffff81e0012b&amp;gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e
  ...&lt;/p&gt;
&lt;p&gt;This issue can be consistently reproduced on three different servers:
  * a 448-core server
  * a 256-core server
  * a 192-core server&lt;/p&gt;
&lt;p&gt;[Root Cause]
Since multiple threads are created by the hackbench program (along with
the command argument &amp;#39;thread&amp;#39;), a shared vma…&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;sched/numa: fix memory leak due to the overwritten vma-&amp;gt;numab_state&lt;/p&gt;
&lt;p&gt;[Problem Description]
When running the hackbench program of LTP, the following memory leak is
reported by kmemleak.&lt;/p&gt;
&lt;p&gt;# /opt/ltp/testcases/bin/hackbench 20 thread 1000
  Running with 20*40 (== 800) tasks.&lt;/p&gt;
&lt;p&gt;# dmesg | grep kmemleak
  ...
  kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
  kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kmemleak
  unreferenced object 0xffff888cd8ca2c40 (size 64):
    comm &amp;#34;hackbench&amp;#34;, pid 17142, jiffies 4299780315
    hex dump (first 32 bytes):
      ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    backtrace (crc bff18fd4):
      [&amp;lt;ffffffff81419a89&amp;gt;] __kmalloc_cache_noprof+0x2f9/0x3f0
      [&amp;lt;ffffffff8113f715&amp;gt;] task_numa_work+0x725/0xa00
      [&amp;lt;ffffffff8110f878&amp;gt;] task_work_run+0x58/0x90
      [&amp;lt;ffffffff81ddd9f8&amp;gt;] syscall_exit_to_user_mode+0x1c8/0x1e0
      [&amp;lt;ffffffff81dd78d5&amp;gt;] do_syscall_64+0x85/0x150
      [&amp;lt;ffffffff81e0012b&amp;gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e
  ...&lt;/p&gt;
&lt;p&gt;This issue can be consistently reproduced on three different servers:
  * a 448-core server
  * a 256-core server
  * a 192-core server&lt;/p&gt;
&lt;p&gt;[Root Cause]
Since multiple threads are created by the hackbench program (along with
the command argument &amp;#39;thread&amp;#39;), a shared vma…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56613</guid>
    </item>
    <item>
      <title>GHSA-qqv2-5qvx-v346</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qqv2-5qvx-v346</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/numa: fix memory leak due to the overwritten vma-&amp;gt;numab_state&lt;/p&gt;
&lt;p&gt;[Problem Description]
When running the hackbench program of LTP, the following memory leak is
reported by kmemleak.&lt;/p&gt;
&lt;p&gt;# /opt/ltp/testcases/bin/hackbench 20 thread 1000
  Running with 20*40 (== 800) tasks.&lt;/p&gt;
&lt;p&gt;# dmesg | grep kmemleak
  ...
  kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
  kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kmemleak
  unreferenced object 0xffff888cd8ca2c40 (size 64):
    comm &amp;#34;hackbench&amp;#34;, pid 17142, jiffies 4299780315
    hex dump (first 32 bytes):
      ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    backtrace (crc bff18fd4):
      [&amp;lt;ffffffff81419a89&amp;gt;] __kmalloc_cache_noprof+0x2f9/0x3f0
      [&amp;lt;ffffffff8113f715&amp;gt;] task_numa_work+0x725/0xa00
      [&amp;lt;ffffffff8110f878&amp;gt;] task_work_run+0x58/0x90
      [&amp;lt;ffffffff81ddd9f8&amp;gt;] syscall_exit_to_user_mode+0x1c8/0x1e0
      [&amp;lt;ffffffff81dd78d5&amp;gt;] do_syscall_64+0x85/0x150
      [&amp;lt;ffffffff81e0012b&amp;gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e
  ...&lt;/p&gt;
&lt;p&gt;This issue can be consistently reproduced on three different servers:
  * a 448-core server
  * a 256-core server
  * a 192-core server&lt;/p&gt;
&lt;p&gt;[Root Cause]
Since multiple threads are created by the hackbench program (along with
the command argument &amp;#39;thread&amp;#39;), a shared vma…&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;sched/numa: fix memory leak due to the overwritten vma-&amp;gt;numab_state&lt;/p&gt;
&lt;p&gt;[Problem Description]
When running the hackbench program of LTP, the following memory leak is
reported by kmemleak.&lt;/p&gt;
&lt;p&gt;# /opt/ltp/testcases/bin/hackbench 20 thread 1000
  Running with 20*40 (== 800) tasks.&lt;/p&gt;
&lt;p&gt;# dmesg | grep kmemleak
  ...
  kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
  kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kmemleak
  unreferenced object 0xffff888cd8ca2c40 (size 64):
    comm &amp;#34;hackbench&amp;#34;, pid 17142, jiffies 4299780315
    hex dump (first 32 bytes):
      ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    backtrace (crc bff18fd4):
      [&amp;lt;ffffffff81419a89&amp;gt;] __kmalloc_cache_noprof+0x2f9/0x3f0
      [&amp;lt;ffffffff8113f715&amp;gt;] task_numa_work+0x725/0xa00
      [&amp;lt;ffffffff8110f878&amp;gt;] task_work_run+0x58/0x90
      [&amp;lt;ffffffff81ddd9f8&amp;gt;] syscall_exit_to_user_mode+0x1c8/0x1e0
      [&amp;lt;ffffffff81dd78d5&amp;gt;] do_syscall_64+0x85/0x150
      [&amp;lt;ffffffff81e0012b&amp;gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e
  ...&lt;/p&gt;
&lt;p&gt;This issue can be consistently reproduced on three different servers:
  * a 448-core server
  * a 256-core server
  * a 192-core server&lt;/p&gt;
&lt;p&gt;[Root Cause]
Since multiple threads are created by the hackbench program (along with
the command argument &amp;#39;thread&amp;#39;), a shared vma…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qqv2-5qvx-v346</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-56613 — sched/numa: fix memory leak due to the overwritten vma-&gt;numab_state</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-56613</link>
      <description>msrc_CVE-2024-56613</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-56613</guid>
    </item>
    <item>
      <title>OESA-2025-1078 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1078</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:&lt;/p&gt;
&lt;p&gt;net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new&lt;/p&gt;
&lt;p&gt;This patch enhances error handling in scenarios with RTS (Request to
Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
backtraces with a new error handling method. This provides clearer error
messages and allows for the early termination of problematic sessions.
Previously, sessions were only released at the end of j1939_xtp_rx_rts().&lt;/p&gt;
&lt;p&gt;Potentially this could be reproduced with something like:
testj1939 -r vcan0:0x80 &amp;amp;amp;
while true; do
	# send first RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send second RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send abort
	cansend vcan0 18EC8090#ff00000000002301;
done(CVE-2023-52887)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;amp;c…&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:&lt;/p&gt;
&lt;p&gt;net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new&lt;/p&gt;
&lt;p&gt;This patch enhances error handling in scenarios with RTS (Request to
Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
backtraces with a new error handling method. This provides clearer error
messages and allows for the early termination of problematic sessions.
Previously, sessions were only released at the end of j1939_xtp_rx_rts().&lt;/p&gt;
&lt;p&gt;Potentially this could be reproduced with something like:
testj1939 -r vcan0:0x80 &amp;amp;amp;
while true; do
	# send first RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send second RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send abort
	cansend vcan0 18EC8090#ff00000000002301;
done(CVE-2023-52887)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;amp;c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1078</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02249-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02249-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:02249-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56613</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56613</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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/numa: fix memory leak due to the overwritten vma-&amp;gt;numab_state [Problem Description] When running the hackbench program of LTP, the following memory leak is reported by kmemleak.   # /opt/ltp/testcases/bin/hackbench 20 thread 1000   Running with 20*40 (== 800) tasks.   # dmesg | grep kmemleak   ...   kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)   kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)   # cat /sys/kernel/debug/kmemleak   unreferenced object 0xffff888cd8ca2c40 (size 64):     comm &amp;#34;hackbench&amp;#34;, pid 17142, jiffies 4299780315     hex dump (first 32 bytes):       ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     backtrace (crc bff18fd4):       [&amp;lt;ffffffff81419a89&amp;gt;] __kmalloc_cache_noprof+0x2f9/0x3f0       [&amp;lt;ffffffff8113f715&amp;gt;] task_numa_work+0x725/0xa00       [&amp;lt;ffffffff8110f878&amp;gt;] task_work_run+0x58/0x90       [&amp;lt;ffffffff81ddd9f8&amp;gt;] syscall_exit_to_user_mode+0x1c8/0x1e0       [&amp;lt;ffffffff81dd78d5&amp;gt;] do_syscall_64+0x85/0x150       [&amp;lt;ffffffff81e0012b&amp;gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e   ... This issue can be consistently reproduced on three different servers:   * a 448-core server   * a 256-core server   * a 192-core server [Root Cause] Since multiple threads are created by the hackbench program (along with the command argument &amp;#39;thread&amp;#39;), a shared vma might…&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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/numa: fix memory leak due to the overwritten vma-&amp;gt;numab_state [Problem Description] When running the hackbench program of LTP, the following memory leak is reported by kmemleak.   # /opt/ltp/testcases/bin/hackbench 20 thread 1000   Running with 20*40 (== 800) tasks.   # dmesg | grep kmemleak   ...   kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)   kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)   # cat /sys/kernel/debug/kmemleak   unreferenced object 0xffff888cd8ca2c40 (size 64):     comm &amp;#34;hackbench&amp;#34;, pid 17142, jiffies 4299780315     hex dump (first 32 bytes):       ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     backtrace (crc bff18fd4):       [&amp;lt;ffffffff81419a89&amp;gt;] __kmalloc_cache_noprof+0x2f9/0x3f0       [&amp;lt;ffffffff8113f715&amp;gt;] task_numa_work+0x725/0xa00       [&amp;lt;ffffffff8110f878&amp;gt;] task_work_run+0x58/0x90       [&amp;lt;ffffffff81ddd9f8&amp;gt;] syscall_exit_to_user_mode+0x1c8/0x1e0       [&amp;lt;ffffffff81dd78d5&amp;gt;] do_syscall_64+0x85/0x150       [&amp;lt;ffffffff81e0012b&amp;gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e   ... This issue can be consistently reproduced on three different servers:   * a 448-core server   * a 256-core server   * a 192-core server [Root Cause] Since multiple threads are created by the hackbench program (along with the command argument &amp;#39;thread&amp;#39;), a shared vma might…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56613</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>
