<?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://db.gcve.eu</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, 20 Nov 2026 21:03:57 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99359</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99359</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFSD: validate transport name in listener_set before serv creation&lt;/p&gt;
&lt;p&gt;nfsd_nl_listener_set_doit() holds nfsd_mutex for the whole listener
teardown and rebuild. The code checks NFSD_A_SOCK_TRANSPORT_NAME for
presence only, and not for content. An arbitrary name therefore reaches
svc_xprt_create_from_sa(). There, a name that matches no registered class
calls request_module(&amp;#34;svc%s&amp;#34;, name). That call is a TASK_KILLABLE usermode
helper upcall, and it runs under nfsd_mutex.&lt;/p&gt;
&lt;p&gt;Check the name against the classes that NFSD can create: tcp, udp and
rdma. The check goes in nfsd_nl_validate_listeners(), which runs before
the code takes nfsd_mutex. The rejection names the offending attribute
through extack, since -EPROTONOSUPPORT on its own does not say which
entry carried the bad name.&lt;/p&gt;
&lt;p&gt;This narrows the upcall. It does not remove it. NFSD accepts &amp;#34;rdma&amp;#34;
without a condition, so on a kernel that does not build svcrdma the name
still reaches request_module(&amp;#34;svcrdma&amp;#34;) under nfsd_mutex. That is
necessary for the modular case, where the autoload is legitimate.&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;NFSD: validate transport name in listener_set before serv creation&lt;/p&gt;
&lt;p&gt;nfsd_nl_listener_set_doit() holds nfsd_mutex for the whole listener
teardown and rebuild. The code checks NFSD_A_SOCK_TRANSPORT_NAME for
presence only, and not for content. An arbitrary name therefore reaches
svc_xprt_create_from_sa(). There, a name that matches no registered class
calls request_module(&amp;#34;svc%s&amp;#34;, name). That call is a TASK_KILLABLE usermode
helper upcall, and it runs under nfsd_mutex.&lt;/p&gt;
&lt;p&gt;Check the name against the classes that NFSD can create: tcp, udp and
rdma. The check goes in nfsd_nl_validate_listeners(), which runs before
the code takes nfsd_mutex. The rejection names the offending attribute
through extack, since -EPROTONOSUPPORT on its own does not say which
entry carried the bad name.&lt;/p&gt;
&lt;p&gt;This narrows the upcall. It does not remove it. NFSD accepts &amp;#34;rdma&amp;#34;
without a condition, so on a kernel that does not build svcrdma the name
still reaches request_module(&amp;#34;svcrdma&amp;#34;) under nfsd_mutex. That is
necessary for the modular case, where the autoload is legitimate.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99359</guid>
    </item>
    <item>
      <title>GHSA-67pm-pw7x-4r44</title>
      <link>https://db.gcve.eu/vuln/ghsa-67pm-pw7x-4r44</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFSD: validate transport name in listener_set before serv creation&lt;/p&gt;
&lt;p&gt;nfsd_nl_listener_set_doit() holds nfsd_mutex for the whole listener
teardown and rebuild. The code checks NFSD_A_SOCK_TRANSPORT_NAME for
presence only, and not for content. An arbitrary name therefore reaches
svc_xprt_create_from_sa(). There, a name that matches no registered class
calls request_module(&amp;#34;svc%s&amp;#34;, name). That call is a TASK_KILLABLE usermode
helper upcall, and it runs under nfsd_mutex.&lt;/p&gt;
&lt;p&gt;Check the name against the classes that NFSD can create: tcp, udp and
rdma. The check goes in nfsd_nl_validate_listeners(), which runs before
the code takes nfsd_mutex. The rejection names the offending attribute
through extack, since -EPROTONOSUPPORT on its own does not say which
entry carried the bad name.&lt;/p&gt;
&lt;p&gt;This narrows the upcall. It does not remove it. NFSD accepts &amp;#34;rdma&amp;#34;
without a condition, so on a kernel that does not build svcrdma the name
still reaches request_module(&amp;#34;svcrdma&amp;#34;) under nfsd_mutex. That is
necessary for the modular case, where the autoload is legitimate.&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;NFSD: validate transport name in listener_set before serv creation&lt;/p&gt;
&lt;p&gt;nfsd_nl_listener_set_doit() holds nfsd_mutex for the whole listener
teardown and rebuild. The code checks NFSD_A_SOCK_TRANSPORT_NAME for
presence only, and not for content. An arbitrary name therefore reaches
svc_xprt_create_from_sa(). There, a name that matches no registered class
calls request_module(&amp;#34;svc%s&amp;#34;, name). That call is a TASK_KILLABLE usermode
helper upcall, and it runs under nfsd_mutex.&lt;/p&gt;
&lt;p&gt;Check the name against the classes that NFSD can create: tcp, udp and
rdma. The check goes in nfsd_nl_validate_listeners(), which runs before
the code takes nfsd_mutex. The rejection names the offending attribute
through extack, since -EPROTONOSUPPORT on its own does not say which
entry carried the bad name.&lt;/p&gt;
&lt;p&gt;This narrows the upcall. It does not remove it. NFSD accepts &amp;#34;rdma&amp;#34;
without a condition, so on a kernel that does not build svcrdma the name
still reaches request_module(&amp;#34;svcrdma&amp;#34;) under nfsd_mutex. That is
necessary for the modular case, where the autoload is legitimate.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-67pm-pw7x-4r44</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</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 einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&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 einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
