<?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>Fri, 02 Oct 2026 18:36:31 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04420</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04420</link>
      <description>bdu:2025-04420</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04420</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0252 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</link>
      <description>certfr-2025-avi-0252</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</guid>
    </item>
    <item>
      <title>EUVD-2026-344770</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344770</link>
      <description>EUVD-2026-344770</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344770</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49667</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49667</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bonding: fix use-after-free after 802.3ad slave unbind&lt;/p&gt;
&lt;p&gt;commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;),
resolve case, when there is several aggregation groups in the same bond.
bond_3ad_unbind_slave will invalidate (clear) aggregator when
__agg_active_ports return zero. So, ad_clear_agg can be executed even, when
num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for,
previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave
will not update slave ports list, because lag_ports==NULL. So, here we
got slave ports, pointing to freed aggregator memory.&lt;/p&gt;
&lt;p&gt;Fix with checking actual number of ports in group (as was before
commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;) ),
before ad_clear_agg().&lt;/p&gt;
&lt;p&gt;The KASAN logs are as follows:&lt;/p&gt;
&lt;p&gt;[  767.617392] ==================================================================
[  767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470
[  767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767
[  767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G           O 5.15.11 #15
[  767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT)
[  767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler
[  767.666468] Call trace:
[  767.668930]  dump_backtrace+0x0/0x2d0
[  767.672625]  show_stack+0x24/0x30
[  767.675965]  dump_stack_lvl+0x68/0x84
[  767.679659]  prin…&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: bonding: fix use-after-free after 802.3ad slave unbind&lt;/p&gt;
&lt;p&gt;commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;),
resolve case, when there is several aggregation groups in the same bond.
bond_3ad_unbind_slave will invalidate (clear) aggregator when
__agg_active_ports return zero. So, ad_clear_agg can be executed even, when
num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for,
previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave
will not update slave ports list, because lag_ports==NULL. So, here we
got slave ports, pointing to freed aggregator memory.&lt;/p&gt;
&lt;p&gt;Fix with checking actual number of ports in group (as was before
commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;) ),
before ad_clear_agg().&lt;/p&gt;
&lt;p&gt;The KASAN logs are as follows:&lt;/p&gt;
&lt;p&gt;[  767.617392] ==================================================================
[  767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470
[  767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767
[  767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G           O 5.15.11 #15
[  767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT)
[  767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler
[  767.666468] Call trace:
[  767.668930]  dump_backtrace+0x0/0x2d0
[  767.672625]  show_stack+0x24/0x30
[  767.675965]  dump_stack_lvl+0x68/0x84
[  767.679659]  prin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49667</guid>
    </item>
    <item>
      <title>GHSA-5wq4-958x-w5fq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5wq4-958x-w5fq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bonding: fix use-after-free after 802.3ad slave unbind&lt;/p&gt;
&lt;p&gt;commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;),
resolve case, when there is several aggregation groups in the same bond.
bond_3ad_unbind_slave will invalidate (clear) aggregator when
__agg_active_ports return zero. So, ad_clear_agg can be executed even, when
num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for,
previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave
will not update slave ports list, because lag_ports==NULL. So, here we
got slave ports, pointing to freed aggregator memory.&lt;/p&gt;
&lt;p&gt;Fix with checking actual number of ports in group (as was before
commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;) ),
before ad_clear_agg().&lt;/p&gt;
&lt;p&gt;The KASAN logs are as follows:&lt;/p&gt;
&lt;p&gt;[  767.617392] ==================================================================
[  767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470
[  767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767
[  767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G           O 5.15.11 #15
[  767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT)
[  767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler
[  767.666468] Call trace:
[  767.668930]  dump_backtrace+0x0/0x2d0
[  767.672625]  show_stack+0x24/0x30
[  767.675965]  dump_stack_lvl+0x68/0x84
[  767.679659]  prin…&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: bonding: fix use-after-free after 802.3ad slave unbind&lt;/p&gt;
&lt;p&gt;commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;),
resolve case, when there is several aggregation groups in the same bond.
bond_3ad_unbind_slave will invalidate (clear) aggregator when
__agg_active_ports return zero. So, ad_clear_agg can be executed even, when
num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for,
previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave
will not update slave ports list, because lag_ports==NULL. So, here we
got slave ports, pointing to freed aggregator memory.&lt;/p&gt;
&lt;p&gt;Fix with checking actual number of ports in group (as was before
commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;) ),
before ad_clear_agg().&lt;/p&gt;
&lt;p&gt;The KASAN logs are as follows:&lt;/p&gt;
&lt;p&gt;[  767.617392] ==================================================================
[  767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470
[  767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767
[  767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G           O 5.15.11 #15
[  767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT)
[  767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler
[  767.666468] Call trace:
[  767.668930]  dump_backtrace+0x0/0x2d0
[  767.672625]  show_stack+0x24/0x30
[  767.675965]  dump_stack_lvl+0x68/0x84
[  767.679659]  prin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5wq4-958x-w5fq</guid>
    </item>
    <item>
      <title>RHSA-2026:1494 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:1494</link>
      <description>&lt;p&gt;kernel: mac80211: fix potential double free on mesh join kernel: Linux kernel: be2net buffer overflow in be_get_module_eeprom kernel: net: bonding: fix use-after-free after 802.3ad slave unbind kernel: Linux kernel: Information disclosure and denial of service in ntb_hw_switchtec module kernel: RDMA/rxe: Fix incomplete state save in rxe_requester kernel: Linux kernel (openvswitch): Denial of Service and limited data exposure via improper key length validation kernel: KVM: arm64: Tear down vGIC on failed vCPU creation kernel: smb: client: Fix use-after-free in cifs_fill_dirent kernel: i40e: fix idx validation in config queues msg kernel: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping kernel: Linux kernel: vsock vulnerability may lead to memory corruption kernel: mptcp: fix race condition in mptcp_schedule_work() kernel: drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: mac80211: fix potential double free on mesh join kernel: Linux kernel: be2net buffer overflow in be_get_module_eeprom kernel: net: bonding: fix use-after-free after 802.3ad slave unbind kernel: Linux kernel: Information disclosure and denial of service in ntb_hw_switchtec module kernel: RDMA/rxe: Fix incomplete state save in rxe_requester kernel: Linux kernel (openvswitch): Denial of Service and limited data exposure via improper key length validation kernel: KVM: arm64: Tear down vGIC on failed vCPU creation kernel: smb: client: Fix use-after-free in cifs_fill_dirent kernel: i40e: fix idx validation in config queues msg kernel: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping kernel: Linux kernel: vsock vulnerability may lead to memory corruption kernel: mptcp: fix race condition in mptcp_schedule_work() kernel: drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:1494</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:1176-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49667</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49667</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 143 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix use-after-free after 802.3ad slave unbind commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;), resolve case, when there is several aggregation groups in the same bond. bond_3ad_unbind_slave will invalidate (clear) aggregator when __agg_active_ports return zero. So, ad_clear_agg can be executed even, when num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for, previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave will not update slave ports list, because lag_ports==NULL. So, here we got slave ports, pointing to freed aggregator memory. Fix with checking actual number of ports in group (as was before commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;) ), before ad_clear_agg(). The KASAN logs are as follows: [  767.617392] ================================================================== [  767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470 [  767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767 [  767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G           O 5.15.11 #15 [  767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT) [  767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler [  767.666468] Call trace: [  767.668930]  dump_backtrace+0x0/0x2d0 [  767.672625]  show_stack+0x24/0x30 [  767.675965]  dump_stack_lvl+0x68/0x84 [  767.679659]  print_add…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 143 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix use-after-free after 802.3ad slave unbind commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;), resolve case, when there is several aggregation groups in the same bond. bond_3ad_unbind_slave will invalidate (clear) aggregator when __agg_active_ports return zero. So, ad_clear_agg can be executed even, when num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for, previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave will not update slave ports list, because lag_ports==NULL. So, here we got slave ports, pointing to freed aggregator memory. Fix with checking actual number of ports in group (as was before commit 0622cab0341c (&amp;#34;bonding: fix 802.3ad aggregator reselection&amp;#34;) ), before ad_clear_agg(). The KASAN logs are as follows: [  767.617392] ================================================================== [  767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470 [  767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767 [  767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G           O 5.15.11 #15 [  767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT) [  767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler [  767.666468] Call trace: [  767.668930]  dump_backtrace+0x0/0x2d0 [  767.672625]  show_stack+0x24/0x30 [  767.675965]  dump_stack_lvl+0x68/0x84 [  767.679659]  print_add…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49667</guid>
    </item>
  </channel>
</rss>
