<?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 05:03:17 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-09674</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-09674</link>
      <description>bdu:2025-09674</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-09674</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38181</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38181</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-38181</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0668 — 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-2025-avi-0668</link>
      <description>certfr-2025-avi-0668</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0668</guid>
    </item>
    <item>
      <title>EUVD-2026-346955</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346955</link>
      <description>EUVD-2026-346955</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346955</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38181</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38181</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;calipso: Fix null-ptr-deref in calipso_req_{set,del}attr().&lt;/p&gt;
&lt;p&gt;syzkaller reported a null-ptr-deref in sock_omalloc() while allocating
a CALIPSO option.  [0]&lt;/p&gt;
&lt;p&gt;The NULL is of struct sock, which was fetched by sk_to_full_sk() in
calipso_req_setattr().&lt;/p&gt;
&lt;p&gt;Since commit a1a5344ddbe8 (&amp;#34;tcp: avoid two atomic ops for syncookies&amp;#34;),
reqsk-&amp;gt;rsk_listener could be NULL when SYN Cookie is returned to its
client, as hinted by the leading SYN Cookie log.&lt;/p&gt;
&lt;p&gt;Here are 3 options to fix the bug:&lt;/p&gt;
&lt;p&gt;1) Return 0 in calipso_req_setattr()
  2) Return an error in calipso_req_setattr()
  3) Alaways set rsk_listener&lt;/p&gt;
&lt;p&gt;1) is no go as it bypasses LSM, but 2) effectively disables SYN Cookie
for CALIPSO.  3) is also no go as there have been many efforts to reduce
atomic ops and make TCP robust against DDoS.  See also commit 3b24d854cb35
(&amp;#34;tcp/dccp: do not touch listener sk_refcnt under synflood&amp;#34;).&lt;/p&gt;
&lt;p&gt;As of the blamed commit, SYN Cookie already did not need refcounting,
and no one has stumbled on the bug for 9 years, so no CALIPSO user will
care about SYN Cookie.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s return an error in calipso_req_setattr() and calipso_req_delattr()
in the SYN Cookie case.&lt;/p&gt;
&lt;p&gt;This can be reproduced by [1] on Fedora and now connect() of nc times out.&lt;/p&gt;
&lt;p&gt;[0]:
TCP: request_sock_TCPv6: Possible SYN flooding on port [::]:20002. Sending cookies.
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN:…&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;calipso: Fix null-ptr-deref in calipso_req_{set,del}attr().&lt;/p&gt;
&lt;p&gt;syzkaller reported a null-ptr-deref in sock_omalloc() while allocating
a CALIPSO option.  [0]&lt;/p&gt;
&lt;p&gt;The NULL is of struct sock, which was fetched by sk_to_full_sk() in
calipso_req_setattr().&lt;/p&gt;
&lt;p&gt;Since commit a1a5344ddbe8 (&amp;#34;tcp: avoid two atomic ops for syncookies&amp;#34;),
reqsk-&amp;gt;rsk_listener could be NULL when SYN Cookie is returned to its
client, as hinted by the leading SYN Cookie log.&lt;/p&gt;
&lt;p&gt;Here are 3 options to fix the bug:&lt;/p&gt;
&lt;p&gt;1) Return 0 in calipso_req_setattr()
  2) Return an error in calipso_req_setattr()
  3) Alaways set rsk_listener&lt;/p&gt;
&lt;p&gt;1) is no go as it bypasses LSM, but 2) effectively disables SYN Cookie
for CALIPSO.  3) is also no go as there have been many efforts to reduce
atomic ops and make TCP robust against DDoS.  See also commit 3b24d854cb35
(&amp;#34;tcp/dccp: do not touch listener sk_refcnt under synflood&amp;#34;).&lt;/p&gt;
&lt;p&gt;As of the blamed commit, SYN Cookie already did not need refcounting,
and no one has stumbled on the bug for 9 years, so no CALIPSO user will
care about SYN Cookie.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s return an error in calipso_req_setattr() and calipso_req_delattr()
in the SYN Cookie case.&lt;/p&gt;
&lt;p&gt;This can be reproduced by [1] on Fedora and now connect() of nc times out.&lt;/p&gt;
&lt;p&gt;[0]:
TCP: request_sock_TCPv6: Possible SYN flooding on port [::]:20002. Sending cookies.
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38181</guid>
    </item>
    <item>
      <title>GHSA-5hp5-2vg6-w8h9</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5hp5-2vg6-w8h9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;calipso: Fix null-ptr-deref in calipso_req_{set,del}attr().&lt;/p&gt;
&lt;p&gt;syzkaller reported a null-ptr-deref in sock_omalloc() while allocating
a CALIPSO option.  [0]&lt;/p&gt;
&lt;p&gt;The NULL is of struct sock, which was fetched by sk_to_full_sk() in
calipso_req_setattr().&lt;/p&gt;
&lt;p&gt;Since commit a1a5344ddbe8 (&amp;#34;tcp: avoid two atomic ops for syncookies&amp;#34;),
reqsk-&amp;gt;rsk_listener could be NULL when SYN Cookie is returned to its
client, as hinted by the leading SYN Cookie log.&lt;/p&gt;
&lt;p&gt;Here are 3 options to fix the bug:&lt;/p&gt;
&lt;p&gt;1) Return 0 in calipso_req_setattr()
  2) Return an error in calipso_req_setattr()
  3) Alaways set rsk_listener&lt;/p&gt;
&lt;p&gt;1) is no go as it bypasses LSM, but 2) effectively disables SYN Cookie
for CALIPSO.  3) is also no go as there have been many efforts to reduce
atomic ops and make TCP robust against DDoS.  See also commit 3b24d854cb35
(&amp;#34;tcp/dccp: do not touch listener sk_refcnt under synflood&amp;#34;).&lt;/p&gt;
&lt;p&gt;As of the blamed commit, SYN Cookie already did not need refcounting,
and no one has stumbled on the bug for 9 years, so no CALIPSO user will
care about SYN Cookie.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s return an error in calipso_req_setattr() and calipso_req_delattr()
in the SYN Cookie case.&lt;/p&gt;
&lt;p&gt;This can be reproduced by [1] on Fedora and now connect() of nc times out.&lt;/p&gt;
&lt;p&gt;[0]:
TCP: request_sock_TCPv6: Possible SYN flooding on port [::]:20002. Sending cookies.
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN:…&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;calipso: Fix null-ptr-deref in calipso_req_{set,del}attr().&lt;/p&gt;
&lt;p&gt;syzkaller reported a null-ptr-deref in sock_omalloc() while allocating
a CALIPSO option.  [0]&lt;/p&gt;
&lt;p&gt;The NULL is of struct sock, which was fetched by sk_to_full_sk() in
calipso_req_setattr().&lt;/p&gt;
&lt;p&gt;Since commit a1a5344ddbe8 (&amp;#34;tcp: avoid two atomic ops for syncookies&amp;#34;),
reqsk-&amp;gt;rsk_listener could be NULL when SYN Cookie is returned to its
client, as hinted by the leading SYN Cookie log.&lt;/p&gt;
&lt;p&gt;Here are 3 options to fix the bug:&lt;/p&gt;
&lt;p&gt;1) Return 0 in calipso_req_setattr()
  2) Return an error in calipso_req_setattr()
  3) Alaways set rsk_listener&lt;/p&gt;
&lt;p&gt;1) is no go as it bypasses LSM, but 2) effectively disables SYN Cookie
for CALIPSO.  3) is also no go as there have been many efforts to reduce
atomic ops and make TCP robust against DDoS.  See also commit 3b24d854cb35
(&amp;#34;tcp/dccp: do not touch listener sk_refcnt under synflood&amp;#34;).&lt;/p&gt;
&lt;p&gt;As of the blamed commit, SYN Cookie already did not need refcounting,
and no one has stumbled on the bug for 9 years, so no CALIPSO user will
care about SYN Cookie.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s return an error in calipso_req_setattr() and calipso_req_delattr()
in the SYN Cookie case.&lt;/p&gt;
&lt;p&gt;This can be reproduced by [1] on Fedora and now connect() of nc times out.&lt;/p&gt;
&lt;p&gt;[0]:
TCP: request_sock_TCPv6: Possible SYN flooding on port [::]:20002. Sending cookies.
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5hp5-2vg6-w8h9</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38181 — calipso: Fix null-ptr-deref in calipso_req_{set,del}attr().</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38181</link>
      <description>msrc_CVE-2025-38181</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38181</guid>
    </item>
    <item>
      <title>OESA-2025-1959 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1959</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;xfrm: state: fix out-of-bounds read during lookup&lt;/p&gt;
&lt;p&gt;lookup and resize can run in parallel.&lt;/p&gt;
&lt;p&gt;The xfrm_state_hash_generation seqlock ensures a retry, but the hash
functions can observe a hmask value that is too large for the new hlist
array.&lt;/p&gt;
&lt;p&gt;rehash does:
  rcu_assign_pointer(net-&amp;amp;gt;xfrm.state_bydst, ndst) [..]
  net-&amp;amp;gt;xfrm.state_hmask = nhashmask;&lt;/p&gt;
&lt;p&gt;While state lookup does:
  h = xfrm_dst_hash(net, daddr, saddr, tmpl-&amp;amp;gt;reqid, encap_family);
  hlist_for_each_entry_rcu(x, net-&amp;amp;gt;xfrm.state_bydst + h, bydst) {&lt;/p&gt;
&lt;p&gt;This is only safe in case the update to state_bydst is larger than
net-&amp;amp;gt;xfrm.xfrm_state_hmask (or if the lookup function gets
serialized via state spinlock again).&lt;/p&gt;
&lt;p&gt;Fix this by prefetching state_hmask and the associated pointers.
The xfrm_state_hash_generation seqlock retry will ensure that the pointer
and the hmask will be consistent.&lt;/p&gt;
&lt;p&gt;The existing helpers, like xfrm_dst_hash(), are now unsafe for RCU side,
add lockdep assertions to document that they are only safe for insert
side.&lt;/p&gt;
&lt;p&gt;xfrm_state_lookup_byaddr() uses the spinlock rather than RCU.
AFAICS this is an oversight from back when state lookup was converted to
RCU, this lock should be replaced with RCU in a future patch.(CVE-2024-57982)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;eth: bnxt: always recalculate features after XDP clearing, fix n…&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;xfrm: state: fix out-of-bounds read during lookup&lt;/p&gt;
&lt;p&gt;lookup and resize can run in parallel.&lt;/p&gt;
&lt;p&gt;The xfrm_state_hash_generation seqlock ensures a retry, but the hash
functions can observe a hmask value that is too large for the new hlist
array.&lt;/p&gt;
&lt;p&gt;rehash does:
  rcu_assign_pointer(net-&amp;amp;gt;xfrm.state_bydst, ndst) [..]
  net-&amp;amp;gt;xfrm.state_hmask = nhashmask;&lt;/p&gt;
&lt;p&gt;While state lookup does:
  h = xfrm_dst_hash(net, daddr, saddr, tmpl-&amp;amp;gt;reqid, encap_family);
  hlist_for_each_entry_rcu(x, net-&amp;amp;gt;xfrm.state_bydst + h, bydst) {&lt;/p&gt;
&lt;p&gt;This is only safe in case the update to state_bydst is larger than
net-&amp;amp;gt;xfrm.xfrm_state_hmask (or if the lookup function gets
serialized via state spinlock again).&lt;/p&gt;
&lt;p&gt;Fix this by prefetching state_hmask and the associated pointers.
The xfrm_state_hash_generation seqlock retry will ensure that the pointer
and the hmask will be consistent.&lt;/p&gt;
&lt;p&gt;The existing helpers, like xfrm_dst_hash(), are now unsafe for RCU side,
add lockdep assertions to document that they are only safe for insert
side.&lt;/p&gt;
&lt;p&gt;xfrm_state_lookup_byaddr() uses the spinlock rather than RCU.
AFAICS this is an oversight from back when state lookup was converted to
RCU, this lock should be replaced with RCU in a future patch.(CVE-2024-57982)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;eth: bnxt: always recalculate features after XDP clearing, fix n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1959</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-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/opensuse-su-2025:20081-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02588-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02588-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:02588-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38181</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38181</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 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: calipso: Fix null-ptr-deref in calipso_req_{set,del}attr(). syzkaller reported a null-ptr-deref in sock_omalloc() while allocating a CALIPSO option.  [0] The NULL is of struct sock, which was fetched by sk_to_full_sk() in calipso_req_setattr(). Since commit a1a5344ddbe8 (&amp;#34;tcp: avoid two atomic ops for syncookies&amp;#34;), reqsk-&amp;gt;rsk_listener could be NULL when SYN Cookie is returned to its client, as hinted by the leading SYN Cookie log. Here are 3 options to fix the bug:   1) Return 0 in calipso_req_setattr()   2) Return an error in calipso_req_setattr()   3) Alaways set rsk_listener 1) is no go as it bypasses LSM, but 2) effectively disables SYN Cookie for CALIPSO.  3) is also no go as there have been many efforts to reduce atomic ops and make TCP robust against DDoS.  See also commit 3b24d854cb35 (&amp;#34;tcp/dccp: do not touch listener sk_refcnt under synflood&amp;#34;). As of the blamed commit, SYN Cookie already did not need refcounting, and no one has stumbled on the bug for 9 years, so no CALIPSO user will care about SYN Cookie. Let&amp;#39;s return an error in calipso_req_setattr() and calipso_req_delattr() in the SYN Cookie case. This can be reproduced by [1] on Fedora and now connect() of nc times out. [0]: TCP: request_sock_TCPv6: Possible SYN flooding on port [::]:20002. Sending cookies. Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-de…&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 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: calipso: Fix null-ptr-deref in calipso_req_{set,del}attr(). syzkaller reported a null-ptr-deref in sock_omalloc() while allocating a CALIPSO option.  [0] The NULL is of struct sock, which was fetched by sk_to_full_sk() in calipso_req_setattr(). Since commit a1a5344ddbe8 (&amp;#34;tcp: avoid two atomic ops for syncookies&amp;#34;), reqsk-&amp;gt;rsk_listener could be NULL when SYN Cookie is returned to its client, as hinted by the leading SYN Cookie log. Here are 3 options to fix the bug:   1) Return 0 in calipso_req_setattr()   2) Return an error in calipso_req_setattr()   3) Alaways set rsk_listener 1) is no go as it bypasses LSM, but 2) effectively disables SYN Cookie for CALIPSO.  3) is also no go as there have been many efforts to reduce atomic ops and make TCP robust against DDoS.  See also commit 3b24d854cb35 (&amp;#34;tcp/dccp: do not touch listener sk_refcnt under synflood&amp;#34;). As of the blamed commit, SYN Cookie already did not need refcounting, and no one has stumbled on the bug for 9 years, so no CALIPSO user will care about SYN Cookie. Let&amp;#39;s return an error in calipso_req_setattr() and calipso_req_delattr() in the SYN Cookie case. This can be reproduced by [1] on Fedora and now connect() of nc times out. [0]: TCP: request_sock_TCPv6: Possible SYN flooding on port [::]:20002. Sending cookies. Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-de…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38181</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1465 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1465</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1465</guid>
    </item>
  </channel>
</rss>
