<?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, 02 Oct 2026 16:30:00 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64069</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-64069</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-64069</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — 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-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-348384</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-348384</link>
      <description>EUVD-2026-348384</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-348384</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64069</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64069</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix cancellation of a DIO and single read subrequests&lt;/p&gt;
&lt;p&gt;When the preparation of a new subrequest for a read fails, if the
subrequest has already been added to the stream-&amp;gt;subrequests list, it can&amp;#39;t
simply be put and abandoned as the collector may see it.  Also, if it
hasn&amp;#39;t been queued yet, it has two outstanding refs that both need to be
put.  Both DIO read and single-read dispatch fail at this; further, both
differ in the order they do things to the way buffered read works.&lt;/p&gt;
&lt;p&gt;Fix cancellation of both DIO-read and single-read subrequests that failed
preparation by the following steps:&lt;/p&gt;
&lt;p&gt;(1) Harmonise all three reads (buffered, dio, single) to queue the subreq
     before prepping it.&lt;/p&gt;
&lt;p&gt;(2) Make all three call netfs_queue_read() to do the queuing.&lt;/p&gt;
&lt;p&gt;(3) Set NETFS_RREQ_ALL_QUEUED independently of the queuing as we don&amp;#39;t
     know the length of the subreq at this point.&lt;/p&gt;
&lt;p&gt;(4) In all cases, set the error and NETFS_SREQ_FAILED flag on the subreq
     and then call netfs_read_subreq_terminated() to deal with it.  This
     will pass responsibility off to the collector for dealing with it.&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 cancellation of a DIO and single read subrequests&lt;/p&gt;
&lt;p&gt;When the preparation of a new subrequest for a read fails, if the
subrequest has already been added to the stream-&amp;gt;subrequests list, it can&amp;#39;t
simply be put and abandoned as the collector may see it.  Also, if it
hasn&amp;#39;t been queued yet, it has two outstanding refs that both need to be
put.  Both DIO read and single-read dispatch fail at this; further, both
differ in the order they do things to the way buffered read works.&lt;/p&gt;
&lt;p&gt;Fix cancellation of both DIO-read and single-read subrequests that failed
preparation by the following steps:&lt;/p&gt;
&lt;p&gt;(1) Harmonise all three reads (buffered, dio, single) to queue the subreq
     before prepping it.&lt;/p&gt;
&lt;p&gt;(2) Make all three call netfs_queue_read() to do the queuing.&lt;/p&gt;
&lt;p&gt;(3) Set NETFS_RREQ_ALL_QUEUED independently of the queuing as we don&amp;#39;t
     know the length of the subreq at this point.&lt;/p&gt;
&lt;p&gt;(4) In all cases, set the error and NETFS_SREQ_FAILED flag on the subreq
     and then call netfs_read_subreq_terminated() to deal with it.  This
     will pass responsibility off to the collector for dealing with it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64069</guid>
    </item>
    <item>
      <title>GHSA-95rq-8wg2-8c57</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-95rq-8wg2-8c57</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix cancellation of a DIO and single read subrequests&lt;/p&gt;
&lt;p&gt;When the preparation of a new subrequest for a read fails, if the
subrequest has already been added to the stream-&amp;gt;subrequests list, it can&amp;#39;t
simply be put and abandoned as the collector may see it.  Also, if it
hasn&amp;#39;t been queued yet, it has two outstanding refs that both need to be
put.  Both DIO read and single-read dispatch fail at this; further, both
differ in the order they do things to the way buffered read works.&lt;/p&gt;
&lt;p&gt;Fix cancellation of both DIO-read and single-read subrequests that failed
preparation by the following steps:&lt;/p&gt;
&lt;p&gt;(1) Harmonise all three reads (buffered, dio, single) to queue the subreq
     before prepping it.&lt;/p&gt;
&lt;p&gt;(2) Make all three call netfs_queue_read() to do the queuing.&lt;/p&gt;
&lt;p&gt;(3) Set NETFS_RREQ_ALL_QUEUED independently of the queuing as we don&amp;#39;t
     know the length of the subreq at this point.&lt;/p&gt;
&lt;p&gt;(4) In all cases, set the error and NETFS_SREQ_FAILED flag on the subreq
     and then call netfs_read_subreq_terminated() to deal with it.  This
     will pass responsibility off to the collector for dealing with it.&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 cancellation of a DIO and single read subrequests&lt;/p&gt;
&lt;p&gt;When the preparation of a new subrequest for a read fails, if the
subrequest has already been added to the stream-&amp;gt;subrequests list, it can&amp;#39;t
simply be put and abandoned as the collector may see it.  Also, if it
hasn&amp;#39;t been queued yet, it has two outstanding refs that both need to be
put.  Both DIO read and single-read dispatch fail at this; further, both
differ in the order they do things to the way buffered read works.&lt;/p&gt;
&lt;p&gt;Fix cancellation of both DIO-read and single-read subrequests that failed
preparation by the following steps:&lt;/p&gt;
&lt;p&gt;(1) Harmonise all three reads (buffered, dio, single) to queue the subreq
     before prepping it.&lt;/p&gt;
&lt;p&gt;(2) Make all three call netfs_queue_read() to do the queuing.&lt;/p&gt;
&lt;p&gt;(3) Set NETFS_RREQ_ALL_QUEUED independently of the queuing as we don&amp;#39;t
     know the length of the subreq at this point.&lt;/p&gt;
&lt;p&gt;(4) In all cases, set the error and NETFS_SREQ_FAILED flag on the subreq
     and then call netfs_read_subreq_terminated() to deal with it.  This
     will pass responsibility off to the collector for dealing with it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-95rq-8wg2-8c57</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64069</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64069</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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix cancellation of a DIO and single read subrequests When the preparation of a new subrequest for a read fails, if the subrequest has already been added to the stream-&amp;gt;subrequests list, it can&amp;#39;t simply be put and abandoned as the collector may see it.  Also, if it hasn&amp;#39;t been queued yet, it has two outstanding refs that both need to be put.  Both DIO read and single-read dispatch fail at this; further, both differ in the order they do things to the way buffered read works. Fix cancellation of both DIO-read and single-read subrequests that failed preparation by the following steps:  (1) Harmonise all three reads (buffered, dio, single) to queue the subreq      before prepping it.  (2) Make all three call netfs_queue_read() to do the queuing.  (3) Set NETFS_RREQ_ALL_QUEUED independently of the queuing as we don&amp;#39;t      know the length of the subreq at this point.  (4) In all cases, set the error and NETFS_SREQ_FAILED flag on the subreq      and then call netfs_read_subreq_terminated() to deal with it.  This      will pass responsibility off to the collector for dealing with it.&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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix cancellation of a DIO and single read subrequests When the preparation of a new subrequest for a read fails, if the subrequest has already been added to the stream-&amp;gt;subrequests list, it can&amp;#39;t simply be put and abandoned as the collector may see it.  Also, if it hasn&amp;#39;t been queued yet, it has two outstanding refs that both need to be put.  Both DIO read and single-read dispatch fail at this; further, both differ in the order they do things to the way buffered read works. Fix cancellation of both DIO-read and single-read subrequests that failed preparation by the following steps:  (1) Harmonise all three reads (buffered, dio, single) to queue the subreq      before prepping it.  (2) Make all three call netfs_queue_read() to do the queuing.  (3) Set NETFS_RREQ_ALL_QUEUED independently of the queuing as we don&amp;#39;t      know the length of the subreq at this point.  (4) In all cases, set the error and NETFS_SREQ_FAILED flag on the subreq      and then call netfs_read_subreq_terminated() to deal with it.  This      will pass responsibility off to the collector for dealing with it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64069</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
