<?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>Wed, 07 Oct 2026 19:29:49 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-09126</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-09126</link>
      <description>bdu:2025-09126</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-09126</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2025-38411 — CVE-2025-38411 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38411</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-38411</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0922 — 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-0922</link>
      <description>certfr-2025-avi-0922</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0922</guid>
    </item>
    <item>
      <title>EUVD-2026-347031</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347031</link>
      <description>EUVD-2026-347031</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347031</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38411</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38411</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix double put of request&lt;/p&gt;
&lt;p&gt;If a netfs request finishes during the pause loop, it will have the ref
that belongs to the IN_PROGRESS flag removed at that point - however, if it
then goes to the final wait loop, that will *also* put the ref because it
sees that the IN_PROGRESS flag is clear and incorrectly assumes that this
happened when it called the collector.&lt;/p&gt;
&lt;p&gt;In fact, since IN_PROGRESS is clear, we shouldn&amp;#39;t call the collector again
since it&amp;#39;s done all the cleanup, such as calling -&amp;gt;ki_complete().&lt;/p&gt;
&lt;p&gt;Fix this by making netfs_collect_in_app() just return, indicating that
we&amp;#39;re done if IN_PROGRESS is removed.&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;netfs: Fix double put of request&lt;/p&gt;
&lt;p&gt;If a netfs request finishes during the pause loop, it will have the ref
that belongs to the IN_PROGRESS flag removed at that point - however, if it
then goes to the final wait loop, that will *also* put the ref because it
sees that the IN_PROGRESS flag is clear and incorrectly assumes that this
happened when it called the collector.&lt;/p&gt;
&lt;p&gt;In fact, since IN_PROGRESS is clear, we shouldn&amp;#39;t call the collector again
since it&amp;#39;s done all the cleanup, such as calling -&amp;gt;ki_complete().&lt;/p&gt;
&lt;p&gt;Fix this by making netfs_collect_in_app() just return, indicating that
we&amp;#39;re done if IN_PROGRESS is removed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38411</guid>
    </item>
    <item>
      <title>GHSA-c3c4-j5v2-q687</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c3c4-j5v2-q687</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix double put of request&lt;/p&gt;
&lt;p&gt;If a netfs request finishes during the pause loop, it will have the ref
that belongs to the IN_PROGRESS flag removed at that point - however, if it
then goes to the final wait loop, that will *also* put the ref because it
sees that the IN_PROGRESS flag is clear and incorrectly assumes that this
happened when it called the collector.&lt;/p&gt;
&lt;p&gt;In fact, since IN_PROGRESS is clear, we shouldn&amp;#39;t call the collector again
since it&amp;#39;s done all the cleanup, such as calling -&amp;gt;ki_complete().&lt;/p&gt;
&lt;p&gt;Fix this by making netfs_collect_in_app() just return, indicating that
we&amp;#39;re done if IN_PROGRESS is removed.&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;netfs: Fix double put of request&lt;/p&gt;
&lt;p&gt;If a netfs request finishes during the pause loop, it will have the ref
that belongs to the IN_PROGRESS flag removed at that point - however, if it
then goes to the final wait loop, that will *also* put the ref because it
sees that the IN_PROGRESS flag is clear and incorrectly assumes that this
happened when it called the collector.&lt;/p&gt;
&lt;p&gt;In fact, since IN_PROGRESS is clear, we shouldn&amp;#39;t call the collector again
since it&amp;#39;s done all the cleanup, such as calling -&amp;gt;ki_complete().&lt;/p&gt;
&lt;p&gt;Fix this by making netfs_collect_in_app() just return, indicating that
we&amp;#39;re done if IN_PROGRESS is removed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c3c4-j5v2-q687</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38411 — netfs: Fix double put of request</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38411</link>
      <description>msrc_CVE-2025-38411</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38411</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38411</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38411</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 82 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix double put of request If a netfs request finishes during the pause loop, it will have the ref that belongs to the IN_PROGRESS flag removed at that point - however, if it then goes to the final wait loop, that will *also* put the ref because it sees that the IN_PROGRESS flag is clear and incorrectly assumes that this happened when it called the collector. In fact, since IN_PROGRESS is clear, we shouldn&amp;#39;t call the collector again since it&amp;#39;s done all the cleanup, such as calling -&amp;gt;ki_complete(). Fix this by making netfs_collect_in_app() just return, indicating that we&amp;#39;re done if IN_PROGRESS is removed.&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 82 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix double put of request If a netfs request finishes during the pause loop, it will have the ref that belongs to the IN_PROGRESS flag removed at that point - however, if it then goes to the final wait loop, that will *also* put the ref because it sees that the IN_PROGRESS flag is clear and incorrectly assumes that this happened when it called the collector. In fact, since IN_PROGRESS is clear, we shouldn&amp;#39;t call the collector again since it&amp;#39;s done all the cleanup, such as calling -&amp;gt;ki_complete(). Fix this by making netfs_collect_in_app() just return, indicating that we&amp;#39;re done if IN_PROGRESS is removed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38411</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1653 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1653</link>
      <description>&lt;p&gt;Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1653</guid>
    </item>
  </channel>
</rss>
