<?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 20:41:50 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99779</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99779</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/9p/usbg: call disable_usb9pfs() from usb9pfs_disable()&lt;/p&gt;
&lt;p&gt;usb9pfs_disable() is the usb_function -&amp;gt;disable callback, invoked by
the composite gadget core whenever the host resets or unconfigures
the gadget. The gadget function API requires this callback to disable
its endpoints; every other in-tree function driver does so from its
-&amp;gt;disable hook.&lt;/p&gt;
&lt;p&gt;usb9pfs_disable() never called disable_usb9pfs(), so the IN/OUT
endpoints and their usb_request objects were left active and
allocated across a host-driven disable. When the host later
reconfigures the device, enable_usb9pfs() calls alloc_requests() again
and unconditionally overwrites usb9pfs-&amp;gt;in_req/out_req, permanently
leaking the previous allocations, while the endpoints themselves are
left enabled underneath the function&amp;#39;s own idea of being disabled.&lt;/p&gt;
&lt;p&gt;Call disable_usb9pfs() before reinit_completion(&amp;amp;usb9pfs-&amp;gt;send),
mirroring the same sequence already used in p9_usbg_close(). Placing
it before the reinit_completion() also ensures usb_ep_disable() has
synchronously flushed any requests still queued in hardware before the
completion is reset, closing the same race that motivated resetting
the completion here in the first place.&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;net/9p/usbg: call disable_usb9pfs() from usb9pfs_disable()&lt;/p&gt;
&lt;p&gt;usb9pfs_disable() is the usb_function -&amp;gt;disable callback, invoked by
the composite gadget core whenever the host resets or unconfigures
the gadget. The gadget function API requires this callback to disable
its endpoints; every other in-tree function driver does so from its
-&amp;gt;disable hook.&lt;/p&gt;
&lt;p&gt;usb9pfs_disable() never called disable_usb9pfs(), so the IN/OUT
endpoints and their usb_request objects were left active and
allocated across a host-driven disable. When the host later
reconfigures the device, enable_usb9pfs() calls alloc_requests() again
and unconditionally overwrites usb9pfs-&amp;gt;in_req/out_req, permanently
leaking the previous allocations, while the endpoints themselves are
left enabled underneath the function&amp;#39;s own idea of being disabled.&lt;/p&gt;
&lt;p&gt;Call disable_usb9pfs() before reinit_completion(&amp;amp;usb9pfs-&amp;gt;send),
mirroring the same sequence already used in p9_usbg_close(). Placing
it before the reinit_completion() also ensures usb_ep_disable() has
synchronously flushed any requests still queued in hardware before the
completion is reset, closing the same race that motivated resetting
the completion here in the first place.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99779</guid>
    </item>
    <item>
      <title>GHSA-fg8v-rx56-65pf</title>
      <link>https://db.gcve.eu/vuln/ghsa-fg8v-rx56-65pf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/9p/usbg: call disable_usb9pfs() from usb9pfs_disable()&lt;/p&gt;
&lt;p&gt;usb9pfs_disable() is the usb_function -&amp;gt;disable callback, invoked by
the composite gadget core whenever the host resets or unconfigures
the gadget. The gadget function API requires this callback to disable
its endpoints; every other in-tree function driver does so from its
-&amp;gt;disable hook.&lt;/p&gt;
&lt;p&gt;usb9pfs_disable() never called disable_usb9pfs(), so the IN/OUT
endpoints and their usb_request objects were left active and
allocated across a host-driven disable. When the host later
reconfigures the device, enable_usb9pfs() calls alloc_requests() again
and unconditionally overwrites usb9pfs-&amp;gt;in_req/out_req, permanently
leaking the previous allocations, while the endpoints themselves are
left enabled underneath the function&amp;#39;s own idea of being disabled.&lt;/p&gt;
&lt;p&gt;Call disable_usb9pfs() before reinit_completion(&amp;amp;usb9pfs-&amp;gt;send),
mirroring the same sequence already used in p9_usbg_close(). Placing
it before the reinit_completion() also ensures usb_ep_disable() has
synchronously flushed any requests still queued in hardware before the
completion is reset, closing the same race that motivated resetting
the completion here in the first place.&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;net/9p/usbg: call disable_usb9pfs() from usb9pfs_disable()&lt;/p&gt;
&lt;p&gt;usb9pfs_disable() is the usb_function -&amp;gt;disable callback, invoked by
the composite gadget core whenever the host resets or unconfigures
the gadget. The gadget function API requires this callback to disable
its endpoints; every other in-tree function driver does so from its
-&amp;gt;disable hook.&lt;/p&gt;
&lt;p&gt;usb9pfs_disable() never called disable_usb9pfs(), so the IN/OUT
endpoints and their usb_request objects were left active and
allocated across a host-driven disable. When the host later
reconfigures the device, enable_usb9pfs() calls alloc_requests() again
and unconditionally overwrites usb9pfs-&amp;gt;in_req/out_req, permanently
leaking the previous allocations, while the endpoints themselves are
left enabled underneath the function&amp;#39;s own idea of being disabled.&lt;/p&gt;
&lt;p&gt;Call disable_usb9pfs() before reinit_completion(&amp;amp;usb9pfs-&amp;gt;send),
mirroring the same sequence already used in p9_usbg_close(). Placing
it before the reinit_completion() also ensures usb_ep_disable() has
synchronously flushed any requests still queued in hardware before the
completion is reset, closing the same race that motivated resetting
the completion here in the first place.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-fg8v-rx56-65pf</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>
