<?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>Tue, 06 Oct 2026 22:55:46 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-264336</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-264336</link>
      <description>EUVD-2026-264336</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-264336</guid>
    </item>
    <item>
      <title>fkie_cve-2025-68617</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68617</link>
      <description>&lt;p&gt;FluidSynth is a software synthesizer based on the SoundFont 2 specifications. From versions 2.5.0 to before 2.5.2, a race condition during unloading of a DLS file can trigger a heap-based use-after-free. A concurrently running thread may be pending to unload a DLS file, leading to use of freed memory, if the synthesizer is being concurrently destroyed, or samples of the (unloaded) DLS file are concurrently used to synthesize audio. This issue has been patched in version 2.5.2. The problem will not occur, when explicitly unloading a DLS file (before synth destruction), provided that at the time of unloading, no samples of the respective file are used by active voices. The problem will not occur in versions of FluidSynth that have been compiled without native DLS support.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;FluidSynth is a software synthesizer based on the SoundFont 2 specifications. From versions 2.5.0 to before 2.5.2, a race condition during unloading of a DLS file can trigger a heap-based use-after-free. A concurrently running thread may be pending to unload a DLS file, leading to use of freed memory, if the synthesizer is being concurrently destroyed, or samples of the (unloaded) DLS file are concurrently used to synthesize audio. This issue has been patched in version 2.5.2. The problem will not occur, when explicitly unloading a DLS file (before synth destruction), provided that at the time of unloading, no samples of the respective file are used by active voices. The problem will not occur in versions of FluidSynth that have been compiled without native DLS support.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-68617</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10004-1 — fluidsynth-2.5.2-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10004-1</link>
      <description>&lt;p&gt;fluidsynth-2.5.2-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;fluidsynth-2.5.2-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10004-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-68617</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68617</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: fluidsynth, Ubuntu:16.04:LTS: fluidsynth, Ubuntu:18.04:LTS: fluidsynth, Ubuntu:20.04:LTS: fluidsynth, Ubuntu:22.04:LTS: fluidsynth, Ubuntu:24.04:LTS: fluidsynth, Ubuntu:25.10: fluidsynth, Ubuntu:26.04:LTS: fluidsynth&lt;/p&gt;
&lt;p&gt;FluidSynth is a software synthesizer based on the SoundFont 2 specifications. From versions 2.5.0 to before 2.5.2, a race condition during unloading of a DLS file can trigger a heap-based use-after-free. A concurrently running thread may be pending to unload a DLS file, leading to use of freed memory, if the synthesizer is being concurrently destroyed, or samples of the (unloaded) DLS file are concurrently used to synthesize audio. This issue has been patched in version 2.5.2. The problem will not occur, when explicitly unloading a DLS file (before synth destruction), provided that at the time of unloading, no samples of the respective file are used by active voices. The problem will not occur in versions of FluidSynth that have been compiled without native DLS support.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: fluidsynth, Ubuntu:16.04:LTS: fluidsynth, Ubuntu:18.04:LTS: fluidsynth, Ubuntu:20.04:LTS: fluidsynth, Ubuntu:22.04:LTS: fluidsynth, Ubuntu:24.04:LTS: fluidsynth, Ubuntu:25.10: fluidsynth, Ubuntu:26.04:LTS: fluidsynth&lt;/p&gt;
&lt;p&gt;FluidSynth is a software synthesizer based on the SoundFont 2 specifications. From versions 2.5.0 to before 2.5.2, a race condition during unloading of a DLS file can trigger a heap-based use-after-free. A concurrently running thread may be pending to unload a DLS file, leading to use of freed memory, if the synthesizer is being concurrently destroyed, or samples of the (unloaded) DLS file are concurrently used to synthesize audio. This issue has been patched in version 2.5.2. The problem will not occur, when explicitly unloading a DLS file (before synth destruction), provided that at the time of unloading, no samples of the respective file are used by active voices. The problem will not occur in versions of FluidSynth that have been compiled without native DLS support.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68617</guid>
    </item>
  </channel>
</rss>
