In the Linux kernel, the following vulnerability has been resolved: team: avoid NETDEV_CHANGEMTU event when unregistering slave syzbot is reporting unregister_netdevice: waiting for netdevsim0 to become free. Usage count = 3 ref_tracker: netdev@ffff88807dcf8618 has 1/2 users at __netdev_tracker_alloc include/linux/netdevice.h:4400 [inline] netdev_hold include/linux/netdevice.h:4429 [inline] inetdev_init+0x201/0x4e0 net/ipv4/devinet.c:286 inetdev_event+0x251/0x1610 net/ipv4/devinet.c:1600 notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85 call_netdevice_notifiers_mtu net/core/dev.c:2318 [inline] netif_set_mtu_ext+0x5aa/0x800 net/core/dev.c:9886 netif_set_mtu+0xd7/0x1b0 net/core/dev.c:9907 dev_set_mtu+0x126/0x260 net/core/dev_api.c:248 team_port_del+0xb07/0xcb0 drivers/net/team/team_core.c:1333 team_del_slave drivers/net/team/team_core.c:1936 [inline] team_device_event+0x207/0x5b0 drivers/net/team/team_core.c:2929 notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85 call_netdevice_notifiers_extack net/core/dev.c:2281 [inline] call_netdevice_notifiers net/core/dev.c:2295 [inline] __dev_change_net_namespace+0xcb7/0x2050 net/core/dev.c:12592 do_setlink+0x2ce/0x4590 net/core/rtnetlink.c:3060 rtnl_changelink net/core/rtnetlink.c:3776 [inline] __rtnl_newlink net/core/rtnetlink.c:3935 [inline] rtnl_newlink+0x15a9/0x1be0 net/core/rtnetlink.c:4072 rtnetlink_rcv_msg+0x7d5/0xbe0 net/core/rtnetlink.c:6958 netlink_rcv_skb+0x232/0x4b0 net/netlink/af_netlink.c:2550 netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline] netlink_unicast+0x80f/0x9b0 net/netlink/af_netlink.c:1344 netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1894 problem. Ido Schimmel found steps to reproduce ip link add name team1 type team ip link add name dummy1 mtu 1499 master team1 type dummy ip netns add ns1 ip link set dev dummy1 netns ns1 ip -n ns1 link del dev dummy1 and also found that the same issue was fixed in the bond driver in commit f51048c3e07b ("bonding: avoid NETDEV_CHANGEMTU event when unregistering slave"). Let's do similar thing for the team driver, with commit ad7c7b2172c3 ("net: hold netdev instance lock during sysfs operations") and commit 303a8487a657 ("net: s/__dev_set_mtu/__netif_set_mtu/") also applied.

The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1781344094 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: i2c: designware: use casting of u64 in     clock multiplication to avoid overflow In functions i2c_dw_scl_lcnt() and i2c_dw_scl_hcnt() may have     overflow by depending on the values of the given parameters including the ic_clk. For example in our use     case where ic_clk is larger than one million, multiplication of ic_clk * 4700 will result in 32 bit     overflow. Add cast of u64 to the calculation to avoid multiplication overflow, and use the corresponding     define for divide. (CVE-2022-49749)

  - In the Linux kernel, the following vulnerability has been resolved: kernel/irq/irqdomain.c: fix memory     leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it,     otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove()     instead which handles all of the logic at once. (CVE-2023-52936)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix null pointer dereference     in tracing_err_log_open() Fix an issue in function 'tracing_err_log_open'. The function doesn't call     'seq_open' if the file is opened only with write permissions, which results in 'file->private_data' being     left as null. If we then use 'lseek' on that opened file, 'seq_lseek' dereferences 'file->private_data' in     'mutex_lock(&m->lock)', resulting in a kernel panic. Writing to this node requires root privileges,     therefore this bug has very little security impact. Tracefs node: /sys/kernel/tracing/error_log Example     Kernel panic: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038 Call     trace: mutex_lock+0x30/0x110 seq_lseek+0x34/0xb8 __arm64_sys_lseek+0x6c/0xb8 invoke_syscall+0x58/0x13c     el0_svc_common+0xc4/0x10c do_el0_svc+0x24/0x98 el0_svc+0x24/0x88 el0t_64_sync_handler+0x84/0xe4     el0t_64_sync+0x1b4/0x1b8 Code: d503201f aa0803e0 aa1f03e1 aa0103e9 (c8e97d02) ---[ end trace     561d1b49c12cf8a5 ]--- Kernel panic - not syncing: Oops: Fatal exception (CVE-2023-53167)

  - In the Linux kernel, the following vulnerability has been resolved: irqchip: Fix refcount leak in     platform_irqchip_probe of_irq_find_parent() returns a node pointer with refcount incremented, We should     use of_node_put() on it when not needed anymore. Add missing of_node_put() to avoid refcount leak.
    (CVE-2023-53610)

  - In the Linux kernel, the following vulnerability has been resolved: uio_hv_generic: Fix kernel NULL     pointer dereference in hv_uio_rescind For primary VM Bus channels, primary_channel pointer is always NULL.
    This pointer is valid only for the secondary channels. Also, rescind callback is meant for primary     channels only. Fix NULL pointer dereference by retrieving the device_obj from the parent for the primary     channel. (CVE-2024-46739)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1781344094 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: i2c: designware: use casting of u64 in     clock multiplication to avoid overflow In functions i2c_dw_scl_lcnt() and i2c_dw_scl_hcnt() may have     overflow by depending on the values of the given parameters including the ic_clk. For example in our use     case where ic_clk is larger than one million, multiplication of ic_clk * 4700 will result in 32 bit     overflow. Add cast of u64 to the calculation to avoid multiplication overflow, and use the corresponding     define for divide. (CVE-2022-49749)

  - In the Linux kernel, the following vulnerability has been resolved: kernel/irq/irqdomain.c: fix memory     leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it,     otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove()     instead which handles all of the logic at once. (CVE-2023-52936)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix null pointer dereference     in tracing_err_log_open() Fix an issue in function 'tracing_err_log_open'. The function doesn't call     'seq_open' if the file is opened only with write permissions, which results in 'file->private_data' being     left as null. If we then use 'lseek' on that opened file, 'seq_lseek' dereferences 'file->private_data' in     'mutex_lock(&m->lock)', resulting in a kernel panic. Writing to this node requires root privileges,     therefore this bug has very little security impact. Tracefs node: /sys/kernel/tracing/error_log Example     Kernel panic: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038 Call     trace: mutex_lock+0x30/0x110 seq_lseek+0x34/0xb8 __arm64_sys_lseek+0x6c/0xb8 invoke_syscall+0x58/0x13c     el0_svc_common+0xc4/0x10c do_el0_svc+0x24/0x98 el0_svc+0x24/0x88 el0t_64_sync_handler+0x84/0xe4     el0t_64_sync+0x1b4/0x1b8 Code: d503201f aa0803e0 aa1f03e1 aa0103e9 (c8e97d02) ---[ end trace     561d1b49c12cf8a5 ]--- Kernel panic - not syncing: Oops: Fatal exception (CVE-2023-53167)

  - In the Linux kernel, the following vulnerability has been resolved: irqchip: Fix refcount leak in     platform_irqchip_probe of_irq_find_parent() returns a node pointer with refcount incremented, We should     use of_node_put() on it when not needed anymore. Add missing of_node_put() to avoid refcount leak.
    (CVE-2023-53610)

  - In the Linux kernel, the following vulnerability has been resolved: uio_hv_generic: Fix kernel NULL     pointer dereference in hv_uio_rescind For primary VM Bus channels, primary_channel pointer is always NULL.
    This pointer is valid only for the secondary channels. Also, rescind callback is meant for primary     channels only. Fix NULL pointer dereference by retrieving the device_obj from the parent for the primary     channel. (CVE-2024-46739)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1783791447 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot     reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED     indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but     device_register() was called In case of device_register() has been called we should call put_device() to     correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of     MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_     calling device_register(), because put_device() should be called even in case of device_register()     failure. (CVE-2021-47416)

  - An out-of-bounds read flaw was found in the Linux kernel's TeleTYpe subsystem. The issue occurs in how a     user triggers a race condition using ioctls TIOCSPTLCK and TIOCGPTPEER and TIOCSTI and TCXONC with leakage     of memory in the flush_to_ldisc function. This flaw allows a local user to crash the system or read     unauthorized random data from memory. (CVE-2022-1462)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling     printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print     failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2 ----
    ---- ---- lock(console_owner); lock(&port_lock_key); lock(&port->lock); lock(&port_lock_key);
    lock(&port->lock); lock(console_owner); As commit dbdda842fe96 (printk: Add console owner and waiter     logic to load balance console writes) said, such deadlock can be prevented by using printk_deferred() in     kmalloc() (which is invoked in the section guarded by the port->lock). But there are too many printk() on     the kmalloc() path, and kmalloc() can be called from anywhere, so changing printk() to printk_deferred()     is too complicated and inelegant. Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so     that printk() will not be called, and this deadlock problem can be avoided. Syzbot reported the following     lockdep error: ====================================================== WARNING: possible circular locking     dependency detected 5.4.143-00237-g08ccc19a-dirty #10 Not tainted
    ------------------------------------------------------ syz-executor.4/29420 is trying to acquire lock:
    ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752     [inline] ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470     kernel/printk/printk.c:2023 but task is already holding lock: ffff8880119c9158 (&port->lock){-.-.}-{2:2},     at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 which lock already depends on the new lock. the existing     dependency chain (in reverse order) is: -> #2 (&port->lock){-.-.}-{2:2}: __raw_spin_lock_irqsave     include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50     kernel/locking/spinlock.c:159 tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock);
    tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x530/0xa80     drivers/tty/serial/8250/8250_port.c:1767 serial8250_handle_irq.part.0+0x31f/0x3d0     drivers/tty/serial/8250/8250_port.c:1854 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827     [inline] <-- lock(&port_lock_key); serial8250_default_handle_irq+0xb2/0x220     drivers/tty/serial/8250/8250_port.c:1870 serial8250_interrupt+0xfd/0x200     drivers/tty/serial/8250/8250_core.c:126 __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156     [...] -> #1 (&port_lock_key){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110     [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159     serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 <-- lock(&port_lock_key);
    call_console_drivers kernel/printk/printk.c:1819 [inline] console_unlock+0x8cb/0xd00     kernel/printk/printk.c:2504 vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner);
    vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 printk+0xba/0xed kernel/printk/printk.c:2084     register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 univ8250_console_init+0x3a/0x46     drivers/tty/serial/8250/8250_core.c:681 console_init+0x49d/0x6d3 kernel/printk/printk.c:2915     start_kernel+0x5e9/0x879 init/main.c:713 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 ->     #0 (console_owner){....}-{0:0}: [...] lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734     console_trylock_spinning kernel/printk/printk.c:1773 ---truncated--- (CVE-2022-49441)

  - In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around     ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is     empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to     avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
    Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless     ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait())     made some ep_events_available() calls lockless and added single call under a lock, finally commit     e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available()     lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by     task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init     include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events     fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes     by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available     fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 ->     0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
    G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS     Google 01/01/2011 (CVE-2022-49443)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-098732 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    team: avoid NETDEV_CHANGEMTU event when unregistering slave

    syzbot is reporting

      unregister_netdevice: waiting for netdevsim0 to become free. Usage count = 3       ref_tracker: netdev@ffff88807dcf8618 has 1/2 users at
           __netdev_tracker_alloc include/linux/netdevice.h:4400 [inline]            netdev_hold include/linux/netdevice.h:4429 [inline]            inetdev_init+0x201/0x4e0 net/ipv4/devinet.c:286            inetdev_event+0x251/0x1610 net/ipv4/devinet.c:1600            notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85            call_netdevice_notifiers_mtu net/core/dev.c:2318 [inline]            netif_set_mtu_ext+0x5aa/0x800 net/core/dev.c:9886            netif_set_mtu+0xd7/0x1b0 net/core/dev.c:9907            dev_set_mtu+0x126/0x260 net/core/dev_api.c:248            team_port_del+0xb07/0xcb0 drivers/net/team/team_core.c:1333            team_del_slave drivers/net/team/team_core.c:1936 [inline]            team_device_event+0x207/0x5b0 drivers/net/team/team_core.c:2929            notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85            call_netdevice_notifiers_extack net/core/dev.c:2281 [inline]            call_netdevice_notifiers net/core/dev.c:2295 [inline]
           __dev_change_net_namespace+0xcb7/0x2050 net/core/dev.c:12592            do_setlink+0x2ce/0x4590 net/core/rtnetlink.c:3060            rtnl_changelink net/core/rtnetlink.c:3776 [inline]
           __rtnl_newlink net/core/rtnetlink.c:3935 [inline]            rtnl_newlink+0x15a9/0x1be0 net/core/rtnetlink.c:4072            rtnetlink_rcv_msg+0x7d5/0xbe0 net/core/rtnetlink.c:6958            netlink_rcv_skb+0x232/0x4b0 net/netlink/af_netlink.c:2550            netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]            netlink_unicast+0x80f/0x9b0 net/netlink/af_netlink.c:1344            netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1894

    problem. Ido Schimmel found steps to reproduce

      ip link add name team1 type team       ip link add name dummy1 mtu 1499 master team1 type dummy       ip netns add ns1       ip link set dev dummy1 netns ns1       ip -n ns1 link del dev dummy1

    and also found that the same issue was fixed in the bond driver in     commit f51048c3e07b (bonding: avoid NETDEV_CHANGEMTU event when     unregistering slave).

    Let's do similar thing for the team driver, with commit ad7c7b2172c3 (net:
    hold netdev instance lock during sysfs operations) and commit 303a8487a657     (net: s/__dev_set_mtu/__netif_set_mtu/) also applied.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-102098 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    team: avoid NETDEV_CHANGEMTU event when unregistering slave

    syzbot is reporting

      unregister_netdevice: waiting for netdevsim0 to become free. Usage count = 3       ref_tracker: netdev@ffff88807dcf8618 has 1/2 users at
           __netdev_tracker_alloc include/linux/netdevice.h:4400 [inline]            netdev_hold include/linux/netdevice.h:4429 [inline]            inetdev_init+0x201/0x4e0 net/ipv4/devinet.c:286            inetdev_event+0x251/0x1610 net/ipv4/devinet.c:1600            notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85            call_netdevice_notifiers_mtu net/core/dev.c:2318 [inline]            netif_set_mtu_ext+0x5aa/0x800 net/core/dev.c:9886            netif_set_mtu+0xd7/0x1b0 net/core/dev.c:9907            dev_set_mtu+0x126/0x260 net/core/dev_api.c:248            team_port_del+0xb07/0xcb0 drivers/net/team/team_core.c:1333            team_del_slave drivers/net/team/team_core.c:1936 [inline]            team_device_event+0x207/0x5b0 drivers/net/team/team_core.c:2929            notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85            call_netdevice_notifiers_extack net/core/dev.c:2281 [inline]            call_netdevice_notifiers net/core/dev.c:2295 [inline]
           __dev_change_net_namespace+0xcb7/0x2050 net/core/dev.c:12592            do_setlink+0x2ce/0x4590 net/core/rtnetlink.c:3060            rtnl_changelink net/core/rtnetlink.c:3776 [inline]
           __rtnl_newlink net/core/rtnetlink.c:3935 [inline]            rtnl_newlink+0x15a9/0x1be0 net/core/rtnetlink.c:4072            rtnetlink_rcv_msg+0x7d5/0xbe0 net/core/rtnetlink.c:6958            netlink_rcv_skb+0x232/0x4b0 net/netlink/af_netlink.c:2550            netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]            netlink_unicast+0x80f/0x9b0 net/netlink/af_netlink.c:1344            netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1894

    problem. Ido Schimmel found steps to reproduce

      ip link add name team1 type team       ip link add name dummy1 mtu 1499 master team1 type dummy       ip netns add ns1       ip link set dev dummy1 netns ns1       ip -n ns1 link del dev dummy1

    and also found that the same issue was fixed in the bond driver in     commit f51048c3e07b (bonding: avoid NETDEV_CHANGEMTU event when     unregistering slave).

    Let's do similar thing for the team driver, with commit ad7c7b2172c3 (net:
    hold netdev instance lock during sysfs operations) and commit 303a8487a657     (net: s/__dev_set_mtu/__netif_set_mtu/) also applied.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:2450-1 advisory.

    The SUSE Linux Enterprise 12 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2025-10263: arm64: Add workaround for Cortex-A76 erratum 1286807 (bsc#1266290).
    - CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).
    - CVE-2025-68822: Input: alps - fix use-after-free bugs caused by dev3_register_work (bsc#1256668).
    - CVE-2026-3150: bcache: fix cached_dev.sb_bio use-after-free and crash (bsc#1263169).
    - CVE-2026-23271: perf: Fix __perf_event_overflow() vs perf_remove_from_context() race (bsc#1260018).
    - CVE-2026-23279: wifi: mac80211: fix NULL pointer dereference in mesh_rx_csa_frame() (bsc#1260468).
    - CVE-2026-23303: smb: client: Don't log plaintext credentials in cifs_set_cifscreds (bsc#1260502).
    - CVE-2026-23367: wifi: radiotap: reject radiotap with unknown bits (bsc#1260731).
    - CVE-2026-23396: wifi: mac80211: fix NULL deref in mesh_matches_local() (bsc#1260729).
    - CVE-2026-23444: wifi: mac80211: always free skb on ieee80211_tx_prepare_skb() failure (bsc#1266307).
    - CVE-2026-23448: net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (bsc#1261750).
    - CVE-2026-31405: media: dvb-net: fix OOB access in ULE extension header tables (bsc#1261700).
    - CVE-2026-31415: ipv6: avoid overflows in ip6_datagram_send_ctl() (bsc#1262099).
    - CVE-2026-31421: net/sched: cls_fw: fix NULL pointer dereference on shared blocks (bsc#1262061).
    - CVE-2026-31447: ext4: reject mount if bigalloc with s_first_data_block != 0 (bsc#1262614).
    - CVE-2026-31452: ext4: convert inline data to extents when truncate exceeds inline size (bsc#1262620).
    - CVE-2026-31464: scsi: ibmvfc: Fix OOB access in ibmvfc_discover_targets_done() (bsc#1262656).
    - CVE-2026-31469: virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false       (bsc#1267816).
    - CVE-2026-31498: Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (bsc#1262751).
    - CVE-2026-31500: Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (bsc#1262993).
    - CVE-2026-31515: af_key: validate families in pfkey_send_migrate() (bsc#1262752).
    - CVE-2026-31516: xfrm: prevent policy_hthresh.work from racing with netns teardown (bsc#1262755).
    - CVE-2026-31532: can: af_can: export can_sock_destruct() (bsc#1262757).
    - CVE-2026-31540: drm/i915/gt: Check set_default_submission() before deferencing (bsc#1263011).
    - CVE-2026-31546: net: bonding: fix NULL deref in bond_debug_rlb_hash_show (bsc#1263006).
    - CVE-2026-31588: KVM: x86: Use scratch field in MMIO fragment to hold small write values (bsc#1263165).
    - CVE-2026-31590: KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION (bsc#1263152).
    - CVE-2026-31596: ocfs2: handle invalid dinode in ocfs2_group_extend (bsc#1263319).
    - CVE-2026-31629: nfc: llcp: add missing return after LLCP_CLOSED checks (bsc#1263790).
    - CVE-2026-31664: string.h: Introduce memset_after() for wiping trailing members/padding (bsc#1263578).
    - CVE-2026-31668: seg6: separate dst_cache for input and output paths in seg6 lwtunnel (bsc#1263140).
    - CVE-2026-31671: xfrm_user: fix info leak in build_report() (bsc#1263115).
    - CVE-2026-31673: af_unix: read UNIX_DIAG_VFS data under unix_state_lock (bsc#1263143).
    - CVE-2026-31674: netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check() (bsc#1263568).
    - CVE-2026-31678: openvswitch: defer tunnel netdev_put to RCU release (bsc#1263562).
    - CVE-2026-31759: usb: ulpi: fix double free in ulpi_register_interface() error path (bsc#1264076).
    - CVE-2026-31778: ALSA: caiaq: fix stack out-of-bounds read in init_card (bsc#1263923).
    - CVE-2026-43020: Bluetooth: MGMT: validate LTK enc_size on load (bsc#1264006).
    - CVE-2026-43024: netfilter: nf_tables: reject immediate NF_QUEUE verdict (bsc#1263930).
    - CVE-2026-43026: netfilter: ctnetlink: zero expect NAT fields when CTA_EXPECT_NAT absent (bsc#1263932).
    - CVE-2026-43028: netfilter: x_tables: ensure names are nul-terminated (bsc#1263934).
    - CVE-2026-43037: ip6_tunnel: clear skb2->cb in ip4ip6_err() (bsc#1263995).
    - CVE-2026-43038: ipv6: icmp: clear skb2->cb in ip6_err_gen_icmpv6_unreach() (bsc#1264097).
    - CVE-2026-43040: net: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to     prevent an info-       leak (bsc#1264091).
    - CVE-2026-43052: wifi: mac80211: check tdls flag in ieee80211_tdls_oper (bsc#1263945).
    - CVE-2026-43077: crypto: algif_aead - Fix minimum RX size check for decryption (bsc#1264470).
    - CVE-2026-43140: HID: magicmouse: Do not crash on missing msc->input (bsc#1264630).
    - CVE-2026-43158: xfs: fix freemap adjustments when adding xattrs to leaf blocks (bsc#1264595).
    - CVE-2026-43187: xfs: delete attr leaf freemap entries when empty (bsc#1264603).
    - CVE-2026-43198: tcp: fix potential race in tcp_v6_syn_recv_sock() (bsc#1264610).
    - CVE-2026-43206: drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (bsc#1264551).
    - CVE-2026-43234: team: avoid NETDEV_CHANGEMTU event when unregistering slave (bsc#1264409).
    - CVE-2026-43338: btrfs: reserve enough transaction items for qgroup ioctls (bsc#1264716).
    - CVE-2026-43339: ipv6: prevent possible UaF in addrconf_permanent_addr() (bsc#1264763).
    - CVE-2026-43359: btrfs: fix transaction abort on set received ioctl due to item overflow (bsc#1264719).
    - CVE-2026-43361: btrfs: fix transaction abort when snapshotting received subvolumes (bsc#1264722).
    - CVE-2026-43407: libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() (bsc#1265020).
    - CVE-2026-43413: scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1264671).
    - CVE-2026-43414: scsi: qla2xxx: Completely fix fcport double free (bsc#1264669).
    - CVE-2026-43499: rtmutex: Use waiter::task instead of current in remove_waiter() (bsc#1266001).
    - CVE-2026-43503: net: skbuff: propagate shared-frag marker through frag-transfer helpers (bsc#1265960).
    - CVE-2026-45835: Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_connection_cb() (bsc#1266411).
    - CVE-2026-45841: netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO (bsc#1266390).
    - CVE-2026-45842: slip: reject VJ receive packets on instances with no rstate array (bsc#1266400).
    - CVE-2026-45843: slip: bound decode() reads against the compressed packet length (bsc#1266395).
    - CVE-2026-45852: RDMA/rxe: Fix double free in rxe_srq_from_init (bsc#1266711).
    - CVE-2026-45870: SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths (bsc#1266704).
    - CVE-2026-45970: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (bsc#1267205).
    - CVE-2026-45983: nfsd: never defer requests during idmap lookup (bsc#1266697).
    - CVE-2026-46021: thermal: core: Fix thermal zone governor cleanup issues (bsc#1267220).
    - CVE-2026-46024: libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply() (bsc#1267218).
    - CVE-2026-46043: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv (bsc#1266901).
    - CVE-2026-46090: ALSA: aloop: Fix peer runtime UAF during format-change stop (bsc#1267531).
    - CVE-2026-46113: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (bsc#1266969).
    - CVE-2026-46116: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete (bsc#1267369).
    - CVE-2026-46150: fanotify: fix false positive on permission events (bsc#1267387).
    - CVE-2026-46157: ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger (bsc#1267726).
    - CVE-2026-46159: btrfs: fix btrfs_ioctl_space_info() slot_count TOCTOU which can lead to info-leak     (bsc#1267652).
    - CVE-2026-46160: btrfs: fix missing last_unlink_trans update when removing a directory (bsc#1267624).
    - CVE-2026-46169: hfsplus: fix uninit-value by validating catalog record size (bsc#1267713).
    - CVE-2026-46181: RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() (bsc#1266826).
    - CVE-2026-46243: smb: client: reject userspace cifs.spnego descriptions (bsc#1266238).
    - CVE-2026-46259: procfs: fix missing RCU protection when reading real_parent in do_task_stat()     (bsc#1267685).
    - CVE-2026-46273: ibmveth: Disable GSO for packets with small MSS (bsc#1267651).

    The following non security issues were fixed:

    - arm64: tlb: Allow XZR argument to TLBI ops (git-fixes).
    - arm64: tlb: Optimize ARM64_WORKAROUND_REPEAT_TLBI (git-fixes).
    - bcache: fix uninitialized closure object (git-fixes).
    - check-for-config-changes: Exclude CC_MS_EXTENSIONS.
    - check-for-config-changes: Exclude HAVE_CFI_ICALL_NORMALIZE_INTEGERS{,_RUSTC}.
    - kvm/svm: PKU not currently supported (bsc#1263887).
    - KVM: x86: Handle PKU CPUID adjustment in VMX code (bsc#1263887).
    - mkspec: Add signature to source list only when it exists.
    - net/sched: cls_fw: fix NULL dereference of 'old' filters before change() (git-fixes).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1702 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    audit: add fchmodat2() to change attributes class (CVE-2025-71239)

    In the Linux kernel, the following vulnerability has been resolved:

    fs: ntfs3: fix infinite loop in attr_load_runs_range on inconsistent metadata (CVE-2025-71265)

    In the Linux kernel, the following vulnerability has been resolved:

    fs: ntfs3: check return value of indx_find to avoid infinite loop (CVE-2025-71266)

    In the Linux kernel, the following vulnerability has been resolved:

    fs: ntfs3: fix infinite loop triggered by zero-sized ATTR_LIST (CVE-2025-71267)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/buffer: add alert in try_to_free_buffers() for folios without buffers (CVE-2025-71295)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/tests: shmem: Hold reservation lock around purge (CVE-2025-71296)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/tests: shmem: Hold reservation lock around madvise (CVE-2025-71298)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/tests: shmem: Hold reservation lock around vmap/vunmap (CVE-2025-71301)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/display/dp_mst: Add protection against 0 vcpi (CVE-2025-71305)

    In the Linux kernel, the following vulnerability has been resolved:

    espintcp: Fix race condition in espintcp_close() (CVE-2026-23239)

    In the Linux kernel, the following vulnerability has been resolved:

    tls: Fix race condition in tls_sw_cancel_work_tx() (CVE-2026-23240)

    In the Linux kernel, the following vulnerability has been resolved:

    audit: add missing syscalls to read class (CVE-2026-23241)

    In the Linux kernel, the following vulnerability has been resolved:

    xfs: check for deleted cursors when revalidating two btrees (CVE-2026-23249)

    In the Linux kernel, the following vulnerability has been resolved:

    cifs: some missing initializations on replay (CVE-2026-31693)

    In the Linux kernel, the following vulnerability has been resolved:

    io_uring/zcrx: fix user_ref race between scrub and refill paths (CVE-2026-43121)

    In the Linux kernel, the following vulnerability has been resolved:

    fbcon: check return value of con2fb_acquire_newinfo() (CVE-2026-43123)

    In the Linux kernel, the following vulnerability has been resolved:

    pstore: ram_core: fix incorrect success return when vmap() fails (CVE-2026-43124)

    In the Linux kernel, the following vulnerability has been resolved:

    ntfs3: fix circular locking dependency in run_unpack_ex (CVE-2026-43127)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/umem: Fix double dma_buf_unpin in failure path (CVE-2026-43128)

    In the Linux kernel, the following vulnerability has been resolved:

    ima: verify the previous kernel's IMA buffer lies in addressable RAM (CVE-2026-43129)

    In the Linux kernel, the following vulnerability has been resolved:

    iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode (CVE-2026-43130)

    In the Linux kernel, the following vulnerability has been resolved:

    dm-verity: correctly handle dm_bufio_client_create() failure (CVE-2026-43132)

    In the Linux kernel, the following vulnerability has been resolved:

    KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (CVE-2026-43133)

    In the Linux kernel, the following vulnerability has been resolved:

    xfrm6: fix uninitialized saddr in xfrm6_get_saddr() (CVE-2026-43139)

    In the Linux kernel, the following vulnerability has been resolved:

    mfd: core: Add locking around 'mfd_of_node_list' (CVE-2026-43143)

    In the Linux kernel, the following vulnerability has been resolved:

    Revert PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (CVE-2026-43147)

    In the Linux kernel, the following vulnerability has been resolved:

    perf/arm-cmn: Reject unsupported hardware configurations (CVE-2026-43150)

    In the Linux kernel, the following vulnerability has been resolved:

    HID: hid-pl: handle probe errors (CVE-2026-43152)

    In the Linux kernel, the following vulnerability has been resolved:

    xfs: remove xfs_attr_leaf_hasname (CVE-2026-43153)

    In the Linux kernel, the following vulnerability has been resolved:

    erofs: fix incorrect early exits in volume label handling (CVE-2026-43154)

    In the Linux kernel, the following vulnerability has been resolved:

    xfs: fix freemap adjustments when adding xattrs to leaf blocks (CVE-2026-43158)

    In the Linux kernel, the following vulnerability has been resolved:

    md/bitmap: fix GPF in write_page caused by resize race (CVE-2026-43163)

    In the Linux kernel, the following vulnerability has been resolved:

    udplite: Fix null-ptr-deref in __udp_enqueue_schedule_skb(). (CVE-2026-43164)

    In the Linux kernel, the following vulnerability has been resolved:

    erofs: fix interlaced plain identification for encoded extents (CVE-2026-43166)

    In the Linux kernel, the following vulnerability has been resolved:

    xfrm: always flush state and policy upon NETDEV_UNREGISTER event (CVE-2026-43167)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/buddy: Prevent BUG_ON by validating rounded allocation (CVE-2026-43169)

    In the Linux kernel, the following vulnerability has been resolved:

    EFI/CPER: don't dump the entire memory region (CVE-2026-43171)

    In the Linux kernel, the following vulnerability has been resolved:

    erofs: fix incorrect early exits for invalid metabox-enabled images (CVE-2026-43179)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data() (CVE-2026-43186)

    In the Linux kernel, the following vulnerability has been resolved:

    xfs: delete attr leaf freemap entries when empty (CVE-2026-43187)

    In the Linux kernel, the following vulnerability has been resolved:

    ceph: do not propagate page array emplacement errors as batch errors (CVE-2026-43188)

    In the Linux kernel, the following vulnerability has been resolved:

    media: v4l2-async: Fix error handling on steps after finding a match (CVE-2026-43189)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: xt_tcpmss: check remaining length before reading optlen (CVE-2026-43190)

    In the Linux kernel, the following vulnerability has been resolved:

    net: consume xmit errors of GSO frames (CVE-2026-43194)

    In the Linux kernel, the following vulnerability has been resolved:

    tcp: fix potential race in tcp_v6_syn_recv_sock() (CVE-2026-43198)

    In the Linux kernel, the following vulnerability has been resolved:

    net/mlx5e: Fix scheduling while atomic in IPsec MAC address query (CVE-2026-43199)

    In the Linux kernel, the following vulnerability has been resolved:

    APEI/GHES: ARM processor Error: don't go past allocated memory (CVE-2026-43201)

    In the Linux kernel, the following vulnerability has been resolved:

    net: do not pass flow_id to set_rps_cpu() (CVE-2026-43208)

    In the Linux kernel, the following vulnerability has been resolved:

    tracing: ring-buffer: Fix to check event length before using (CVE-2026-43210)

    In the Linux kernel, the following vulnerability has been resolved:

    PCI: Fix pci_slot_trylock() error handling (CVE-2026-43211)

    In the Linux kernel, the following vulnerability has been resolved:

    KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() (CVE-2026-43214)

    In the Linux kernel, the following vulnerability has been resolved:

    cifs: Fix locking usage for tcon fields (CVE-2026-43215)

    In the Linux kernel, the following vulnerability has been resolved:

    net: Drop the lock in skb_may_tx_timestamp() (CVE-2026-43216)

    In the Linux kernel, the following vulnerability has been resolved:

    io_uring/zcrx: fix sgtable leak on mapping failures (CVE-2026-43224)

    In the Linux kernel, the following vulnerability has been resolved:

    net/rds: No shortcut out of RDS_CONN_ERROR (CVE-2026-43226)

    In the Linux kernel, the following vulnerability has been resolved:

    net/rds: Clear reconnect pending bit (CVE-2026-43230)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (CVE-2026-43233)

    In the Linux kernel, the following vulnerability has been resolved:

    team: avoid NETDEV_CHANGEMTU event when unregistering slave (CVE-2026-43234)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: act_skbedit: fix divide-by-zero in tcf_skbedit_hash() (CVE-2026-43238)

    In the Linux kernel, the following vulnerability has been resolved:

    smb: client: prevent races in ->query_interfaces() (CVE-2026-43239)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/kexec: add a sanity check on previous kernel's ima kexec buffer (CVE-2026-43240)

    In the Linux kernel, the following vulnerability has been resolved:

    kcm: fix zero-frag skb in frag_list on partial sendmsg error (CVE-2026-43244)

    In the Linux kernel, the following vulnerability has been resolved:

    ntfs: ->d_compare() must not block (CVE-2026-43245)

    In the Linux kernel, the following vulnerability has been resolved:

    mptcp: pm: in-kernel: always set ID as avail when rm endp (CVE-2026-43252)

    In the Linux kernel, the following vulnerability has been resolved:

    iommu/amd: move wait_on_sem() out of spinlock (CVE-2026-43253)

    In the Linux kernel, the following vulnerability has been resolved:

    ovpn: tcp - fix packet extraction from stream (CVE-2026-43254)

    In the Linux kernel, the following vulnerability has been resolved:

    alpha: fix user-space corruption during memory compaction (CVE-2026-43258)

    In the Linux kernel, the following vulnerability has been resolved:

    arm64: Add support for TSV110 Spectre-BHB mitigation (CVE-2026-43261)

    In the Linux kernel, the following vulnerability has been resolved:

    EFI/CPER: don't go past the ARM processor CPER record buffer (CVE-2026-43266)

    In the Linux kernel, the following vulnerability has been resolved:

    ring-buffer: Fix possible dereference of uninitialized pointer (CVE-2026-43272)

    In the Linux kernel, the following vulnerability has been resolved:

    ceph: supply snapshot context in ceph_zero_partial_object() (CVE-2026-43273)

    In the Linux kernel, the following vulnerability has been resolved:

    APEI/GHES: ensure that won't go past CPER allocated record (CVE-2026-43277)

    In the Linux kernel, the following vulnerability has been resolved:

    dm: clear cloned request bio pointer when last clone bio completes (CVE-2026-43278)

    In the Linux kernel, the following vulnerability has been resolved:

    mailbox: Prevent out-of-bounds access in fw_mbox_index_xlate() (CVE-2026-43281)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/slab: do not access current->mems_allowed_seq if !allow_spin (CVE-2026-43285)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/hugetlb: restore failed global reservations to subpool (CVE-2026-43286)

    In the Linux kernel, the following vulnerability has been resolved:

    drm: Account property blob allocations to memcg (CVE-2026-43287)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: move ext4_percpu_param_init() before ext4_mb_init() (CVE-2026-43288)

    In the Linux kernel, the following vulnerability has been resolved:

    kexec: derive purgatory entry from symbol (CVE-2026-43289)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/vmalloc: prevent RCU stalls in kasan_release_vmalloc_node (CVE-2026-43292)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/page_alloc: clear page->private in free_pages_prepare() (CVE-2026-43303)

    In the Linux kernel, the following vulnerability has been resolved:

    libceph: define and enforce CEPH_MAX_KEY_LEN (CVE-2026-43304)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: crypto: Use the correct destructor kfunc type (CVE-2026-43306)

    In the Linux kernel, the following vulnerability has been resolved:

    md raid: fix hang when stopping arrays with metadata through dm-raid (CVE-2026-43309)

    In the Linux kernel, the following vulnerability has been resolved:

    ACPI: processor: Fix NULL-pointer dereference in acpi_processor_errata_piix4() (CVE-2026-43313)

    In the Linux kernel, the following vulnerability has been resolved:

    dm: remove fake timeout to avoid leak request (CVE-2026-43314)

    In the Linux kernel, the following vulnerability has been resolved:

    KVM: nSVM: Remove a user-triggerable WARN on nested_svm_load_cr3() succeeding (CVE-2026-43315)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Properly mark live registers for indirect jumps (CVE-2026-43321)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - team: avoid NETDEV_CHANGEMTU event when unregistering slave syzbot is reporting unregister_netdevice:
    waiting for netdevsim0 to become free. Usage count = 3 ref_tracker: netdev@ffff88807dcf8618 has 1/2 users     at __netdev_tracker_alloc include/linux/netdevice.h:4400 [inline] netdev_hold     include/linux/netdevice.h:4429 [inline] inetdev_init+0x201/0x4e0 net/ipv4/devinet.c:286     inetdev_event+0x251/0x1610 net/ipv4/devinet.c:1600 notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85     call_netdevice_notifiers_mtu net/core/dev.c:2318 [inline] netif_set_mtu_ext+0x5aa/0x800     net/core/dev.c:9886 netif_set_mtu+0xd7/0x1b0 net/core/dev.c:9907 dev_set_mtu+0x126/0x260     net/core/dev_api.c:248 team_port_del+0xb07/0xcb0 drivers/net/team/team_core.c:1333 team_del_slave     drivers/net/team/team_core.c:1936 [inline] team_device_event+0x207/0x5b0 drivers/net/team/team_core.c:2929     notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85 call_netdevice_notifiers_extack net/core/dev.c:2281     [inline] call_netdevice_notifiers net/core/dev.c:2295 [inline] __dev_change_net_namespace+0xcb7/0x2050     net/core/dev.c:12592 do_setlink+0x2ce/0x4590 net/core/rtnetlink.c:3060 rtnl_changelink     net/core/rtnetlink.c:3776 [inline] __rtnl_newlink net/core/rtnetlink.c:3935 [inline]     rtnl_newlink+0x15a9/0x1be0 net/core/rtnetlink.c:4072 rtnetlink_rcv_msg+0x7d5/0xbe0     net/core/rtnetlink.c:6958 netlink_rcv_skb+0x232/0x4b0 net/netlink/af_netlink.c:2550 netlink_unicast_kernel     net/netlink/af_netlink.c:1318 [inline] netlink_unicast+0x80f/0x9b0 net/netlink/af_netlink.c:1344     netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1894 problem. Ido Schimmel found steps to reproduce     ip link add name team1 type team ip link add name dummy1 mtu 1499 master team1 type dummy ip netns add ns1     ip link set dev dummy1 netns ns1 ip -n ns1 link del dev dummy1 and also found that the same issue was     fixed in the bond driver in commit f51048c3e07b (bonding: avoid NETDEV_CHANGEMTU event when unregistering     slave). Let's do similar thing for the team driver, with commit ad7c7b2172c3 (net: hold netdev instance     lock during sysfs operations) and commit 303a8487a657 (net: s/__dev_set_mtu/__netif_set_mtu/) also     applied. (CVE-2026-43234)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
360843	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1781344094)	Nessus	Rocky Linux Local Security Checks	Local	high
360739	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1781344094)	Nessus	Alma Linux Local Security Checks	Local	high
352871	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783791447)	Nessus	Alma Linux Local Security Checks	Local	low
340501	Unity Linux 20.1050a Security Update: kernel (UTSA-2026-098732)	Nessus	Unity Linux Local Security Checks	Local	medium
338539	Unity Linux 20.1050e Security Update: kernel (UTSA-2026-102098)	Nessus	Unity Linux Local Security Checks	Local	medium
323086	SUSE SLED15 / SLES15 : Security update for the Linux Kernel (SUSE-SU-2026:2482-1)	Nessus	SuSE Local Security Checks	Local	high
321690	SUSE SLES12 Security Update : kernel (SUSE-SU-2026:2450-1)	Nessus	SuSE Local Security Checks	Local	medium
320429	openSUSE 16 Security Update : kernel (openSUSE-SU-2026:20912-1)	Nessus	SuSE Local Security Checks	Local	medium
315658	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1702)	Nessus	Amazon Linux Local Security Checks	Local	high
312701	Linux Distros Unpatched Vulnerability : CVE-2026-43234	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-43234

medium

Tenable Plugins

high

high

low

medium

medium

high

medium

medium

high

medium