<?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>Sat, 03 Oct 2026 13:31:52 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64067</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-64067</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-64067</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-348383</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-348383</link>
      <description>EUVD-2026-348383</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-348383</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64067</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64067</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix missing barriers when accessing stream-&amp;gt;subrequests locklessly&lt;/p&gt;
&lt;p&gt;The list of subrequests attached to stream-&amp;gt;subrequests is accessed without
locks by netfs_collect_read_results() and netfs_collect_write_results(),
and then they access subreq-&amp;gt;flags without taking a barrier after getting
the subreq pointer from the list.  Relatedly, the functions that build the
list don&amp;#39;t use any sort of write barrier when constructing the list to make
sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if
no lock is taken.&lt;/p&gt;
&lt;p&gt;Fix this by:&lt;/p&gt;
&lt;p&gt;(1) Add a new list_add_tail_release() function that uses a release barrier
     to set the pointer to the new member of the list.&lt;/p&gt;
&lt;p&gt;(2) Add a new list_first_entry_or_null_acquire() function that uses an
     acquire barrier to read the pointer to the first member in a list (or
     return NULL).&lt;/p&gt;
&lt;p&gt;(3) Use list_add_tail_release() when adding a subreq to -&amp;gt;subrequests.&lt;/p&gt;
&lt;p&gt;(4) Use list_first_entry_or_null_acquire() when initially accessing the
     front of the list (when an item is removed, the pointer to the new
     front iterm is obtained under the same lock).&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 missing barriers when accessing stream-&amp;gt;subrequests locklessly&lt;/p&gt;
&lt;p&gt;The list of subrequests attached to stream-&amp;gt;subrequests is accessed without
locks by netfs_collect_read_results() and netfs_collect_write_results(),
and then they access subreq-&amp;gt;flags without taking a barrier after getting
the subreq pointer from the list.  Relatedly, the functions that build the
list don&amp;#39;t use any sort of write barrier when constructing the list to make
sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if
no lock is taken.&lt;/p&gt;
&lt;p&gt;Fix this by:&lt;/p&gt;
&lt;p&gt;(1) Add a new list_add_tail_release() function that uses a release barrier
     to set the pointer to the new member of the list.&lt;/p&gt;
&lt;p&gt;(2) Add a new list_first_entry_or_null_acquire() function that uses an
     acquire barrier to read the pointer to the first member in a list (or
     return NULL).&lt;/p&gt;
&lt;p&gt;(3) Use list_add_tail_release() when adding a subreq to -&amp;gt;subrequests.&lt;/p&gt;
&lt;p&gt;(4) Use list_first_entry_or_null_acquire() when initially accessing the
     front of the list (when an item is removed, the pointer to the new
     front iterm is obtained under the same lock).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64067</guid>
    </item>
    <item>
      <title>GHSA-f3mp-m5hm-h688</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f3mp-m5hm-h688</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix missing barriers when accessing stream-&amp;gt;subrequests locklessly&lt;/p&gt;
&lt;p&gt;The list of subrequests attached to stream-&amp;gt;subrequests is accessed without
locks by netfs_collect_read_results() and netfs_collect_write_results(),
and then they access subreq-&amp;gt;flags without taking a barrier after getting
the subreq pointer from the list.  Relatedly, the functions that build the
list don&amp;#39;t use any sort of write barrier when constructing the list to make
sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if
no lock is taken.&lt;/p&gt;
&lt;p&gt;Fix this by:&lt;/p&gt;
&lt;p&gt;(1) Add a new list_add_tail_release() function that uses a release barrier
     to set the pointer to the new member of the list.&lt;/p&gt;
&lt;p&gt;(2) Add a new list_first_entry_or_null_acquire() function that uses an
     acquire barrier to read the pointer to the first member in a list (or
     return NULL).&lt;/p&gt;
&lt;p&gt;(3) Use list_add_tail_release() when adding a subreq to -&amp;gt;subrequests.&lt;/p&gt;
&lt;p&gt;(4) Use list_first_entry_or_null_acquire() when initially accessing the
     front of the list (when an item is removed, the pointer to the new
     front iterm is obtained under the same lock).&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 missing barriers when accessing stream-&amp;gt;subrequests locklessly&lt;/p&gt;
&lt;p&gt;The list of subrequests attached to stream-&amp;gt;subrequests is accessed without
locks by netfs_collect_read_results() and netfs_collect_write_results(),
and then they access subreq-&amp;gt;flags without taking a barrier after getting
the subreq pointer from the list.  Relatedly, the functions that build the
list don&amp;#39;t use any sort of write barrier when constructing the list to make
sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if
no lock is taken.&lt;/p&gt;
&lt;p&gt;Fix this by:&lt;/p&gt;
&lt;p&gt;(1) Add a new list_add_tail_release() function that uses a release barrier
     to set the pointer to the new member of the list.&lt;/p&gt;
&lt;p&gt;(2) Add a new list_first_entry_or_null_acquire() function that uses an
     acquire barrier to read the pointer to the first member in a list (or
     return NULL).&lt;/p&gt;
&lt;p&gt;(3) Use list_add_tail_release() when adding a subreq to -&amp;gt;subrequests.&lt;/p&gt;
&lt;p&gt;(4) Use list_first_entry_or_null_acquire() when initially accessing the
     front of the list (when an item is removed, the pointer to the new
     front iterm is obtained under the same lock).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f3mp-m5hm-h688</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64067</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64067</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 missing barriers when accessing stream-&amp;gt;subrequests locklessly The list of subrequests attached to stream-&amp;gt;subrequests is accessed without locks by netfs_collect_read_results() and netfs_collect_write_results(), and then they access subreq-&amp;gt;flags without taking a barrier after getting the subreq pointer from the list.  Relatedly, the functions that build the list don&amp;#39;t use any sort of write barrier when constructing the list to make sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if no lock is taken. Fix this by:  (1) Add a new list_add_tail_release() function that uses a release barrier      to set the pointer to the new member of the list.  (2) Add a new list_first_entry_or_null_acquire() function that uses an      acquire barrier to read the pointer to the first member in a list (or      return NULL).  (3) Use list_add_tail_release() when adding a subreq to -&amp;gt;subrequests.  (4) Use list_first_entry_or_null_acquire() when initially accessing the      front of the list (when an item is removed, the pointer to the new      front iterm is obtained under the same lock).&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 missing barriers when accessing stream-&amp;gt;subrequests locklessly The list of subrequests attached to stream-&amp;gt;subrequests is accessed without locks by netfs_collect_read_results() and netfs_collect_write_results(), and then they access subreq-&amp;gt;flags without taking a barrier after getting the subreq pointer from the list.  Relatedly, the functions that build the list don&amp;#39;t use any sort of write barrier when constructing the list to make sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if no lock is taken. Fix this by:  (1) Add a new list_add_tail_release() function that uses a release barrier      to set the pointer to the new member of the list.  (2) Add a new list_first_entry_or_null_acquire() function that uses an      acquire barrier to read the pointer to the first member in a list (or      return NULL).  (3) Use list_add_tail_release() when adding a subreq to -&amp;gt;subrequests.  (4) Use list_first_entry_or_null_acquire() when initially accessing the      front of the list (when an item is removed, the pointer to the new      front iterm is obtained under the same lock).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64067</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>
