<?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>Fri, 09 Oct 2026 18:45:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-213461</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-213461</link>
      <description>EUVD-2026-213461</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-213461</guid>
    </item>
    <item>
      <title>fkie_cve-2023-24820</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-24820</link>
      <description>&lt;p&gt;RIOT-OS, an operating system that supports Internet of Things devices, contains a network stack with the ability to process 6LoWPAN frames. An attacker can send a crafted frame to the device resulting in a large out of bounds write beyond the packet buffer. The write will create a hard fault exception after reaching the last page of RAM. The hard fault is not handled and the system will be stuck until reset. Thus the impact is denial of service. Version 2022.10 fixes this issue. As a workaround, apply the patch manually.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;RIOT-OS, an operating system that supports Internet of Things devices, contains a network stack with the ability to process 6LoWPAN frames. An attacker can send a crafted frame to the device resulting in a large out of bounds write beyond the packet buffer. The write will create a hard fault exception after reaching the last page of RAM. The hard fault is not handled and the system will be stuck until reset. Thus the impact is denial of service. Version 2022.10 fixes this issue. As a workaround, apply the patch manually.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-24820</guid>
    </item>
    <item>
      <title>gsd-2023-24820</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-24820</link>
      <description>gsd-2023-24820</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-24820</guid>
    </item>
  </channel>
</rss>
