<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 10:05:02 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99117</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99117</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-99117</guid>
    </item>
    <item>
      <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>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</link>
      <description>certfr-2026-avi-1473</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</guid>
    </item>
    <item>
      <title>EUVD-2026-396179</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396179</link>
      <description>EUVD-2026-396179</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396179</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99117</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99117</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bridge: mcast: don&amp;#39;t truncate the port group walk on teardown&lt;/p&gt;
&lt;p&gt;__br_multicast_disable_port_ctx() and br_multicast_del_port() walk
port-&amp;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().&lt;/p&gt;
&lt;p&gt;If such an entry is the iterator&amp;#39;s saved next node, hlist_del_init()
clears its -&amp;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 -&amp;gt;key.port after del_nbp() frees the port:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;Use hlist_del_init_rcu() to unlink the group while preserving -&amp;gt;next.
br_multicast_del_pg() and the teardown walks run under
br-&amp;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.&lt;/p&gt;
&lt;p&gt;Preserving -&amp;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-&amp;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-&amp;gt;mglist when it is created and only unlinked
when it is delete…&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;net: bridge: mcast: don&amp;#39;t truncate the port group walk on teardown&lt;/p&gt;
&lt;p&gt;__br_multicast_disable_port_ctx() and br_multicast_del_port() walk
port-&amp;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().&lt;/p&gt;
&lt;p&gt;If such an entry is the iterator&amp;#39;s saved next node, hlist_del_init()
clears its -&amp;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 -&amp;gt;key.port after del_nbp() frees the port:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;Use hlist_del_init_rcu() to unlink the group while preserving -&amp;gt;next.
br_multicast_del_pg() and the teardown walks run under
br-&amp;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.&lt;/p&gt;
&lt;p&gt;Preserving -&amp;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-&amp;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-&amp;gt;mglist when it is created and only unlinked
when it is delete…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99117</guid>
    </item>
    <item>
      <title>GHSA-phhg-87vx-7j2v</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-phhg-87vx-7j2v</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bridge: mcast: don&amp;#39;t truncate the port group walk on teardown&lt;/p&gt;
&lt;p&gt;__br_multicast_disable_port_ctx() and br_multicast_del_port() walk
port-&amp;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().&lt;/p&gt;
&lt;p&gt;If such an entry is the iterator&amp;#39;s saved next node, hlist_del_init()
clears its -&amp;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 -&amp;gt;key.port after del_nbp() frees the port:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;Use hlist_del_init_rcu() to unlink the group while preserving -&amp;gt;next.
br_multicast_del_pg() and the teardown walks run under
br-&amp;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.&lt;/p&gt;
&lt;p&gt;Preserving -&amp;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-&amp;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-&amp;gt;mglist when it is created and only unlinked
when it is delete…&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;net: bridge: mcast: don&amp;#39;t truncate the port group walk on teardown&lt;/p&gt;
&lt;p&gt;__br_multicast_disable_port_ctx() and br_multicast_del_port() walk
port-&amp;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().&lt;/p&gt;
&lt;p&gt;If such an entry is the iterator&amp;#39;s saved next node, hlist_del_init()
clears its -&amp;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 -&amp;gt;key.port after del_nbp() frees the port:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;Use hlist_del_init_rcu() to unlink the group while preserving -&amp;gt;next.
br_multicast_del_pg() and the teardown walks run under
br-&amp;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.&lt;/p&gt;
&lt;p&gt;Preserving -&amp;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-&amp;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-&amp;gt;mglist when it is created and only unlinked
when it is delete…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-phhg-87vx-7j2v</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99117 — net: bridge: mcast: don't truncate the port group walk on teardown</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99117</link>
      <description>msrc_CVE-2026-99117</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99117</guid>
    </item>
    <item>
      <title>OESA-2026-4810 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-4810</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmsmac: Fix dma_free_coherent() size&lt;/p&gt;
&lt;p&gt;dma_alloc_consistent() may change the size to align it. The new size is
saved in alloced.&lt;/p&gt;
&lt;p&gt;Change the free size to match the allocation size.(CVE-2026-31661)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Validate GPIO pin LUT table size before iterating&lt;/p&gt;
&lt;p&gt;[Why&amp;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)(CVE-2026-64097)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usbip: vudc: fix NULL deref in vep_dequeue()&lt;/p&gt;
&lt;p&gt;vep_alloc_request() wasn&amp;amp;apos;t initializing vrequest-&amp;amp;gt;udc, so cancellations
on the FunctionFS AIO path were arriving in vep_dequeue without a valid
UDC reference.&lt;/p&gt;
&lt;p&gt;Since vrequest-&amp;amp;gt;udc…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmsmac: Fix dma_free_coherent() size&lt;/p&gt;
&lt;p&gt;dma_alloc_consistent() may change the size to align it. The new size is
saved in alloced.&lt;/p&gt;
&lt;p&gt;Change the free size to match the allocation size.(CVE-2026-31661)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Validate GPIO pin LUT table size before iterating&lt;/p&gt;
&lt;p&gt;[Why&amp;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)(CVE-2026-64097)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usbip: vudc: fix NULL deref in vep_dequeue()&lt;/p&gt;
&lt;p&gt;vep_alloc_request() wasn&amp;amp;apos;t initializing vrequest-&amp;amp;gt;udc, so cancellations
on the FunctionFS AIO path were arriving in vep_dequeue without a valid
UDC reference.&lt;/p&gt;
&lt;p&gt;Since vrequest-&amp;amp;gt;udc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-4810</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99117</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99117</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 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: bridge: mcast: don&amp;#39;t truncate the port group walk on teardown __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port-&amp;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&amp;#39;s saved next node, hlist_del_init() clears its -&amp;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 -&amp;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 -&amp;gt;next. br_multicast_del_pg() and the teardown walks run under br-&amp;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 -&amp;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-&amp;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-&amp;gt;mglist when it is created and only unlinked when it is deleted, so…&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 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: bridge: mcast: don&amp;#39;t truncate the port group walk on teardown __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port-&amp;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&amp;#39;s saved next node, hlist_del_init() clears its -&amp;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 -&amp;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 -&amp;gt;next. br_multicast_del_pg() and the teardown walks run under br-&amp;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 -&amp;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-&amp;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-&amp;gt;mglist when it is created and only unlinked when it is deleted, so…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99117</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4224 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224</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://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224</guid>
    </item>
  </channel>
</rss>
