In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync roc_abort_sync() can deadlock with roc_work(). roc_work() holds dev->mt76.mutex, while cancel_work_sync() waits for roc_work() to finish. If the caller already owns the same mutex, both sides block and no progress is possible. This deadlock can occur during station removal when mt76_sta_state() -> mt76_sta_remove() -> mt7925_mac_sta_remove_link() -> mt7925_mac_link_sta_remove() -> mt7925_roc_abort_sync() invokes cancel_work_sync() while roc_work() is still running and holding dev->mt76.mutex. This avoids the mutex deadlock and preserves exactly-once work ownership.

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

  - In the Linux kernel, the following vulnerability has been resolved: tracing/histogram: Fix a potential     memory leak for kstrdup() kfree() is missing on an error path to free the memory allocated by kstrdup(): p     = param = kstrdup(data->params[i], GFP_KERNEL); So it is better to free it via kfree(p). (CVE-2022-48768)

  - In the Linux kernel, the following vulnerability has been resolved: can: af_can: fix NULL pointer     dereference in can_rx_register() It causes NULL pointer dereference when testing as following: (a) use     syscall(__NR_socket, 0x10ul, 3ul, 0) to create netlink socket. (b) use syscall(__NR_sendmsg, ...) to     create bond link device and vxcan link device, and bind vxcan device to bond device (can also use     ifenslave command to bind vxcan device to bond device). (c) use syscall(__NR_socket, 0x1dul, 3ul, 1) to     create CAN socket. (d) use syscall(__NR_bind, ...) to bind the bond device to CAN socket. The bond device     invokes the can-raw protocol registration interface to receive CAN packets. However, ml_priv is not     allocated to the dev, dev_rcv_lists is assigned to NULL in can_rx_register(). In this case, it will occur     the NULL pointer dereference issue. The following is the stack information: BUG: kernel NULL pointer     dereference, address: 0000000000000008 PGD 122a4067 P4D 122a4067 PUD 1223c067 PMD 0 Oops: 0000 [#1]     PREEMPT SMP RIP: 0010:can_rx_register+0x12d/0x1e0 Call Trace: <TASK> raw_enable_filters+0x8d/0x120     raw_enable_allfilters+0x3b/0x130 raw_bind+0x118/0x4f0 __sys_bind+0x163/0x1a0 __x64_sys_bind+0x1e/0x30     do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> (CVE-2022-49863)

  - In the Linux kernel, the following vulnerability has been resolved: net/tipc: fix slab-use-after-free Read     in tipc_aead_encrypt_done Syzbot reported a slab-use-after-free with the following call trace:
    ================================================================== BUG: KASAN: slab-use-after-free in     tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 Read of size 8 at addr ffff88807a733000 by task     kworker/1:0/25 Call Trace: kasan_report+0xd9/0x110 mm/kasan/report.c:601     tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 crypto_request_complete     include/crypto/algapi.h:266 aead_request_complete include/crypto/internal/aead.h:85     cryptd_aead_crypt+0x3b8/0x750 crypto/cryptd.c:772 crypto_request_complete include/crypto/algapi.h:266     cryptd_queue_worker+0x131/0x200 crypto/cryptd.c:181 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231     Allocated by task 8355: kzalloc_noprof include/linux/slab.h:778 tipc_crypto_start+0xcc/0x9e0     net/tipc/crypto.c:1466 tipc_init_net+0x2dd/0x430 net/tipc/core.c:72 ops_init+0xb9/0x650     net/core/net_namespace.c:139 setup_net+0x435/0xb40 net/core/net_namespace.c:343 copy_net_ns+0x2f0/0x670     net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110     unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228 ksys_unshare+0x419/0x970 kernel/fork.c:3323
    __do_sys_unshare kernel/fork.c:3394 Freed by task 63: kfree+0x12a/0x3b0 mm/slub.c:4557     tipc_crypto_stop+0x23c/0x500 net/tipc/crypto.c:1539 tipc_exit_net+0x8c/0x110 net/tipc/core.c:119     ops_exit_list+0xb0/0x180 net/core/net_namespace.c:173 cleanup_net+0x5b7/0xbf0 net/core/net_namespace.c:640     process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 After freed the tipc_crypto tx by delete namespace,     tipc_aead_encrypt_done may still visit it in cryptd_queue_worker workqueue. I reproduce this issue by: ip     netns add ns1 ip link add veth1 type veth peer name veth2 ip link set veth1 netns ns1 ip netns exec ns1     tipc bearer enable media eth dev veth1 ip netns exec ns1 tipc node set key this_is_a_master_key master ip     netns exec ns1 tipc bearer disable media eth dev veth1 ip netns del ns1 The key of reproduction is that,     simd_aead_encrypt is interrupted, leading to crypto_simd_usable() return false. Thus, the     cryptd_queue_worker is triggered, and the tipc_crypto tx will be visited. tipc_disc_timeout     tipc_bearer_xmit_skb tipc_crypto_xmit tipc_aead_encrypt crypto_aead_encrypt // encrypt() simd_aead_encrypt     // crypto_simd_usable() is false child = &ctx->cryptd_tfm->base; simd_aead_encrypt crypto_aead_encrypt //     encrypt() cryptd_aead_encrypt_enqueue cryptd_aead_enqueue cryptd_enqueue_request // trigger     cryptd_queue_worker queue_work_on(smp_processor_id(), cryptd_wq, &cpu_queue->work) Fix this by holding net     reference count before encrypt. (CVE-2025-38052)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: eir: Fix possible crashes     on eir_create_adv_data eir_create_adv_data may attempt to add EIR_FLAGS and EIR_TX_POWER without checking     if that would fit. (CVE-2025-38303)

  - In the Linux kernel, the following vulnerability has been resolved: gve: prevent ethtool ops after     shutdown A crash can occur if an ethtool operation is invoked after shutdown() is called. shutdown() is     invoked during system shutdown to stop DMA operations without performing expensive deallocations. It is     discouraged to unregister the netdev in this path, so the device may still be visible to userspace and     kernel helpers. In gve, shutdown() tears down most internal data structures. If an ethtool operation is     dispatched after shutdown(), it will dereference freed or NULL pointers, leading to a kernel panic. While     graceful shutdown normally quiesces userspace before invoking the reboot syscall, forced shutdowns (as     observed on GCP VMs) can still trigger this path. Fix by calling netif_device_detach() in shutdown(). This     marks the device as detached so the ethtool ioctl handler will skip dispatching operations to the driver.
    (CVE-2025-38735)

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:1788168285 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: tracing/histogram: Fix a potential     memory leak for kstrdup() kfree() is missing on an error path to free the memory allocated by kstrdup(): p     = param = kstrdup(data->params[i], GFP_KERNEL); So it is better to free it via kfree(p). (CVE-2022-48768)

  - In the Linux kernel, the following vulnerability has been resolved: can: af_can: fix NULL pointer     dereference in can_rx_register() It causes NULL pointer dereference when testing as following: (a) use     syscall(__NR_socket, 0x10ul, 3ul, 0) to create netlink socket. (b) use syscall(__NR_sendmsg, ...) to     create bond link device and vxcan link device, and bind vxcan device to bond device (can also use     ifenslave command to bind vxcan device to bond device). (c) use syscall(__NR_socket, 0x1dul, 3ul, 1) to     create CAN socket. (d) use syscall(__NR_bind, ...) to bind the bond device to CAN socket. The bond device     invokes the can-raw protocol registration interface to receive CAN packets. However, ml_priv is not     allocated to the dev, dev_rcv_lists is assigned to NULL in can_rx_register(). In this case, it will occur     the NULL pointer dereference issue. The following is the stack information: BUG: kernel NULL pointer     dereference, address: 0000000000000008 PGD 122a4067 P4D 122a4067 PUD 1223c067 PMD 0 Oops: 0000 [#1]     PREEMPT SMP RIP: 0010:can_rx_register+0x12d/0x1e0 Call Trace: <TASK> raw_enable_filters+0x8d/0x120     raw_enable_allfilters+0x3b/0x130 raw_bind+0x118/0x4f0 __sys_bind+0x163/0x1a0 __x64_sys_bind+0x1e/0x30     do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> (CVE-2022-49863)

  - In the Linux kernel, the following vulnerability has been resolved: net/tipc: fix slab-use-after-free Read     in tipc_aead_encrypt_done Syzbot reported a slab-use-after-free with the following call trace:
    ================================================================== BUG: KASAN: slab-use-after-free in     tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 Read of size 8 at addr ffff88807a733000 by task     kworker/1:0/25 Call Trace: kasan_report+0xd9/0x110 mm/kasan/report.c:601     tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 crypto_request_complete     include/crypto/algapi.h:266 aead_request_complete include/crypto/internal/aead.h:85     cryptd_aead_crypt+0x3b8/0x750 crypto/cryptd.c:772 crypto_request_complete include/crypto/algapi.h:266     cryptd_queue_worker+0x131/0x200 crypto/cryptd.c:181 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231     Allocated by task 8355: kzalloc_noprof include/linux/slab.h:778 tipc_crypto_start+0xcc/0x9e0     net/tipc/crypto.c:1466 tipc_init_net+0x2dd/0x430 net/tipc/core.c:72 ops_init+0xb9/0x650     net/core/net_namespace.c:139 setup_net+0x435/0xb40 net/core/net_namespace.c:343 copy_net_ns+0x2f0/0x670     net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110     unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228 ksys_unshare+0x419/0x970 kernel/fork.c:3323
    __do_sys_unshare kernel/fork.c:3394 Freed by task 63: kfree+0x12a/0x3b0 mm/slub.c:4557     tipc_crypto_stop+0x23c/0x500 net/tipc/crypto.c:1539 tipc_exit_net+0x8c/0x110 net/tipc/core.c:119     ops_exit_list+0xb0/0x180 net/core/net_namespace.c:173 cleanup_net+0x5b7/0xbf0 net/core/net_namespace.c:640     process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 After freed the tipc_crypto tx by delete namespace,     tipc_aead_encrypt_done may still visit it in cryptd_queue_worker workqueue. I reproduce this issue by: ip     netns add ns1 ip link add veth1 type veth peer name veth2 ip link set veth1 netns ns1 ip netns exec ns1     tipc bearer enable media eth dev veth1 ip netns exec ns1 tipc node set key this_is_a_master_key master ip     netns exec ns1 tipc bearer disable media eth dev veth1 ip netns del ns1 The key of reproduction is that,     simd_aead_encrypt is interrupted, leading to crypto_simd_usable() return false. Thus, the     cryptd_queue_worker is triggered, and the tipc_crypto tx will be visited. tipc_disc_timeout     tipc_bearer_xmit_skb tipc_crypto_xmit tipc_aead_encrypt crypto_aead_encrypt // encrypt() simd_aead_encrypt     // crypto_simd_usable() is false child = &ctx->cryptd_tfm->base; simd_aead_encrypt crypto_aead_encrypt //     encrypt() cryptd_aead_encrypt_enqueue cryptd_aead_enqueue cryptd_enqueue_request // trigger     cryptd_queue_worker queue_work_on(smp_processor_id(), cryptd_wq, &cpu_queue->work) Fix this by holding net     reference count before encrypt. (CVE-2025-38052)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: eir: Fix possible crashes     on eir_create_adv_data eir_create_adv_data may attempt to add EIR_FLAGS and EIR_TX_POWER without checking     if that would fit. (CVE-2025-38303)

  - In the Linux kernel, the following vulnerability has been resolved: gve: prevent ethtool ops after     shutdown A crash can occur if an ethtool operation is invoked after shutdown() is called. shutdown() is     invoked during system shutdown to stop DMA operations without performing expensive deallocations. It is     discouraged to unregister the netdev in this path, so the device may still be visible to userspace and     kernel helpers. In gve, shutdown() tears down most internal data structures. If an ethtool operation is     dispatched after shutdown(), it will dereference freed or NULL pointers, leading to a kernel panic. While     graceful shutdown normally quiesces userspace before invoking the reboot syscall, forced shutdowns (as     observed on GCP VMs) can still trigger this path. Fix by calling netif_device_detach() in shutdown(). This     marks the device as detached so the ethtool ioctl handler will skip dispatching operations to the driver.
    (CVE-2025-38735)

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.

  - wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync roc_abort_sync() can deadlock with     roc_work(). roc_work() holds dev->mt76.mutex, while cancel_work_sync() waits for roc_work() to finish. If     the caller already owns the same mutex, both sides block and no progress is possible. This deadlock can     occur during station removal when mt76_sta_state() -> mt76_sta_remove() -> mt7925_mac_sta_remove_link() ->     mt7925_mac_link_sta_remove() -> mt7925_roc_abort_sync() invokes cancel_work_sync() while roc_work() is     still running and holding dev->mt76.mutex. This avoids the mutex deadlock and preserves exactly-once work     ownership. (CVE-2026-53103)

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

ID	Name	Product	Family	Type	Severity
360902	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1788168285)	Nessus	Rocky Linux Local Security Checks	Local	high
360768	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1788168285)	Nessus	Alma Linux Local Security Checks	Local	high
343532	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (GCP) vulnerabilities (USN-8728-1)	Nessus	Ubuntu Local Security Checks	Local	high
340681	Ubuntu 24.04 LTS / 26.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (NVIDIA) vulnerabilities (USN-8663-1)	Nessus	Ubuntu Local Security Checks	Local	high
340045	Ubuntu 26.04 LTS : Linux kernel (NVIDIA BaseOS) vulnerabilities (USN-8664-1)	Nessus	Ubuntu Local Security Checks	Local	high
329305	openSUSE 16: cluster-md-kmp-64kb / cluster-md-kmp-azure / cluster-md-kmp-default / etc (openSUSE-SU-2026:21388-1)	Nessus	SuSE Local Security Checks	Local	high
322648	Linux Distros Unpatched Vulnerability : CVE-2026-53103	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-53103

medium

Tenable Plugins

high

high

high

high

high

high

medium