<?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 19:28:40 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74590</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74590</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-74590</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1090 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090</link>
      <description>certfr-2026-avi-1090</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090</guid>
    </item>
    <item>
      <title>EUVD-2026-358498</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-358498</link>
      <description>EUVD-2026-358498</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-358498</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74590</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74590</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fsverity: Fix bpf_get_fsverity_digest() dynptr assumptions&lt;/p&gt;
&lt;p&gt;The BPF verifier and the dynptr abstraction ensure that the memory space
referenced by a dynptr remains valid.  They do not, however, provide any
guarantee that the contents of the memory are stable.  kfuncs are
expected to remain memory-safe even if concurrent modifications occur.&lt;/p&gt;
&lt;p&gt;bpf_get_fsverity_digest() didn&amp;#39;t follow that: it could crash if
arg-&amp;gt;digest_size was concurrently modified.&lt;/p&gt;
&lt;p&gt;Fix that by using the known-good value hash_alg-&amp;gt;digest_size instead.&lt;/p&gt;
&lt;p&gt;Also widen &amp;#39;dynptr_sz&amp;#39; and &amp;#39;out_digest_sz&amp;#39; to u64 to match the return
type of __bpf_dynptr_size().  It doesn&amp;#39;t appear that it can actually be
more than INT_MAX currently (since __bpf_dynptr_data_rw() excludes
file-based pointers), but the correct type might as well be used.&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;fsverity: Fix bpf_get_fsverity_digest() dynptr assumptions&lt;/p&gt;
&lt;p&gt;The BPF verifier and the dynptr abstraction ensure that the memory space
referenced by a dynptr remains valid.  They do not, however, provide any
guarantee that the contents of the memory are stable.  kfuncs are
expected to remain memory-safe even if concurrent modifications occur.&lt;/p&gt;
&lt;p&gt;bpf_get_fsverity_digest() didn&amp;#39;t follow that: it could crash if
arg-&amp;gt;digest_size was concurrently modified.&lt;/p&gt;
&lt;p&gt;Fix that by using the known-good value hash_alg-&amp;gt;digest_size instead.&lt;/p&gt;
&lt;p&gt;Also widen &amp;#39;dynptr_sz&amp;#39; and &amp;#39;out_digest_sz&amp;#39; to u64 to match the return
type of __bpf_dynptr_size().  It doesn&amp;#39;t appear that it can actually be
more than INT_MAX currently (since __bpf_dynptr_data_rw() excludes
file-based pointers), but the correct type might as well be used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74590</guid>
    </item>
    <item>
      <title>GHSA-pxx7-9r2r-m5m2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pxx7-9r2r-m5m2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fsverity: Fix bpf_get_fsverity_digest() dynptr assumptions&lt;/p&gt;
&lt;p&gt;The BPF verifier and the dynptr abstraction ensure that the memory space
referenced by a dynptr remains valid.  They do not, however, provide any
guarantee that the contents of the memory are stable.  kfuncs are
expected to remain memory-safe even if concurrent modifications occur.&lt;/p&gt;
&lt;p&gt;bpf_get_fsverity_digest() didn&amp;#39;t follow that: it could crash if
arg-&amp;gt;digest_size was concurrently modified.&lt;/p&gt;
&lt;p&gt;Fix that by using the known-good value hash_alg-&amp;gt;digest_size instead.&lt;/p&gt;
&lt;p&gt;Also widen &amp;#39;dynptr_sz&amp;#39; and &amp;#39;out_digest_sz&amp;#39; to u64 to match the return
type of __bpf_dynptr_size().  It doesn&amp;#39;t appear that it can actually be
more than INT_MAX currently (since __bpf_dynptr_data_rw() excludes
file-based pointers), but the correct type might as well be used.&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;fsverity: Fix bpf_get_fsverity_digest() dynptr assumptions&lt;/p&gt;
&lt;p&gt;The BPF verifier and the dynptr abstraction ensure that the memory space
referenced by a dynptr remains valid.  They do not, however, provide any
guarantee that the contents of the memory are stable.  kfuncs are
expected to remain memory-safe even if concurrent modifications occur.&lt;/p&gt;
&lt;p&gt;bpf_get_fsverity_digest() didn&amp;#39;t follow that: it could crash if
arg-&amp;gt;digest_size was concurrently modified.&lt;/p&gt;
&lt;p&gt;Fix that by using the known-good value hash_alg-&amp;gt;digest_size instead.&lt;/p&gt;
&lt;p&gt;Also widen &amp;#39;dynptr_sz&amp;#39; and &amp;#39;out_digest_sz&amp;#39; to u64 to match the return
type of __bpf_dynptr_size().  It doesn&amp;#39;t appear that it can actually be
more than INT_MAX currently (since __bpf_dynptr_data_rw() excludes
file-based pointers), but the correct type might as well be used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pxx7-9r2r-m5m2</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74590</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74590</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fsverity: Fix bpf_get_fsverity_digest() dynptr assumptions The BPF verifier and the dynptr abstraction ensure that the memory space referenced by a dynptr remains valid.  They do not, however, provide any guarantee that the contents of the memory are stable.  kfuncs are expected to remain memory-safe even if concurrent modifications occur. bpf_get_fsverity_digest() didn&amp;#39;t follow that: it could crash if arg-&amp;gt;digest_size was concurrently modified. Fix that by using the known-good value hash_alg-&amp;gt;digest_size instead. Also widen &amp;#39;dynptr_sz&amp;#39; and &amp;#39;out_digest_sz&amp;#39; to u64 to match the return type of __bpf_dynptr_size().  It doesn&amp;#39;t appear that it can actually be more than INT_MAX currently (since __bpf_dynptr_data_rw() excludes file-based pointers), but the correct type might as well be used.&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fsverity: Fix bpf_get_fsverity_digest() dynptr assumptions The BPF verifier and the dynptr abstraction ensure that the memory space referenced by a dynptr remains valid.  They do not, however, provide any guarantee that the contents of the memory are stable.  kfuncs are expected to remain memory-safe even if concurrent modifications occur. bpf_get_fsverity_digest() didn&amp;#39;t follow that: it could crash if arg-&amp;gt;digest_size was concurrently modified. Fix that by using the known-good value hash_alg-&amp;gt;digest_size instead. Also widen &amp;#39;dynptr_sz&amp;#39; and &amp;#39;out_digest_sz&amp;#39; to u64 to match the return type of __bpf_dynptr_size().  It doesn&amp;#39;t appear that it can actually be more than INT_MAX currently (since __bpf_dynptr_data_rw() excludes file-based pointers), but the correct type might as well be used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74590</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2970 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2970</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-2970</guid>
    </item>
  </channel>
</rss>
