<?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://127.0.0.1:10001</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, 21 Nov 2026 10:34:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-40326</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-40326</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://127.0.0.1:10001/vuln/bell-cve-2025-40326</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0169 — 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://127.0.0.1:10001/vuln/certfr-2026-avi-0169</link>
      <description>certfr-2026-avi-0169</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0169</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40326</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40326</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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: NFSD: Define actions for the new time_deleg FATTR4 attributes NFSv4 clients won&amp;#39;t send legitimate GETATTR requests for these new attributes because they are intended to be used only with CB_GETATTR and SETATTR. But NFSD has to do something besides crashing if it ever sees a GETATTR request that queries these attributes. RFC 8881 Section 18.7.3 states: &amp;gt; The server MUST return a value for each attribute that the client &amp;gt; requests if the attribute is supported by the server for the &amp;gt; target file system. If the server does not support a particular &amp;gt; attribute on the target file system, then it MUST NOT return the &amp;gt; attribute value and MUST NOT set the attribute bit in the result &amp;gt; bitmap. The server MUST return an error if it supports an &amp;gt; attribute on the target but cannot obtain its value. In that case, &amp;gt; no attribute values will be returned. Further, RFC 9754 Section 5 states: &amp;gt; These new attributes are invalid to be used with GETATTR, VERIFY, &amp;gt; and NVERIFY, and they can only be used with CB_GETATTR and SETATTR &amp;gt; by a client holding an appropriate delegation. Thus there does not appear to be a specific server response mandated by specification. Taking the guidance that querying these attributes via GETATTR is &amp;#34;invalid&amp;#34;, NFSD will return nfserr_inval, failing the request entirely.&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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: NFSD: Define actions for the new time_deleg FATTR4 attributes NFSv4 clients won&amp;#39;t send legitimate GETATTR requests for these new attributes because they are intended to be used only with CB_GETATTR and SETATTR. But NFSD has to do something besides crashing if it ever sees a GETATTR request that queries these attributes. RFC 8881 Section 18.7.3 states: &amp;gt; The server MUST return a value for each attribute that the client &amp;gt; requests if the attribute is supported by the server for the &amp;gt; target file system. If the server does not support a particular &amp;gt; attribute on the target file system, then it MUST NOT return the &amp;gt; attribute value and MUST NOT set the attribute bit in the result &amp;gt; bitmap. The server MUST return an error if it supports an &amp;gt; attribute on the target but cannot obtain its value. In that case, &amp;gt; no attribute values will be returned. Further, RFC 9754 Section 5 states: &amp;gt; These new attributes are invalid to be used with GETATTR, VERIFY, &amp;gt; and NVERIFY, and they can only be used with CB_GETATTR and SETATTR &amp;gt; by a client holding an appropriate delegation. Thus there does not appear to be a specific server response mandated by specification. Taking the guidance that querying these attributes via GETATTR is &amp;#34;invalid&amp;#34;, NFSD will return nfserr_inval, failing the request entirely.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40326</guid>
    </item>
  </channel>
</rss>
