<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-12T08:21:02.576363+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/certfr-2026-avi-1375</id>
    <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>
    <updated>2026-11-12T08:21:02.586516+00:00</updated>
    <content>certfr-2026-avi-1375</content>
    <link href="https://db.gcve.eu/vuln/certfr-2026-avi-1375"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-98544</id>
    <title>fkie_cve-2026-98544</title>
    <updated>2026-11-12T08:21:02.586557+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bna: prevent IOC timer rearm during teardown</p>
<p>bna: prevent IOC timer rearm during teardown</p>
<p>bnad_pci_remove() and the probe disable_ioceth path call
timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for
iocpf_timer.  bnad_iocpf_timeout() then takes bnad-&gt;bna_lock after
free_netdev() has freed the struct bnad.</p>
<p>Deleting iocpf_timer last does not fix this.  sem_timer and
iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm
iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from
bfa_ioc_hw_sem_get() when the semaphore is busy.
timer_delete_sync() only waits out its own callback.
bnad_ioceth_disable() can time out and leave that callback live.</p>
<p>Shut all four IOC timers down with timer_shutdown_sync() on both
paths, so a later mod_timer() is ignored.</p>
<p>This issue was identified during our ongoing static-analysis research
while reviewing kernel code.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-98544"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-crgf-pp48-gvh7</id>
    <title>GHSA-crgf-pp48-gvh7</title>
    <updated>2026-11-12T08:21:02.586599+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bna: prevent IOC timer rearm during teardown</p>
<p>bna: prevent IOC timer rearm during teardown</p>
<p>bnad_pci_remove() and the probe disable_ioceth path call
timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for
iocpf_timer.  bnad_iocpf_timeout() then takes bnad-&gt;bna_lock after
free_netdev() has freed the struct bnad.</p>
<p>Deleting iocpf_timer last does not fix this.  sem_timer and
iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm
iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from
bfa_ioc_hw_sem_get() when the semaphore is busy.
timer_delete_sync() only waits out its own callback.
bnad_ioceth_disable() can time out and leave that callback live.</p>
<p>Shut all four IOC timers down with timer_shutdown_sync() on both
paths, so a later mod_timer() is ignored.</p>
<p>This issue was identified during our ongoing static-analysis research
while reviewing kernel code.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-crgf-pp48-gvh7"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-98544</id>
    <title>msrc_CVE-2026-98544 — bna: prevent IOC timer rearm during teardown</title>
    <updated>2026-11-12T08:21:02.586623+00:00</updated>
    <content>msrc_CVE-2026-98544</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-98544"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-98544</id>
    <title>UBUNTU-CVE-2026-98544</title>
    <updated>2026-11-12T08:21:02.586639+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 248 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: bna: prevent IOC timer rearm during teardown bna: prevent IOC timer rearm during teardown bnad_pci_remove() and the probe disable_ioceth path call timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for iocpf_timer.  bnad_iocpf_timeout() then takes bnad-&gt;bna_lock after free_netdev() has freed the struct bnad. Deleting iocpf_timer last does not fix this.  sem_timer and iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from bfa_ioc_hw_sem_get() when the semaphore is busy. timer_delete_sync() only waits out its own callback. bnad_ioceth_disable() can time out and leave that callback live. Shut all four IOC timers down with timer_shutdown_sync() on both paths, so a later mod_timer() is ignored. This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-98544"/>
  </entry>
</feed>
