Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - 已修复 Linux 内核中的下列漏洞：Bluetooth: hci_conn: Fix memory leaks When hci_cmd_sync_queue() failed in hci_le_terminate_big() or hci_le_big_terminate(), the memory pointed by variable d is not freed, which will cause memory leak. Add release process to error path.
    (CVE-2023-53018)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

远程 Redhat Enterprise Linux 9 主机上安装的程序包受到 RHSA-2024:2394 公告中提及的多个漏洞影响。

  - 内核：蓝牙 BR/EDR PIN 配对程序容易遭受假冒攻击 (CVE-2020-26555)

  - 内核：memcg 未限制 POSIX 文件锁定的数量，可导致内存耗尽 (CVE-2022-0480)

  - 内核：vmwgfx：vmw_cmd_dx_define_query 中存在空指针取消引用 (CVE-2022-38096)

  - 内核：net/bluetooth/l2cap_core.c 中的 l2cap_config_req() 包含整数溢出漏洞 (CVE-2022-45934)

  - 内核：由于存在争用条件，drivers/tty/vt/vc_screen.c 中的 vcs_read 包含释放后使用漏洞 (CVE-2023-3567)

  - 内核：cxgb4：ch_flower_stats_cb() 中的释放后使用漏洞 (CVE-2023-4133)

  - 内核：netfilter：nf_tables：nf_tables_newtable() 中的越界访问漏洞 (CVE-2023-6040)

  - 内核：NVMe：nvmet_ctrl_find_get 中因越界读取导致的信息泄漏问题 (CVE-2023-6121)

  - 内核：scatterwalk_copychunks 中的本地 DoS 漏洞 (CVE-2023-6176)

  - 内核：GC 删除 SKB 会与 unix_stream_read_generic() 发生争用，导致 UAF (CVE-2023-6531)

  - 内核：GSM 多路复用争用条件导致权限升级 (CVE-2023-6546)

  - 内核：nft_dynset_init() 中的空指针取消引用漏洞 (CVE-2023-6622)

  - 内核：lib/idr.c 中的 ida_free 包含空指针取消引用漏洞 (CVE-2023-6915)

  - 内核：由于 perf_event 的 read_size 溢出，导致 perf_read_group() 中发生越界写入 (CVE-2023-6931)

  - 内核：IPv4 IGMP 中的释放后使用 (CVE-2023-6932)

  - 内核：蓝牙转发和未来保密攻击与防御 (CVE-2023-24023)

  - 内核：irdma：访问控制不当 (CVE-2023-25775)

  - Kernel：蓝牙子系统的 hci_conn_cleanup 中包含双重释放漏洞 (CVE-2023-28464)

  - 内核：蓝牙：HCI：net/bluetooth/hci_sync.c 中的全局越界访问漏洞 (CVE-2023-28866)

  - 内核：在 hci_uart_tty_ioctl 中，HCIUARTSETPROTO 和 HCIUARTGETPROTO 之间存在竞争条件 (CVE-2023-31083)

  - 内核：usb：read_descriptors 中的越界读取漏洞 (CVE-2023-37453)

  - 内核：netfilter：nftables nf_osf_match_one() 中的越界读取漏洞 (CVE-2023-39189)

  - 内核：netfilter：xtables sctp match_flags() 中的越界读取漏洞 (CVE-2023-39193)

  - 内核：xfrm：__xfrm_state_filter_match() 中的越界读取漏洞 (CVE-2023-39194)

  - 内核：QXL：qxl_mode_dumb_create() 中的争用条件会导致释放后使用 (CVE-2023-39198)

  - 内核：ipv4：ipv4_send_dest_unreach() 中的空指针取消引用漏洞 (CVE-2023-42754)

  - 内核：netfilter：IPSET_CMD_ADD 和 IPSET_CMD_SWAP 之间的争用条件 (CVE-2023-42756)

  - 内核：lib/kobject.c 容易受到 fill_kobj_path 的越界写入漏洞影响 (CVE-2023-45863)

  - 内核：io_uring_show_fdinfo 中的空指针取消引用漏洞 (CVE-2023-46862)

  - 内核：drivers/gpu/drm/drm_atomic.c 中的无阻塞原子提交和驱动程序卸载之间产生争用条件期间会发生释放后使用 (CVE-2023-51043)

  - 内核：蓝牙：bt_sock_ioctl 争用条件会导致 bt_sock_recvmsg 中发生释放后使用 (CVE-2023-51779)

  - 内核：net/atm/ioctl.c 中包含释放后使用漏洞 (CVE-2023-51780)

  - 内核：smb：client：修复 smb2_parse_contexts() 中潜在的 OOB 漏洞 (CVE-2023-52434)

  - 内核：gfs2：修复 gfs2_rgrp_dump 中的空指针取消引用漏洞 (CVE-2023-52448)

  - 内核：perf/x86/lbr：筛选 vsyscall 地址 (CVE-2023-52476)

  - 内核：mm/sparsemem：修复访问 memory_section->usage 时的争用情形  (CVE-2023-52489)

  - 内核：net：修复 neigh_periodic_work() 中可能存在的存储拆分问题 (CVE-2023-52522)

  - 内核：HID：sony：修复 sony_probe() 中潜在的内存泄漏问题 (CVE-2023-52529)

  - 内核：team：更改团队设备类型时会发生空指针取消引用问题 (CVE-2023-52574)

  - 内核：net：bridge：br_handle_frame_finish() 中的 data-races 包含数据争用问题 (CVE-2023-52578)

  - 内核：net/core：ETH_P_1588 流分析器中的内核崩溃问题 (CVE-2023-52580)

  - 内核：netfilter：nf_tables：当超过 255 个元素到期时会发生内存泄漏 (CVE-2023-52581)

  - 内核：net/sched：act_ct：修复了 ooo 分段上的 skb 泄漏和崩溃问题 (CVE-2023-52610)

  - 内核：netfilter：nf_tables：匿名集不允许超时 (CVE-2023-52620)

  - 内核：客户端的 receive_encrypted_standard 函数中存在 CIFS 文件系统解密不当输入验证远程代码执行漏洞 (CVE-2024-0565)

  - 内核：hugetlbfs：hugetlbfs_fill_super 函数中的空指针取消引用漏洞 (CVE-2024-0841)

  - 内核：nf_tables：nft_setelem_catchall_deactivate() 函数中的释放后使用漏洞 (CVE-2024-1085)

  - 内核：nf_tables：nft_verdict_init() 函数中存在释放后使用漏洞 (CVE-2024-1086)

  - kernel: tls：因部分读取和异步解密发生释放后使用 (CVE-2024-26582)

  - 内核：tls：异步通知和套接字关闭之间的争用问题 (CVE-2024-26583)

  - kernel: tls：处理 crypto 请求积压 (CVE-2024-26584)

  - 内核：tls：tx 工作排程和套接字关闭之间的争用问题 (CVE-2024-26585)

  - kernel: mlxsw: spectrum_acl_tcam：修复堆栈损坏 (CVE-2024-26586)

  - 内核：i2c：i801：修复区块进程调用事务 (CVE-2024-26593)

  - 内核：sched/membarrier：降低重创 sys_membarrier 的能力 (CVE-2024-26602)

  - 内核：netfilter：nf_tables：拒绝 QUEUE/DROP 判定参数 (CVE-2024-26609)

  - 内核：ip6_tunnel：修复 ip6_tnl_parse_tlv_enc_lim() 中的 NEXTHDR_FRAGMENT 处理 (CVE-2024-26633)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

AlmaLinux 9.2 主机上存在安装的程序包，该程序包受到 TuxCare ALMALINUX9.2：CLSA-2026：1783791447公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：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)

  - 在 Linux 内核的 TeleTYpe 子系统中发现越界读取缺陷。在 flush_to_ldisc 函数中存在内存泄漏时，用户使用 ioctls TIOCSPTLCK 和 TIOCGPTPEER 以及 TIOCSTI 和 TCXONC 触发争用条件时会发生此问题。此缺陷会让本地用户导致系统崩溃或从内存读取未经授权的随机数据。 (CVE-2022-1462)

  - 已修复 Linux 内核中的下列漏洞：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)

  - 已修复 Linux 内核中的下列漏洞：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)

  - 已修复 Linux 内核中的下列漏洞：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)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
248187	Linux Distros 未修补的漏洞：CVE-2023-53018	Nessus	Misc.	2025/8/11	2026/7/17	medium
194794	RHEL 9：内核 (RHSA-2024:2394)	Nessus	Red Hat Local Security Checks	2024/4/30	2025/10/29	critical
352871	AlmaLinux 9.2 [TuxCare] 安全更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.2：CLSA-2026：1783791447）	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/1	medium

检测

插件搜索

medium

critical

medium