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

  - In the Linux kernel, the following vulnerability has been resolved: net: hns3: add vlan list lock to     protect vlan list When adding port base VLAN, vf VLAN need to remove from HW and modify the vlan state in     vf VLAN list as false. If the periodicity task is freeing the same node, it may cause use after free     error. This patch adds a vlan list lock to protect the vlan list. (CVE-2022-49182)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix reading strings from     synthetic events The follow commands caused a crash: # cd /sys/kernel/tracing # echo 's:open char file[]'     > dynamic_events # echo 'hist:keys=common_pid:file=filename:onchange($file).trace(open,$file)' >     events/syscalls/sys_enter_openat/trigger' # echo 1 > events/synthetic/open/enable BOOM! The problem is     that the synthetic event field char file[] will read the value given to it as a string without any     memory checks to make sure the address is valid. The above example will pass in the user space address and     the sythetic event code will happily call strlen() on it and then strscpy() where either one will cause an     oops when accessing user space addresses. Use the helper functions from trace_kprobe and trace_eprobe that     can read strings safely (and actually succeed when the address is from user space and the memory is mapped     in). Now the above can show: packagekitd-1721 [000] ...2. 104.597170: open:
    file=/usr/lib/rpm/fileattrs/cmake.attr in:imjournal-978 [006] ...2. 104.599642: open:
    file=/var/lib/rsyslog/imjournal.state.tmp packagekitd-1721 [000] ...2. 104.626308: open:
    file=/usr/lib/rpm/fileattrs/debuginfo.attr (CVE-2022-50255)

  - In the Linux kernel, the following vulnerability has been resolved: ipc: fix memleak if msg_init_ns failed     in create_ipc_ns Percpu memory allocation may failed during create_ipc_ns however this fail is not handled     properly since ipc sysctls and mq sysctls is not released properly. Fix this by release these two resource     when failure. Here is the kmemleak stack when percpu failed: unreferenced object 0xffff88819de2a600 (size     512): comm shmem_2nstest, pid 120711, jiffies 4300542254 hex dump (first 32 bytes): 60 aa 9d 84 ff ff ff     ff fc 18 48 b2 84 88 ff ff `.........H..... 04 00 00 00 a4 01 00 00 20 e4 56 81 ff ff ff ff ........
    .V..... backtrace (crc be7cba35): [<ffffffff81b43f83>] __kmalloc_node_track_caller_noprof+0x333/0x420     [<ffffffff81a52e56>] kmemdup_noprof+0x26/0x50 [<ffffffff821b2f37>] setup_mq_sysctls+0x57/0x1d0     [<ffffffff821b29cc>] copy_ipcs+0x29c/0x3b0 [<ffffffff815d6a10>] create_new_namespaces+0x1d0/0x920     [<ffffffff815d7449>] copy_namespaces+0x2e9/0x3e0 [<ffffffff815458f3>] copy_process+0x29f3/0x7ff0     [<ffffffff8154b080>] kernel_clone+0xc0/0x650 [<ffffffff8154b6b1>] __do_sys_clone+0xa1/0xe0     [<ffffffff843df8ff>] do_syscall_64+0xbf/0x1c0 [<ffffffff846000b0>]     entry_SYSCALL_64_after_hwframe+0x4b/0x53 (CVE-2024-53175)

  - In the Linux kernel, the following vulnerability has been resolved: net/mlx5: HWS, change error flow on     matcher disconnect Currently, when firmware failure occurs during matcher disconnect flow, the error flow     of the function reconnects the matcher back and returns an error, which continues running the calling     function and eventually frees the matcher that is being disconnected. This leads to a case where we have a     freed matcher on the matchers list, which in turn leads to use-after-free and eventual crash. This patch     fixes that by not trying to reconnect the matcher back when some FW command fails during disconnect. Note     that we're dealing here with FW error. We can't overcome this problem. This might lead to bad steering     state (e.g. wrong connection between matchers), and will also lead to resource leakage, as it is the case     with any other error handling during resource destruction. However, the goal here is to allow the driver     to continue and not crash the machine with use-after-free error. (CVE-2025-21751)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Avoid memory leak while     enabling statistics Driver uses monitor destination rings for extended statistics mode and standalone     monitor mode. In extended statistics mode, TLVs are parsed from the buffer received from the monitor     destination ring and assigned to the ppdu_info structure to update per-packet statistics. In standalone     monitor mode, along with per-packet statistics, the packet data (payload) is captured, and the driver     updates per MSDU to mac80211. When the AP interface is enabled, only extended statistics mode is     activated. As part of enabling monitor rings for collecting statistics, the driver subscribes to     HAL_RX_MPDU_START TLV in the filter configuration. This TLV is received from the monitor destination ring,     and kzalloc for the mon_mpdu object occurs, which is not freed, leading to a memory leak. The kzalloc for     the mon_mpdu object is only required while enabling the standalone monitor interface. This causes a memory     leak while enabling extended statistics mode in the driver. Fix this memory leak by removing the kzalloc     for the mon_mpdu object in the HAL_RX_MPDU_START TLV handling. Additionally, remove the standalone monitor     mode handlings in the HAL_MON_BUF_ADDR and HAL_RX_MSDU_END TLVs. These TLV tags will be handled properly     when enabling standalone monitor mode in the future. Tested-on: QCN9274 hw2.0 PCI     WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1 Tested-on: WCN7850 hw2.0 PCI     WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 (CVE-2025-37743)

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.

  - net/mlx5e: xsk: Fix unlocked writing to ICOSQ During napi poll, when the affinity changes and there's     still XSK work to be done, we trigger an ICOSQ interrupt on the new CPU. However, this triggering on the     ICOSQ is done unprotected. There are 2 such races: A) mlx5e_trigger_irq() is called while     mlx5e_xsk_alloc_rx_mpwqe() is running from a different CPU due to affinity change. This can happen because     IRQ triggering is done after napi_complete_done(). At this point the NAPI can be scheduled on a different     CPU. Like this: CPU A (old affinity, NAPI tail) CPU B (new affinity, fresh NAPI)
    ------------------------------- -------------------------------- napi_complete_done() clears SCHED     mlx5e_cq_arm(...) napi_schedule_prep() sets SCHED mlx5e_napi_poll() mlx5e_xsk_alloc_rx_mpwqe()     mlx5e_icosq_sync_lock() // noop memcpy 640 B UMR body advance sq->pc by 10 mlx5e_trigger_irq(&c->icosq)     wqe_info[pi] = {NOP, 1} mlx5e_post_nop() advances sq->pc B) mlx5e_trigger_irq() is called on the ICOSQ     when mlx5e_trigger_napi_icosq() is running. The obvious fix would be to lock the ICOSQ. But ICOSQ has an     optimized locking scheme that doesn't work for this scenario. Kick the async ICOSQ instead which is always     locked. This issue was noticed in the wild with the following splat: netdevice: ge-0-0-1: Bad OP in ICOSQ     CQE: 0xd WARNING: drivers/net/ethernet/mellanox/mlx5/core/en_rx.c:826 [...] [...] Call Trace: <IRQ>     mlx5e_napi_poll+0x11d/0x7f0 [mlx5_core] __napi_poll+0x30/0x200 ? skb_defer_free_flush+0x9c/0xc0     net_rx_action+0x2fe/0x3f0 handle_softirqs+0xd8/0x340 __irq_exit_rcu+0xbc/0xe0 common_interrupt+0x85/0xa0     </IRQ> <TASK> asm_common_interrupt+0x26/0x40 [...] ---[ end trace 0000000000000000 ]--- mlx5_core     0000:08:00.0 ge-0-0-1: Error cqe on cqn 0x548, ci 0x2022, qn 0x8f4, opcode 0xd, syndrome 0x2, vendor     syndrome 0x68 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000010: 00 00 00 00 00 00 00 00     00 00 00 00 00 00 00 00 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000030: 00 00 00 00 01     00 68 02 01 00 08 f4 de 14 59 d2 WQE DUMP: WQ size 16384 WQ cur size 0, WQE index 0x1e14, len: 64     00000000: 00 00 00 01 d9 ed 80 02 00 00 00 01 d9 ed 90 02 00000010: 00 00 00 01 d9 ed a0 02 00 00 00 01 d9     ed b0 02 00000020: 00 00 00 01 d9 ed c0 02 00 00 00 01 d9 ed d0 02 00000030: 00 00 00 01 d9 ed e0 02 00 00     00 01 d9 ed f0 02 mlx5_core 0000:08:00.0 ge-0-0-1: Error cqe on cqn 0x548, ci 0x2023, qn 0x8f4, opcode     0xd, syndrome 0x5, vendor syndrome 0xf9 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00     00 00 00 00000030: 00 00 00 00 01 00 f9 05 01 00 08 f4 de 15 cf d2 (CVE-2026-64210)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
364837	EulerOS 2.0 SP11 : kernel (EulerOS-SA-2026-4241)	Nessus	Huawei Local Security Checks	2026/10/12	2026/10/13	high
352273	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1789986443)	Nessus	Rocky Linux Local Security Checks	2026/9/30	2026/9/30	high
351155	Debian dsa-6528 : ata-modules-6.12.111+deb13-armmp-di - security update	Nessus	Debian Local Security Checks	2026/9/29	2026/9/29	high
362907	Debian dla-4817 : ata-modules-6.12.107+deb12-armmp-di - security update	Nessus	Debian Local Security Checks	2026/10/4	2026/10/4	high
365220	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2026-3197)	Nessus	Amazon Linux Local Security Checks	2026/10/12	2026/10/19	medium
364137	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-500374)	Nessus	Oracle Linux Local Security Checks	2026/10/8	2026/10/8	high
366742	SUSE SLED15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:4706-1)	Nessus	SuSE Local Security Checks	2026/10/17	2026/10/17	high
366919	Debian dla-4841 : ata-modules-6.1.0-53-armmp-di - security update	Nessus	Debian Local Security Checks	2026/10/17	2026/10/17	high
364821	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-4057)	Nessus	Huawei Local Security Checks	2026/10/12	2026/10/13	high
364867	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-4148)	Nessus	Huawei Local Security Checks	2026/10/12	2026/10/13	high
340681	Ubuntu 24.04 LTS / 26.04 LTS : Linux kernel (NVIDIA) vulnerabilities (USN-8663-1)	Nessus	Ubuntu Local Security Checks	2026/8/26	2026/10/14	high
329682	Linux Distros Unpatched Vulnerability : CVE-2026-64210	Nessus	Misc.	2026/7/25	2026/10/13	high
350138	openSUSE 16: cluster-md-kmp-64kb / cluster-md-kmp-azure / cluster-md-kmp-default / etc (openSUSE-SU-2026:21910-1)	Nessus	SuSE Local Security Checks	2026/9/25	2026/9/28	high
343532	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (GCP) vulnerabilities (USN-8728-1)	Nessus	Ubuntu Local Security Checks	2026/9/7	2026/9/24	high

检测

插件搜索

high

high

high

high

medium

high

high

high

high

high

high

high

high

high