<?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 15:27:17 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64031</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-64031</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-64031</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-367497</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367497</link>
      <description>EUVD-2026-367497</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367497</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64031</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64031</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;erofs: fix managed cache race for unaligned extents&lt;/p&gt;
&lt;p&gt;After unaligned compressed extents were introduced, the following race
could occur:&lt;/p&gt;
&lt;p&gt;[Thread 1]                                   [Thread 2]
(z_erofs_fill_bio_vec)
&amp;lt;handle a Z_EROFS_PREALLOCATED_FOLIO folio&amp;gt;
...
filemap_add_folio (1)
                                             (z_erofs_bind_cache)
                                             &amp;lt;the same folio is found..&amp;gt;
                                             ..
                                             ..
folio_attach_private (2)
                                             filemap_add_folio (3) again&lt;/p&gt;
&lt;p&gt;Since (1) is executed but (2) hasn&amp;#39;t been executed yet, it&amp;#39;s possible
that another thread finds the same managed folio in z_erofs_bind_cache()
for a different pcluster and calls filemap_add_folio() again since
folio-&amp;gt;private is still Z_EROFS_PREALLOCATED_FOLIO.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly clearing folio-&amp;gt;private before making the folio
visible in the managed cache so that another pcluster can simply wait
on the locked managed folio as what we did for other shared cases [1].&lt;/p&gt;
&lt;p&gt;This only impacts unaligned data compression (`-E48bit` with zstd,
for example).&lt;/p&gt;
&lt;p&gt;[1] Commit 9e2f9d34dd12 (&amp;#34;erofs: handle overlapped pclusters out of
 crafted images properly&amp;#34;) was originally introduced to handle crafted
 overlapped extents, but it addresses unaligned extents as well.&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;erofs: fix managed cache race for unaligned extents&lt;/p&gt;
&lt;p&gt;After unaligned compressed extents were introduced, the following race
could occur:&lt;/p&gt;
&lt;p&gt;[Thread 1]                                   [Thread 2]
(z_erofs_fill_bio_vec)
&amp;lt;handle a Z_EROFS_PREALLOCATED_FOLIO folio&amp;gt;
...
filemap_add_folio (1)
                                             (z_erofs_bind_cache)
                                             &amp;lt;the same folio is found..&amp;gt;
                                             ..
                                             ..
folio_attach_private (2)
                                             filemap_add_folio (3) again&lt;/p&gt;
&lt;p&gt;Since (1) is executed but (2) hasn&amp;#39;t been executed yet, it&amp;#39;s possible
that another thread finds the same managed folio in z_erofs_bind_cache()
for a different pcluster and calls filemap_add_folio() again since
folio-&amp;gt;private is still Z_EROFS_PREALLOCATED_FOLIO.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly clearing folio-&amp;gt;private before making the folio
visible in the managed cache so that another pcluster can simply wait
on the locked managed folio as what we did for other shared cases [1].&lt;/p&gt;
&lt;p&gt;This only impacts unaligned data compression (`-E48bit` with zstd,
for example).&lt;/p&gt;
&lt;p&gt;[1] Commit 9e2f9d34dd12 (&amp;#34;erofs: handle overlapped pclusters out of
 crafted images properly&amp;#34;) was originally introduced to handle crafted
 overlapped extents, but it addresses unaligned extents as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64031</guid>
    </item>
    <item>
      <title>GHSA-22cv-hg25-xph5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-22cv-hg25-xph5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;erofs: fix managed cache race for unaligned extents&lt;/p&gt;
&lt;p&gt;After unaligned compressed extents were introduced, the following race
could occur:&lt;/p&gt;
&lt;p&gt;[Thread 1]                                   [Thread 2]
(z_erofs_fill_bio_vec)
&amp;lt;handle a Z_EROFS_PREALLOCATED_FOLIO folio&amp;gt;
...
filemap_add_folio (1)
                                             (z_erofs_bind_cache)
                                             &amp;lt;the same folio is found..&amp;gt;
                                             ..
                                             ..
folio_attach_private (2)
                                             filemap_add_folio (3) again&lt;/p&gt;
&lt;p&gt;Since (1) is executed but (2) hasn&amp;#39;t been executed yet, it&amp;#39;s possible
that another thread finds the same managed folio in z_erofs_bind_cache()
for a different pcluster and calls filemap_add_folio() again since
folio-&amp;gt;private is still Z_EROFS_PREALLOCATED_FOLIO.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly clearing folio-&amp;gt;private before making the folio
visible in the managed cache so that another pcluster can simply wait
on the locked managed folio as what we did for other shared cases [1].&lt;/p&gt;
&lt;p&gt;This only impacts unaligned data compression (`-E48bit` with zstd,
for example).&lt;/p&gt;
&lt;p&gt;[1] Commit 9e2f9d34dd12 (&amp;#34;erofs: handle overlapped pclusters out of
 crafted images properly&amp;#34;) was originally introduced to handle crafted
 overlapped extents, but it addresses unaligned extents as well.&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;erofs: fix managed cache race for unaligned extents&lt;/p&gt;
&lt;p&gt;After unaligned compressed extents were introduced, the following race
could occur:&lt;/p&gt;
&lt;p&gt;[Thread 1]                                   [Thread 2]
(z_erofs_fill_bio_vec)
&amp;lt;handle a Z_EROFS_PREALLOCATED_FOLIO folio&amp;gt;
...
filemap_add_folio (1)
                                             (z_erofs_bind_cache)
                                             &amp;lt;the same folio is found..&amp;gt;
                                             ..
                                             ..
folio_attach_private (2)
                                             filemap_add_folio (3) again&lt;/p&gt;
&lt;p&gt;Since (1) is executed but (2) hasn&amp;#39;t been executed yet, it&amp;#39;s possible
that another thread finds the same managed folio in z_erofs_bind_cache()
for a different pcluster and calls filemap_add_folio() again since
folio-&amp;gt;private is still Z_EROFS_PREALLOCATED_FOLIO.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly clearing folio-&amp;gt;private before making the folio
visible in the managed cache so that another pcluster can simply wait
on the locked managed folio as what we did for other shared cases [1].&lt;/p&gt;
&lt;p&gt;This only impacts unaligned data compression (`-E48bit` with zstd,
for example).&lt;/p&gt;
&lt;p&gt;[1] Commit 9e2f9d34dd12 (&amp;#34;erofs: handle overlapped pclusters out of
 crafted images properly&amp;#34;) was originally introduced to handle crafted
 overlapped extents, but it addresses unaligned extents as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-22cv-hg25-xph5</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64031</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64031</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: erofs: fix managed cache race for unaligned extents After unaligned compressed extents were introduced, the following race could occur: [Thread 1]                                   [Thread 2] (z_erofs_fill_bio_vec) &amp;lt;handle a Z_EROFS_PREALLOCATED_FOLIO folio&amp;gt; ... filemap_add_folio (1)                                              (z_erofs_bind_cache)                                              &amp;lt;the same folio is found..&amp;gt;                                              ..                                              .. folio_attach_private (2)                                              filemap_add_folio (3) again Since (1) is executed but (2) hasn&amp;#39;t been executed yet, it&amp;#39;s possible that another thread finds the same managed folio in z_erofs_bind_cache() for a different pcluster and calls filemap_add_folio() again since folio-&amp;gt;private is still Z_EROFS_PREALLOCATED_FOLIO. Fix this by explicitly clearing folio-&amp;gt;private before making the folio visible in the managed cache so that another pcluster can simply wait on the locked managed folio as what we did for other shared cases [1]. This only impacts unaligned data compression (`-E48bit` with zstd, for example). [1] Commit 9e2f9d34dd12 (&amp;#34;erofs: handle overlapped pclusters out of  crafted images properly&amp;#34;) was originally introduced to handle crafted  overlapped extents, but it addresses unaligned extents as well.&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: erofs: fix managed cache race for unaligned extents After unaligned compressed extents were introduced, the following race could occur: [Thread 1]                                   [Thread 2] (z_erofs_fill_bio_vec) &amp;lt;handle a Z_EROFS_PREALLOCATED_FOLIO folio&amp;gt; ... filemap_add_folio (1)                                              (z_erofs_bind_cache)                                              &amp;lt;the same folio is found..&amp;gt;                                              ..                                              .. folio_attach_private (2)                                              filemap_add_folio (3) again Since (1) is executed but (2) hasn&amp;#39;t been executed yet, it&amp;#39;s possible that another thread finds the same managed folio in z_erofs_bind_cache() for a different pcluster and calls filemap_add_folio() again since folio-&amp;gt;private is still Z_EROFS_PREALLOCATED_FOLIO. Fix this by explicitly clearing folio-&amp;gt;private before making the folio visible in the managed cache so that another pcluster can simply wait on the locked managed folio as what we did for other shared cases [1]. This only impacts unaligned data compression (`-E48bit` with zstd, for example). [1] Commit 9e2f9d34dd12 (&amp;#34;erofs: handle overlapped pclusters out of  crafted images properly&amp;#34;) was originally introduced to handle crafted  overlapped extents, but it addresses unaligned extents as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64031</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>
