<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T12:49:54.433195+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2025-71230</id>
    <title>BELL-CVE-2025-71230</title>
    <updated>2026-10-05T12:49:54.441346+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2025-71230"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0215</id>
    <title>certfr-2026-avi-0215 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
    <updated>2026-10-05T12:49:54.441436+00:00</updated>
    <content>certfr-2026-avi-0215</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0215"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-315246</id>
    <title>EUVD-2026-315246</title>
    <updated>2026-10-05T12:49:54.441458+00:00</updated>
    <content>EUVD-2026-315246</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-315246"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-71230</id>
    <title>fkie_cve-2025-71230</title>
    <updated>2026-10-05T12:49:54.441471+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>hfs: ensure sb-&gt;s_fs_info is always cleaned up</p>
<p>When hfs was converted to the new mount api a bug was introduced by
changing the allocation pattern of sb-&gt;s_fs_info. If setup_bdev_super()
fails after a new superblock has been allocated by sget_fc(), but before
hfs_fill_super() takes ownership of the filesystem-specific s_fs_info
data it was leaked.</p>
<p>Fix this by freeing sb-&gt;s_fs_info in hfs_kill_super().</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-71230"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6xrx-3vj8-2rjc</id>
    <title>GHSA-6xrx-3vj8-2rjc</title>
    <updated>2026-10-05T12:49:54.441502+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>hfs: ensure sb-&gt;s_fs_info is always cleaned up</p>
<p>When hfs was converted to the new mount api a bug was introduced by
changing the allocation pattern of sb-&gt;s_fs_info. If setup_bdev_super()
fails after a new superblock has been allocated by sget_fc(), but before
hfs_fill_super() takes ownership of the filesystem-specific s_fs_info
data it was leaked.</p>
<p>Fix this by freeing sb-&gt;s_fs_info in hfs_kill_super().</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6xrx-3vj8-2rjc"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2025-71230</id>
    <title>msrc_CVE-2025-71230 — hfs: ensure sb-&gt;s_fs_info is always cleaned up</title>
    <updated>2026-10-05T12:49:54.441522+00:00</updated>
    <content>msrc_CVE-2025-71230</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2025-71230"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10387-1</id>
    <title>openSUSE-SU-2026:10387-1 — kernel-devel-6.19.8-1.1 on GA media</title>
    <updated>2026-10-05T12:49:54.441538+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel-devel-6.19.8-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:10387-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71230</id>
    <title>UBUNTU-CVE-2025-71230</title>
    <updated>2026-10-05T12:49:54.441563+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 106 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: hfs: ensure sb-&gt;s_fs_info is always cleaned up When hfs was converted to the new mount api a bug was introduced by changing the allocation pattern of sb-&gt;s_fs_info. If setup_bdev_super() fails after a new superblock has been allocated by sget_fc(), but before hfs_fill_super() takes ownership of the filesystem-specific s_fs_info data it was leaked. Fix this by freeing sb-&gt;s_fs_info in hfs_kill_super().</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71230"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0462</id>
    <title>WID-SEC-W-2026-0462 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-05T12:49:54.441701+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0462"/>
  </entry>
</feed>
