<?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>Mon, 02 Nov 2026 20:21:08 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98763</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98763</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: core: clear both ep_in and ep_out for non-ep0 control endpoints&lt;/p&gt;
&lt;p&gt;In usb_enable_endpoint(), non-zero control endpoints (where
usb_endpoint_xfer_control(&amp;amp;ep-&amp;gt;desc) is true) populate both
dev-&amp;gt;ep_in[epnum] and dev-&amp;gt;ep_out[epnum] with the same struct
usb_host_endpoint pointer.&lt;/p&gt;
&lt;p&gt;However, usb_disable_endpoint() only clears either dev-&amp;gt;ep_out[epnum] or
dev-&amp;gt;ep_in[epnum] depending on the direction bit of epaddr when
reset_hardware is set, leaving the opposite direction&amp;#39;s array slot
pointing to the disabled/freed endpoint.&lt;/p&gt;
&lt;p&gt;Clear both dev-&amp;gt;ep_out[epnum] and dev-&amp;gt;ep_in[epnum] when disabling a
non-ep0 control endpoint with reset_hardware set, and update the
function kerneldoc accordingly.&lt;/p&gt;
&lt;p&gt;Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to
enumerate a USB device with a non-zero control endpoint
(bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL),
verifying that both dev-&amp;gt;ep_in[1] and dev-&amp;gt;ep_out[1] are cleared when
the interface is disabled.&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;usb: core: clear both ep_in and ep_out for non-ep0 control endpoints&lt;/p&gt;
&lt;p&gt;In usb_enable_endpoint(), non-zero control endpoints (where
usb_endpoint_xfer_control(&amp;amp;ep-&amp;gt;desc) is true) populate both
dev-&amp;gt;ep_in[epnum] and dev-&amp;gt;ep_out[epnum] with the same struct
usb_host_endpoint pointer.&lt;/p&gt;
&lt;p&gt;However, usb_disable_endpoint() only clears either dev-&amp;gt;ep_out[epnum] or
dev-&amp;gt;ep_in[epnum] depending on the direction bit of epaddr when
reset_hardware is set, leaving the opposite direction&amp;#39;s array slot
pointing to the disabled/freed endpoint.&lt;/p&gt;
&lt;p&gt;Clear both dev-&amp;gt;ep_out[epnum] and dev-&amp;gt;ep_in[epnum] when disabling a
non-ep0 control endpoint with reset_hardware set, and update the
function kerneldoc accordingly.&lt;/p&gt;
&lt;p&gt;Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to
enumerate a USB device with a non-zero control endpoint
(bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL),
verifying that both dev-&amp;gt;ep_in[1] and dev-&amp;gt;ep_out[1] are cleared when
the interface is disabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98763</guid>
    </item>
    <item>
      <title>GHSA-f752-7j6x-76w7</title>
      <link>https://db.gcve.eu/vuln/ghsa-f752-7j6x-76w7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: core: clear both ep_in and ep_out for non-ep0 control endpoints&lt;/p&gt;
&lt;p&gt;In usb_enable_endpoint(), non-zero control endpoints (where
usb_endpoint_xfer_control(&amp;amp;ep-&amp;gt;desc) is true) populate both
dev-&amp;gt;ep_in[epnum] and dev-&amp;gt;ep_out[epnum] with the same struct
usb_host_endpoint pointer.&lt;/p&gt;
&lt;p&gt;However, usb_disable_endpoint() only clears either dev-&amp;gt;ep_out[epnum] or
dev-&amp;gt;ep_in[epnum] depending on the direction bit of epaddr when
reset_hardware is set, leaving the opposite direction&amp;#39;s array slot
pointing to the disabled/freed endpoint.&lt;/p&gt;
&lt;p&gt;Clear both dev-&amp;gt;ep_out[epnum] and dev-&amp;gt;ep_in[epnum] when disabling a
non-ep0 control endpoint with reset_hardware set, and update the
function kerneldoc accordingly.&lt;/p&gt;
&lt;p&gt;Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to
enumerate a USB device with a non-zero control endpoint
(bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL),
verifying that both dev-&amp;gt;ep_in[1] and dev-&amp;gt;ep_out[1] are cleared when
the interface is disabled.&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;usb: core: clear both ep_in and ep_out for non-ep0 control endpoints&lt;/p&gt;
&lt;p&gt;In usb_enable_endpoint(), non-zero control endpoints (where
usb_endpoint_xfer_control(&amp;amp;ep-&amp;gt;desc) is true) populate both
dev-&amp;gt;ep_in[epnum] and dev-&amp;gt;ep_out[epnum] with the same struct
usb_host_endpoint pointer.&lt;/p&gt;
&lt;p&gt;However, usb_disable_endpoint() only clears either dev-&amp;gt;ep_out[epnum] or
dev-&amp;gt;ep_in[epnum] depending on the direction bit of epaddr when
reset_hardware is set, leaving the opposite direction&amp;#39;s array slot
pointing to the disabled/freed endpoint.&lt;/p&gt;
&lt;p&gt;Clear both dev-&amp;gt;ep_out[epnum] and dev-&amp;gt;ep_in[epnum] when disabling a
non-ep0 control endpoint with reset_hardware set, and update the
function kerneldoc accordingly.&lt;/p&gt;
&lt;p&gt;Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to
enumerate a USB device with a non-zero control endpoint
(bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL),
verifying that both dev-&amp;gt;ep_in[1] and dev-&amp;gt;ep_out[1] are cleared when
the interface is disabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-f752-7j6x-76w7</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98763 — usb: core: clear both ep_in and ep_out for non-ep0 control endpoints</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98763</link>
      <description>msrc_CVE-2026-98763</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98763</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98763</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98763</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: core: clear both ep_in and ep_out for non-ep0 control endpoints In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&amp;amp;ep-&amp;gt;desc) is true) populate both dev-&amp;gt;ep_in[epnum] and dev-&amp;gt;ep_out[epnum] with the same struct usb_host_endpoint pointer. However, usb_disable_endpoint() only clears either dev-&amp;gt;ep_out[epnum] or dev-&amp;gt;ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction&amp;#39;s array slot pointing to the disabled/freed endpoint. Clear both dev-&amp;gt;ep_out[epnum] and dev-&amp;gt;ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly. Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev-&amp;gt;ep_in[1] and dev-&amp;gt;ep_out[1] are cleared when the interface is disabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: core: clear both ep_in and ep_out for non-ep0 control endpoints In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&amp;amp;ep-&amp;gt;desc) is true) populate both dev-&amp;gt;ep_in[epnum] and dev-&amp;gt;ep_out[epnum] with the same struct usb_host_endpoint pointer. However, usb_disable_endpoint() only clears either dev-&amp;gt;ep_out[epnum] or dev-&amp;gt;ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction&amp;#39;s array slot pointing to the disabled/freed endpoint. Clear both dev-&amp;gt;ep_out[epnum] and dev-&amp;gt;ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly. Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev-&amp;gt;ep_in[1] and dev-&amp;gt;ep_out[1] are cleared when the interface is disabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98763</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</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-4019</guid>
    </item>
  </channel>
</rss>
