<?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 05:16:55 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89710</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-89710</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-89710</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-367696</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367696</link>
      <description>EUVD-2026-367696</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367696</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89710</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-89710</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path&lt;/p&gt;
&lt;p&gt;When the server returns a new layout stateid while a valid one is still
held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on
the on-stack free_me list and jumps to out_forget. Segments whose
reference count drops to zero are unlinked from lo-&amp;gt;plh_segs and moved
to free_me by mark_lseg_invalid(); for an idle cached segment the layout
header holds the only reference, so this happens on the first decrement.&lt;/p&gt;
&lt;p&gt;out_forget never drains free_me -- only the success path calls
pnfs_free_lseg_list().&lt;/p&gt;
&lt;p&gt;Commit 814b84971388 (&amp;#34;pNFS/NFSv4: Fix a layout segment leak in
pnfs_layout_process()&amp;#34;) added the drain; commit 08bd8dbe8882
(&amp;#34;pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()&amp;#34;)
removed it while switching the destination to lo-&amp;gt;plh_return_segs, which
is drained elsewhere. Commit fb700ef02676 (&amp;#34;NFSv4.1: Simplify layout
return in pnfs_layout_process()&amp;#34;) switched the destination back to
free_me without restoring the drain.&lt;/p&gt;
&lt;p&gt;Restore the pnfs_free_lseg_list() call.&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;NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path&lt;/p&gt;
&lt;p&gt;When the server returns a new layout stateid while a valid one is still
held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on
the on-stack free_me list and jumps to out_forget. Segments whose
reference count drops to zero are unlinked from lo-&amp;gt;plh_segs and moved
to free_me by mark_lseg_invalid(); for an idle cached segment the layout
header holds the only reference, so this happens on the first decrement.&lt;/p&gt;
&lt;p&gt;out_forget never drains free_me -- only the success path calls
pnfs_free_lseg_list().&lt;/p&gt;
&lt;p&gt;Commit 814b84971388 (&amp;#34;pNFS/NFSv4: Fix a layout segment leak in
pnfs_layout_process()&amp;#34;) added the drain; commit 08bd8dbe8882
(&amp;#34;pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()&amp;#34;)
removed it while switching the destination to lo-&amp;gt;plh_return_segs, which
is drained elsewhere. Commit fb700ef02676 (&amp;#34;NFSv4.1: Simplify layout
return in pnfs_layout_process()&amp;#34;) switched the destination back to
free_me without restoring the drain.&lt;/p&gt;
&lt;p&gt;Restore the pnfs_free_lseg_list() call.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-89710</guid>
    </item>
    <item>
      <title>GHSA-84pc-7mxq-h2j8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-84pc-7mxq-h2j8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path&lt;/p&gt;
&lt;p&gt;When the server returns a new layout stateid while a valid one is still
held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on
the on-stack free_me list and jumps to out_forget. Segments whose
reference count drops to zero are unlinked from lo-&amp;gt;plh_segs and moved
to free_me by mark_lseg_invalid(); for an idle cached segment the layout
header holds the only reference, so this happens on the first decrement.&lt;/p&gt;
&lt;p&gt;out_forget never drains free_me -- only the success path calls
pnfs_free_lseg_list().&lt;/p&gt;
&lt;p&gt;Commit 814b84971388 (&amp;#34;pNFS/NFSv4: Fix a layout segment leak in
pnfs_layout_process()&amp;#34;) added the drain; commit 08bd8dbe8882
(&amp;#34;pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()&amp;#34;)
removed it while switching the destination to lo-&amp;gt;plh_return_segs, which
is drained elsewhere. Commit fb700ef02676 (&amp;#34;NFSv4.1: Simplify layout
return in pnfs_layout_process()&amp;#34;) switched the destination back to
free_me without restoring the drain.&lt;/p&gt;
&lt;p&gt;Restore the pnfs_free_lseg_list() call.&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;NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path&lt;/p&gt;
&lt;p&gt;When the server returns a new layout stateid while a valid one is still
held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on
the on-stack free_me list and jumps to out_forget. Segments whose
reference count drops to zero are unlinked from lo-&amp;gt;plh_segs and moved
to free_me by mark_lseg_invalid(); for an idle cached segment the layout
header holds the only reference, so this happens on the first decrement.&lt;/p&gt;
&lt;p&gt;out_forget never drains free_me -- only the success path calls
pnfs_free_lseg_list().&lt;/p&gt;
&lt;p&gt;Commit 814b84971388 (&amp;#34;pNFS/NFSv4: Fix a layout segment leak in
pnfs_layout_process()&amp;#34;) added the drain; commit 08bd8dbe8882
(&amp;#34;pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()&amp;#34;)
removed it while switching the destination to lo-&amp;gt;plh_return_segs, which
is drained elsewhere. Commit fb700ef02676 (&amp;#34;NFSv4.1: Simplify layout
return in pnfs_layout_process()&amp;#34;) switched the destination back to
free_me without restoring the drain.&lt;/p&gt;
&lt;p&gt;Restore the pnfs_free_lseg_list() call.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-84pc-7mxq-h2j8</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89710</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89710</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path When the server returns a new layout stateid while a valid one is still held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on the on-stack free_me list and jumps to out_forget. Segments whose reference count drops to zero are unlinked from lo-&amp;gt;plh_segs and moved to free_me by mark_lseg_invalid(); for an idle cached segment the layout header holds the only reference, so this happens on the first decrement. out_forget never drains free_me -- only the success path calls pnfs_free_lseg_list(). Commit 814b84971388 (&amp;#34;pNFS/NFSv4: Fix a layout segment leak in pnfs_layout_process()&amp;#34;) added the drain; commit 08bd8dbe8882 (&amp;#34;pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()&amp;#34;) removed it while switching the destination to lo-&amp;gt;plh_return_segs, which is drained elsewhere. Commit fb700ef02676 (&amp;#34;NFSv4.1: Simplify layout return in pnfs_layout_process()&amp;#34;) switched the destination back to free_me without restoring the drain. Restore the pnfs_free_lseg_list() call.&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path When the server returns a new layout stateid while a valid one is still held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on the on-stack free_me list and jumps to out_forget. Segments whose reference count drops to zero are unlinked from lo-&amp;gt;plh_segs and moved to free_me by mark_lseg_invalid(); for an idle cached segment the layout header holds the only reference, so this happens on the first decrement. out_forget never drains free_me -- only the success path calls pnfs_free_lseg_list(). Commit 814b84971388 (&amp;#34;pNFS/NFSv4: Fix a layout segment leak in pnfs_layout_process()&amp;#34;) added the drain; commit 08bd8dbe8882 (&amp;#34;pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()&amp;#34;) removed it while switching the destination to lo-&amp;gt;plh_return_segs, which is drained elsewhere. Commit fb700ef02676 (&amp;#34;NFSv4.1: Simplify layout return in pnfs_layout_process()&amp;#34;) switched the destination back to free_me without restoring the drain. Restore the pnfs_free_lseg_list() call.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89710</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3321 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</guid>
    </item>
  </channel>
</rss>
