<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T10:05:02.915567+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bell-cve-2026-99117</id>
    <title>BELL-CVE-2026-99117</title>
    <updated>2026-11-17T10:05:02.925824+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-99117"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</id>
    <title>certfr-2026-avi-1473 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
    <updated>2026-11-17T10:05:02.925874+00:00</updated>
    <content>certfr-2026-avi-1473</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-396179</id>
    <title>EUVD-2026-396179</title>
    <updated>2026-11-17T10:05:02.925894+00:00</updated>
    <content>EUVD-2026-396179</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-396179"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99117</id>
    <title>fkie_cve-2026-99117</title>
    <updated>2026-11-17T10:05:02.925906+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>net: bridge: mcast: don't truncate the port group walk on teardown</p>
<p>__br_multicast_disable_port_ctx() and br_multicast_del_port() walk
port-&gt;mglist with hlist_for_each_entry_safe(). However,
br_multicast_find_del_pg() can also delete other entries from the same
list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().</p>
<p>If such an entry is the iterator's saved next node, hlist_del_init()
clears its -&gt;next and terminates the walk early. The reproducer triggers
this in both teardown walks, leaving port groups in the bridge mdb with
a dangling -&gt;key.port after del_nbp() frees the port:</p>
<p>BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320
   __mdb_fill_info+0x1191/0x1320
   br_mdb_dump+0x594/0xe40
   rtnl_mdb_dump+0x1cf/0x5d0</p>
<p>Use hlist_del_init_rcu() to unlink the group while preserving -&gt;next.
br_multicast_del_pg() and the teardown walks run under
br-&gt;multicast_lock. The GC worker must acquire the same lock before
detaching the group for destruction, so the node remains alive while
the walk uses the preserved pointer.</p>
<p>Preserving -&gt;next means a walk can now reach a group that an earlier
iteration already deleted as a side effect. That group is off mp-&gt;ports,
so br_multicast_find_del_pg() would fall through its port scan and hit
the trailing WARN_ON(1). Skip such groups at the top of that helper: a
port group is put on port-&gt;mglist when it is created and only unlinked
when it is delete…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99117"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-phhg-87vx-7j2v</id>
    <title>GHSA-phhg-87vx-7j2v</title>
    <updated>2026-11-17T10:05:02.925952+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>net: bridge: mcast: don't truncate the port group walk on teardown</p>
<p>__br_multicast_disable_port_ctx() and br_multicast_del_port() walk
port-&gt;mglist with hlist_for_each_entry_safe(). However,
br_multicast_find_del_pg() can also delete other entries from the same
list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().</p>
<p>If such an entry is the iterator's saved next node, hlist_del_init()
clears its -&gt;next and terminates the walk early. The reproducer triggers
this in both teardown walks, leaving port groups in the bridge mdb with
a dangling -&gt;key.port after del_nbp() frees the port:</p>
<p>BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320
   __mdb_fill_info+0x1191/0x1320
   br_mdb_dump+0x594/0xe40
   rtnl_mdb_dump+0x1cf/0x5d0</p>
<p>Use hlist_del_init_rcu() to unlink the group while preserving -&gt;next.
br_multicast_del_pg() and the teardown walks run under
br-&gt;multicast_lock. The GC worker must acquire the same lock before
detaching the group for destruction, so the node remains alive while
the walk uses the preserved pointer.</p>
<p>Preserving -&gt;next means a walk can now reach a group that an earlier
iteration already deleted as a side effect. That group is off mp-&gt;ports,
so br_multicast_find_del_pg() would fall through its port scan and hit
the trailing WARN_ON(1). Skip such groups at the top of that helper: a
port group is put on port-&gt;mglist when it is created and only unlinked
when it is delete…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-phhg-87vx-7j2v"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99117</id>
    <title>msrc_CVE-2026-99117 — net: bridge: mcast: don't truncate the port group walk on teardown</title>
    <updated>2026-11-17T10:05:02.925986+00:00</updated>
    <content>msrc_CVE-2026-99117</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99117"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-4810</id>
    <title>OESA-2026-4810 — kernel security update</title>
    <updated>2026-11-17T10:05:02.926002+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: brcmsmac: Fix dma_free_coherent() size</p>
<p>dma_alloc_consistent() may change the size to align it. The new size is
saved in alloced.</p>
<p>Change the free size to match the allocation size.(CVE-2026-31661)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/amd/display: Validate GPIO pin LUT table size before iterating</p>
<p>[Why&amp;amp;How]
The GPIO pin table parsers in get_gpio_i2c_info() and
bios_parser_get_gpio_pin_info() derive an element count from the VBIOS
table_header.structuresize field, then iterate over gpio_pin[] entries.
However, GET_IMAGE() only validates that the table header itself fits
within the BIOS image. If the VBIOS reports a structuresize larger than
the actual mapped data, the loop reads past the end of the BIOS image,
causing an out-of-bounds read.</p>
<p>Fix this by calling bios_get_image() to validate that the full claimed
structuresize is accessible within the BIOS image before entering the
loop in both functions.</p>
<p>(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)(CVE-2026-64097)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>usbip: vudc: fix NULL deref in vep_dequeue()</p>
<p>vep_alloc_request() wasn&amp;apos;t initializing vrequest-&amp;gt;udc, so cancellations
on the FunctionFS AIO path were arriving in vep_dequeue without a valid
UDC reference.</p>
<p>Since vrequest-&amp;gt;udc…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-4810"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99117</id>
    <title>UBUNTU-CVE-2026-99117</title>
    <updated>2026-11-17T10:05:02.926157+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 195 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: net: bridge: mcast: don't truncate the port group walk on teardown __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port-&gt;mglist with hlist_for_each_entry_safe(). However, br_multicast_find_del_pg() can also delete other entries from the same list through br_multicast_fwd_src_remove() or __fwd_del_star_excl(). If such an entry is the iterator's saved next node, hlist_del_init() clears its -&gt;next and terminates the walk early. The reproducer triggers this in both teardown walks, leaving port groups in the bridge mdb with a dangling -&gt;key.port after del_nbp() frees the port:   BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320    __mdb_fill_info+0x1191/0x1320    br_mdb_dump+0x594/0xe40    rtnl_mdb_dump+0x1cf/0x5d0 Use hlist_del_init_rcu() to unlink the group while preserving -&gt;next. br_multicast_del_pg() and the teardown walks run under br-&gt;multicast_lock. The GC worker must acquire the same lock before detaching the group for destruction, so the node remains alive while the walk uses the preserved pointer. Preserving -&gt;next means a walk can now reach a group that an earlier iteration already deleted as a side effect. That group is off mp-&gt;ports, so br_multicast_find_del_pg() would fall through its port scan and hit the trailing WARN_ON(1). Skip such groups at the top of that helper: a port group is put on port-&gt;mglist when it is created and only unlinked when it is deleted, so…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99117"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224</id>
    <title>WID-SEC-W-2026-4224 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-17T10:05:02.926384+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224"/>
  </entry>
</feed>
