<?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>Sun, 01 Nov 2026 22:48:04 +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-98767</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98767</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: dwc3: gadget: fix IRQ storm on invalid event buffer count&lt;/p&gt;
&lt;p&gt;When dwc3_check_event_buf() reads a GEVNTCOUNT value exceeding the
event buffer length, commit 63ccd26cd1f6 (&amp;#34;usb: dwc3: gadget: check
that event count does not exceed event buffer length&amp;#34;) returns IRQ_NONE
without writing back GEVNTCOUNT. Since the DWC3 interrupt is
level-triggered, the uncleared IRQ source keeps the line asserted,
causing a tight IRQ storm that accumulates 99,900 unhandled interrupts
and triggers spurious.c:184 BUG -&amp;gt; kernel panic.&lt;/p&gt;
&lt;p&gt;The resulting call stack:
  __report_bad_irq+0xac/0xc8
  note_interrupt+0x340/0x468
  handle_irq_event+0xac/0xc0
  handle_fasteoi_irq+0x120/0x228
  gic_handle_irq+0x68/0x108
  ...
  kernel BUG at kernel/irq/spurious.c:184&lt;/p&gt;
&lt;p&gt;To reproduce, write a bogus value exceeding the event buffer length
directly to the GEVNTCOUNT register:&lt;/p&gt;
&lt;p&gt;devmem &amp;lt;DWC3_BASE + 0xc40c&amp;gt; 4 0x1004&lt;/p&gt;
&lt;p&gt;Write the bogus count back to GEVNTCOUNT to clear the IRQ source,
consistent with the stale event clearing pattern in
dwc3_event_buffers_setup(), and schedule error recovery to
reinitialize the controller.&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: dwc3: gadget: fix IRQ storm on invalid event buffer count&lt;/p&gt;
&lt;p&gt;When dwc3_check_event_buf() reads a GEVNTCOUNT value exceeding the
event buffer length, commit 63ccd26cd1f6 (&amp;#34;usb: dwc3: gadget: check
that event count does not exceed event buffer length&amp;#34;) returns IRQ_NONE
without writing back GEVNTCOUNT. Since the DWC3 interrupt is
level-triggered, the uncleared IRQ source keeps the line asserted,
causing a tight IRQ storm that accumulates 99,900 unhandled interrupts
and triggers spurious.c:184 BUG -&amp;gt; kernel panic.&lt;/p&gt;
&lt;p&gt;The resulting call stack:
  __report_bad_irq+0xac/0xc8
  note_interrupt+0x340/0x468
  handle_irq_event+0xac/0xc0
  handle_fasteoi_irq+0x120/0x228
  gic_handle_irq+0x68/0x108
  ...
  kernel BUG at kernel/irq/spurious.c:184&lt;/p&gt;
&lt;p&gt;To reproduce, write a bogus value exceeding the event buffer length
directly to the GEVNTCOUNT register:&lt;/p&gt;
&lt;p&gt;devmem &amp;lt;DWC3_BASE + 0xc40c&amp;gt; 4 0x1004&lt;/p&gt;
&lt;p&gt;Write the bogus count back to GEVNTCOUNT to clear the IRQ source,
consistent with the stale event clearing pattern in
dwc3_event_buffers_setup(), and schedule error recovery to
reinitialize the controller.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98767</guid>
    </item>
    <item>
      <title>GHSA-7v54-4578-623x</title>
      <link>https://db.gcve.eu/vuln/ghsa-7v54-4578-623x</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: dwc3: gadget: fix IRQ storm on invalid event buffer count&lt;/p&gt;
&lt;p&gt;When dwc3_check_event_buf() reads a GEVNTCOUNT value exceeding the
event buffer length, commit 63ccd26cd1f6 (&amp;#34;usb: dwc3: gadget: check
that event count does not exceed event buffer length&amp;#34;) returns IRQ_NONE
without writing back GEVNTCOUNT. Since the DWC3 interrupt is
level-triggered, the uncleared IRQ source keeps the line asserted,
causing a tight IRQ storm that accumulates 99,900 unhandled interrupts
and triggers spurious.c:184 BUG -&amp;gt; kernel panic.&lt;/p&gt;
&lt;p&gt;The resulting call stack:
  __report_bad_irq+0xac/0xc8
  note_interrupt+0x340/0x468
  handle_irq_event+0xac/0xc0
  handle_fasteoi_irq+0x120/0x228
  gic_handle_irq+0x68/0x108
  ...
  kernel BUG at kernel/irq/spurious.c:184&lt;/p&gt;
&lt;p&gt;To reproduce, write a bogus value exceeding the event buffer length
directly to the GEVNTCOUNT register:&lt;/p&gt;
&lt;p&gt;devmem &amp;lt;DWC3_BASE + 0xc40c&amp;gt; 4 0x1004&lt;/p&gt;
&lt;p&gt;Write the bogus count back to GEVNTCOUNT to clear the IRQ source,
consistent with the stale event clearing pattern in
dwc3_event_buffers_setup(), and schedule error recovery to
reinitialize the controller.&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: dwc3: gadget: fix IRQ storm on invalid event buffer count&lt;/p&gt;
&lt;p&gt;When dwc3_check_event_buf() reads a GEVNTCOUNT value exceeding the
event buffer length, commit 63ccd26cd1f6 (&amp;#34;usb: dwc3: gadget: check
that event count does not exceed event buffer length&amp;#34;) returns IRQ_NONE
without writing back GEVNTCOUNT. Since the DWC3 interrupt is
level-triggered, the uncleared IRQ source keeps the line asserted,
causing a tight IRQ storm that accumulates 99,900 unhandled interrupts
and triggers spurious.c:184 BUG -&amp;gt; kernel panic.&lt;/p&gt;
&lt;p&gt;The resulting call stack:
  __report_bad_irq+0xac/0xc8
  note_interrupt+0x340/0x468
  handle_irq_event+0xac/0xc0
  handle_fasteoi_irq+0x120/0x228
  gic_handle_irq+0x68/0x108
  ...
  kernel BUG at kernel/irq/spurious.c:184&lt;/p&gt;
&lt;p&gt;To reproduce, write a bogus value exceeding the event buffer length
directly to the GEVNTCOUNT register:&lt;/p&gt;
&lt;p&gt;devmem &amp;lt;DWC3_BASE + 0xc40c&amp;gt; 4 0x1004&lt;/p&gt;
&lt;p&gt;Write the bogus count back to GEVNTCOUNT to clear the IRQ source,
consistent with the stale event clearing pattern in
dwc3_event_buffers_setup(), and schedule error recovery to
reinitialize the controller.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-7v54-4578-623x</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98767 — usb: dwc3: gadget: fix IRQ storm on invalid event buffer count</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98767</link>
      <description>msrc_CVE-2026-98767</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98767</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98767</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98767</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 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: fix IRQ storm on invalid event buffer count When dwc3_check_event_buf() reads a GEVNTCOUNT value exceeding the event buffer length, commit 63ccd26cd1f6 (&amp;#34;usb: dwc3: gadget: check that event count does not exceed event buffer length&amp;#34;) returns IRQ_NONE without writing back GEVNTCOUNT. Since the DWC3 interrupt is level-triggered, the uncleared IRQ source keeps the line asserted, causing a tight IRQ storm that accumulates 99,900 unhandled interrupts and triggers spurious.c:184 BUG -&amp;gt; kernel panic. The resulting call stack:   __report_bad_irq+0xac/0xc8   note_interrupt+0x340/0x468   handle_irq_event+0xac/0xc0   handle_fasteoi_irq+0x120/0x228   gic_handle_irq+0x68/0x108   ...   kernel BUG at kernel/irq/spurious.c:184 To reproduce, write a bogus value exceeding the event buffer length directly to the GEVNTCOUNT register:   devmem &amp;lt;DWC3_BASE + 0xc40c&amp;gt; 4 0x1004 Write the bogus count back to GEVNTCOUNT to clear the IRQ source, consistent with the stale event clearing pattern in dwc3_event_buffers_setup(), and schedule error recovery to reinitialize the controller.&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 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: fix IRQ storm on invalid event buffer count When dwc3_check_event_buf() reads a GEVNTCOUNT value exceeding the event buffer length, commit 63ccd26cd1f6 (&amp;#34;usb: dwc3: gadget: check that event count does not exceed event buffer length&amp;#34;) returns IRQ_NONE without writing back GEVNTCOUNT. Since the DWC3 interrupt is level-triggered, the uncleared IRQ source keeps the line asserted, causing a tight IRQ storm that accumulates 99,900 unhandled interrupts and triggers spurious.c:184 BUG -&amp;gt; kernel panic. The resulting call stack:   __report_bad_irq+0xac/0xc8   note_interrupt+0x340/0x468   handle_irq_event+0xac/0xc0   handle_fasteoi_irq+0x120/0x228   gic_handle_irq+0x68/0x108   ...   kernel BUG at kernel/irq/spurious.c:184 To reproduce, write a bogus value exceeding the event buffer length directly to the GEVNTCOUNT register:   devmem &amp;lt;DWC3_BASE + 0xc40c&amp;gt; 4 0x1004 Write the bogus count back to GEVNTCOUNT to clear the IRQ source, consistent with the stale event clearing pattern in dwc3_event_buffers_setup(), and schedule error recovery to reinitialize the controller.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98767</guid>
    </item>
  </channel>
</rss>
