<?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:04:18 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99455</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99455</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;serial: core: shut down initialized port on removal&lt;/p&gt;
&lt;p&gt;When a serial port configured as a console is opened and subsequently
closed, tty_port_shutdown() skips invoking port-&amp;gt;ops-&amp;gt;shutdown() because
port-&amp;gt;console is true. As a result, tty_port_initialized() remains true
and the port&amp;#39;s interrupt handler stays registered in the irq subsystem.&lt;/p&gt;
&lt;p&gt;If the underlying device is later unbound or removed (e.g. via sysfs
driver unbind or device hot-unplug), serial_core_remove_one_port()
unregisters the console, frees uport-&amp;gt;name via kfree(), and tears down
the port without shutting it down or freeing its IRQ. Consequently, the
irqaction descriptor remains registered in genirq with action-&amp;gt;name
pointing to freed memory.&lt;/p&gt;
&lt;p&gt;This triggers a use-after-free read whenever genirq accesses action-&amp;gt;name,
such as when reading /proc/interrupts:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in string+0x476/0x570
  Call Trace:
   string+0x476/0x570
   vsnprintf+0x422/0x1300
   seq_printf+0x...
   show_interrupts+...&lt;/p&gt;
&lt;p&gt;Fix this by acquiring port-&amp;gt;mutex in serial_core_remove_one_port() after
console unregistration, clearing port-&amp;gt;console under the mutex to prevent
data races with concurrent tty_port_shutdown(), and invoking
uart_shutdown(NULL, state) if the port remains initialized. This ensures
that port-&amp;gt;ops-&amp;gt;shutdown() is called and the IRQ is freed before
kfree(uport-&amp;gt;name).&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;serial: core: shut down initialized port on removal&lt;/p&gt;
&lt;p&gt;When a serial port configured as a console is opened and subsequently
closed, tty_port_shutdown() skips invoking port-&amp;gt;ops-&amp;gt;shutdown() because
port-&amp;gt;console is true. As a result, tty_port_initialized() remains true
and the port&amp;#39;s interrupt handler stays registered in the irq subsystem.&lt;/p&gt;
&lt;p&gt;If the underlying device is later unbound or removed (e.g. via sysfs
driver unbind or device hot-unplug), serial_core_remove_one_port()
unregisters the console, frees uport-&amp;gt;name via kfree(), and tears down
the port without shutting it down or freeing its IRQ. Consequently, the
irqaction descriptor remains registered in genirq with action-&amp;gt;name
pointing to freed memory.&lt;/p&gt;
&lt;p&gt;This triggers a use-after-free read whenever genirq accesses action-&amp;gt;name,
such as when reading /proc/interrupts:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in string+0x476/0x570
  Call Trace:
   string+0x476/0x570
   vsnprintf+0x422/0x1300
   seq_printf+0x...
   show_interrupts+...&lt;/p&gt;
&lt;p&gt;Fix this by acquiring port-&amp;gt;mutex in serial_core_remove_one_port() after
console unregistration, clearing port-&amp;gt;console under the mutex to prevent
data races with concurrent tty_port_shutdown(), and invoking
uart_shutdown(NULL, state) if the port remains initialized. This ensures
that port-&amp;gt;ops-&amp;gt;shutdown() is called and the IRQ is freed before
kfree(uport-&amp;gt;name).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99455</guid>
    </item>
    <item>
      <title>GHSA-qmcq-gjpg-537p</title>
      <link>https://db.gcve.eu/vuln/ghsa-qmcq-gjpg-537p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;serial: core: shut down initialized port on removal&lt;/p&gt;
&lt;p&gt;When a serial port configured as a console is opened and subsequently
closed, tty_port_shutdown() skips invoking port-&amp;gt;ops-&amp;gt;shutdown() because
port-&amp;gt;console is true. As a result, tty_port_initialized() remains true
and the port&amp;#39;s interrupt handler stays registered in the irq subsystem.&lt;/p&gt;
&lt;p&gt;If the underlying device is later unbound or removed (e.g. via sysfs
driver unbind or device hot-unplug), serial_core_remove_one_port()
unregisters the console, frees uport-&amp;gt;name via kfree(), and tears down
the port without shutting it down or freeing its IRQ. Consequently, the
irqaction descriptor remains registered in genirq with action-&amp;gt;name
pointing to freed memory.&lt;/p&gt;
&lt;p&gt;This triggers a use-after-free read whenever genirq accesses action-&amp;gt;name,
such as when reading /proc/interrupts:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in string+0x476/0x570
  Call Trace:
   string+0x476/0x570
   vsnprintf+0x422/0x1300
   seq_printf+0x...
   show_interrupts+...&lt;/p&gt;
&lt;p&gt;Fix this by acquiring port-&amp;gt;mutex in serial_core_remove_one_port() after
console unregistration, clearing port-&amp;gt;console under the mutex to prevent
data races with concurrent tty_port_shutdown(), and invoking
uart_shutdown(NULL, state) if the port remains initialized. This ensures
that port-&amp;gt;ops-&amp;gt;shutdown() is called and the IRQ is freed before
kfree(uport-&amp;gt;name).&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;serial: core: shut down initialized port on removal&lt;/p&gt;
&lt;p&gt;When a serial port configured as a console is opened and subsequently
closed, tty_port_shutdown() skips invoking port-&amp;gt;ops-&amp;gt;shutdown() because
port-&amp;gt;console is true. As a result, tty_port_initialized() remains true
and the port&amp;#39;s interrupt handler stays registered in the irq subsystem.&lt;/p&gt;
&lt;p&gt;If the underlying device is later unbound or removed (e.g. via sysfs
driver unbind or device hot-unplug), serial_core_remove_one_port()
unregisters the console, frees uport-&amp;gt;name via kfree(), and tears down
the port without shutting it down or freeing its IRQ. Consequently, the
irqaction descriptor remains registered in genirq with action-&amp;gt;name
pointing to freed memory.&lt;/p&gt;
&lt;p&gt;This triggers a use-after-free read whenever genirq accesses action-&amp;gt;name,
such as when reading /proc/interrupts:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in string+0x476/0x570
  Call Trace:
   string+0x476/0x570
   vsnprintf+0x422/0x1300
   seq_printf+0x...
   show_interrupts+...&lt;/p&gt;
&lt;p&gt;Fix this by acquiring port-&amp;gt;mutex in serial_core_remove_one_port() after
console unregistration, clearing port-&amp;gt;console under the mutex to prevent
data races with concurrent tty_port_shutdown(), and invoking
uart_shutdown(NULL, state) if the port remains initialized. This ensures
that port-&amp;gt;ops-&amp;gt;shutdown() is called and the IRQ is freed before
kfree(uport-&amp;gt;name).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-qmcq-gjpg-537p</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>
