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 中存在 NULL 指標解除參照 (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_flow_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() 中的 Null 指標解除參照弱點 (CVE-2023-6622)

  - 核心：lib/idr.c 中的 ida_free 包含 Null 指標解除參照弱點 (CVE-2023-6915)

  - 核心：perf_read_group() 中發生超出邊界寫入，這是 perf_event 的 read_size 溢位的結果 (CVE-2023-6931)

  - 核心：IPv4 IGMP 中的釋放後使用弱點 (CVE-2023-6932)

  - 核心：藍牙轉寄和未來密碼攻擊與防禦 (CVE-2023-24023)

  - kernel：irdma：不當存取控制 (CVE-2023-25775)

  - 核心：藍牙子系統的 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 nf_osf_match_one() 中的超出邊界讀取弱點 (CVE-2023-39193)

  - 核心：xfrm：__xfrm_state_filter_match() 中的超出邊界讀取弱點 (CVE-2023-39194)

  - 核心：QXL：qxl_mode_dumb_create() 中的爭用條件可導致釋放後使用 (CVE-2023-39198)

  - 核心：ipv4：ipv4_send_dest_unreach() 中的 NULL 指標解除參照弱點 (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 中的 Null 指標解除參照弱點 (CVE-2023-46862)

  - 核心：在 drivers/gpu/drm/drm_atomic.c 中的非封鎖 Atomic commit 和驅動程式卸載之間發生爭用情形時，會出現釋放後使用情形 (CVE-2023-51043)

  - 核心：bluetooth：bt_sock_ioctl bt_sock_recvmsg 中的爭用條件可導致釋放後使用 (CVE-2023-51779)

  - 核心：net/atm/ioctl.c 中的釋放後使用弱點 (CVE-2023-51780)

  - 核心：smb：用戶端：修正 smb2_parse_contexts() 中潛在的 OOB 弱點 (CVE-2023-52434)

  - 核心：gfs2：修正 gfs2_rgrp_dump 中的核心 NULL 指標解除參照弱點 (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：團隊裝置類型變更時會發生 NULL 指標解除參照 (CVE-2023-52574)

  - 核心：net：bridge：br_handle_frame_finish() 中的 indata-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 函式中的 Null 指標解除參照弱點 (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：處理密碼編譯要求的積存 (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 / etc 多個弱點（ALMALINUX9.2：CLSA-2026：1783791447）	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/1	medium

偵測

搜尋 Plugin

medium

critical

medium