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

  - Oracle MySQL 的 MySQL 服务器产品中的漏洞组件服务器遥测。支持的版本中受影响的是 8.4.2 和较早版本以及 9.0.1 和较早版本。难以利用的漏洞允许高权限攻击者通过多种协议进行网络访问，从而破坏 MySQL Server。
    成功攻击此漏洞可导致对 MySQL Server 可访问数据子集进行未经授权的读取访问。(CVE-2024-21243)

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

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

  - 已修复 Linux 内核中的下列漏洞：mmc: sdhci-of-esdhc: Fix refcount leak in esdhc_signal_voltage_switch of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.
    of_node_put() checks null pointer. (CVE-2022-50141)

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

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

  - 由于受攻击者控制的事件出现序列异常问题，包含任意（尽管无样式）内容的 Javascript alert() 对话框可显示在攻击者选择的不受控网页之上。此漏洞会影响版本低于 91.3 的 Firefox ESR、版本低于 94 的 Firefox 和版本低于 91.3 的 Thunderbird。
    (CVE-2021-38509)

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

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

  - 已修复 Linux 内核中的下列漏洞：crypto: arm64/neonbs - fix out-of-bounds access on short input The bit-sliced implementation of AES-CTR operates on blocks of 128 bytes, and will fall back to the plain NEON version for tail blocks or inputs that are shorter than 128 bytes to begin with. It will call straight into the plain NEON asm helper, which performs all memory accesses in granules of 16 bytes (the size of a NEON register). For this reason, the associated plain NEON glue code will copy inputs shorter than 16 bytes into a temporary buffer, given that this is a rare occurrence and it is not worth the effort to work around this in the asm code. The fallback from the bit-sliced NEON version fails to take this into account, potentially resulting in out-of-bounds accesses. So clone the same workaround, and use a temp buffer for short in/outputs. (CVE-2024-26789)

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

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

  - 在用户连接恶意 HCI TTY 蓝牙设备的方式中，发现 Linux 内核 HCI 设备初始化子系统中存在双重释放内存损坏缺陷。本地用户可利用此缺陷导致系统崩溃。此缺陷影响从 3.13 开始的所有 Linux 内核版本。(CVE-2021-3564)

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

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

  - 已修复 Linux 内核中的下列漏洞：ipv6: avoid use-after-free in ip6_fragment() Blamed commit claimed rcu_read_lock() was held by ip6_fragment() callers. It seems to not be always true, at least for UDP stack. syzbot reported: BUG: KASAN: use-after-free in ip6_dst_idev include/net/ip6_fib.h:245 [inline] BUG: KASAN: use-after-free in ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951 Read of size 8 at addr ffff88801d403e80 by task syz-executor.3/7618 CPU: 1 PID:
    7618 Comm: syz-executor.3 Not tainted 6.1.0-rc6-syzkaller-00012-g4312098baf37 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x15e/0x45d mm/kasan/report.c:395 kasan_report+0xbf/0x1f0 mm/kasan/report.c:495 ip6_dst_idev include/net/ip6_fib.h:245 [inline] ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951 __ip6_finish_output net/ipv6/ip6_output.c:193 [inline] ip6_finish_output+0x9a3/0x1170 net/ipv6/ip6_output.c:206 NF_HOOK_COND include/linux/netfilter.h:291 [inline] ip6_output+0x1f1/0x540 net/ipv6/ip6_output.c:227 dst_output include/net/dst.h:445 [inline] ip6_local_out+0xb3/0x1a0 net/ipv6/output_core.c:161 ip6_send_skb+0xbb/0x340 net/ipv6/ip6_output.c:1966 udp_v6_send_skb+0x82a/0x18a0 net/ipv6/udp.c:1286 udp_v6_push_pending_frames+0x140/0x200 net/ipv6/udp.c:1313 udpv6_sendmsg+0x18da/0x2c80 net/ipv6/udp.c:1606 inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0xd3/0x120 net/socket.c:734 sock_write_iter+0x295/0x3d0 net/socket.c:1108 call_write_iter include/linux/fs.h:2191 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x9ed/0xdd0 fs/read_write.c:584 ksys_write+0x1ec/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP:
    0033:0x7fde3588c0d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fde365b6168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX:
    00007fde359ac050 RCX: 00007fde3588c0d9 RDX: 000000000000ffdc RSI: 00000000200000c0 RDI: 000000000000000a RBP: 00007fde358e7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11:
    0000000000000246 R12: 0000000000000000 R13: 00007fde35acfb1f R14: 00007fde365b6300 R15: 0000000000022000 </TASK> Allocated by task 7618: kasan_save_stack+0x22/0x40 mm/kasan/common.c:45 kasan_set_track+0x25/0x30 mm/kasan/common.c:52 __kasan_slab_alloc+0x82/0x90 mm/kasan/common.c:325 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slab.h:737 [inline] slab_alloc_node mm/slub.c:3398 [inline] slab_alloc mm/slub.c:3406 [inline] __kmem_cache_alloc_lru mm/slub.c:3413 [inline] kmem_cache_alloc+0x2b4/0x3d0 mm/slub.c:3422 dst_alloc+0x14a/0x1f0 net/core/dst.c:92 ip6_dst_alloc+0x32/0xa0 net/ipv6/route.c:344 ip6_rt_pcpu_alloc net/ipv6/route.c:1369 [inline] rt6_make_pcpu_route net/ipv6/route.c:1417 [inline] ip6_pol_route+0x901/0x1190 net/ipv6/route.c:2254 pol_lookup_func include/net/ip6_fib.h:582 [inline] fib6_rule_lookup+0x52e/0x6f0 net/ipv6/fib6_rules.c:121 ip6_route_output_flags_noref+0x2e6/0x380 net/ipv6/route.c:2625 ip6_route_output_flags+0x76/0x320 net/ipv6/route.c:2638 ip6_route_output include/net/ip6_route.h:98 [inline] ip6_dst_lookup_tail+0x5ab/0x1620 net/ipv6/ip6_output.c:1092 ip6_dst_lookup_flow+0x90/0x1d0 net/ipv6/ip6_output.c:1222 ip6_sk_dst_lookup_flow+0x553/0x980 net/ipv6/ip6_output.c:1260 udpv6_sendmsg+0x151d/0x2c80 net/ipv6/udp.c:1554 inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665 sock_sendmsg_nosec n ---truncated--- (CVE-2022-48956)

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

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

  - Oracle MySQL 的 MySQL 服务器产品中的漏洞组件服务器PAM Auth 插件。支持的版本中受影响的是 8.0.28 和较早版本。难以利用的漏洞允许未经身份验证的攻击者通过多种协议进行网络访问，从而破坏 MySQL Server。成功攻击此漏洞可导致在未经授权的情况下访问重要数据，或完整访问所有可供访问的 MySQL Server 数据。(CVE-2022-21457)

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

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

  - scsimegaraid_sas修复探测失败时的资源泄漏 PCI 设备探测期间 scsi_add_host()、megasas_start_aen() 函数失败时驱动程序未正确清理所有分配资源。清理所有这些资源。 (CVE-2021-47329)

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

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

  - udp修复内存核算泄漏。Matt Downing 报告了一个奇怪的 UDP 内存使用问题。在正常操作下/proc/net/sockstat 中报告的 UDP 内存使用情况仍然接近于零。但是，该页面偶尔会激增至 524,288 页，并且从未下降。此外，当应用程序终止时，该值加倍。最后它会造成间歇性数据包丢弃。可以使用下面的脚本重现此问题 [0]1. /proc/net/sockstat 报告 0 个页面 # cat /proc/net/sockstat | grep UDP: UDP: inuse 1 mem 0 2. 运行脚本直到报告达到 524,288 # python3 test.py & sleep 5 # cat /proc/net/sockstat | grep UDP: UDP: inuse 1 mem 0 2。 grep UDP: UDP: inuse 3 mem 524288 <-- (INT_MAX + 1) >> PAGE_SHIFT 3. 终止套接字并确认数量永不下降 # pkill python3 && sleep 5 # cat /proc/net/sockstat | grep UDP: UDP: inuse 3 mem 524288 <-- (INT_MAX + 1) >> PAGE_SHIFT 3. grep UDP: UDP: inuse 1 mem 524288 4. v6.0 后的必要条件触发 proto_memory_pcpu_drain() # python3 test.py & sleep 1 && pkill python3 5. 数字加倍 # cat /proc/net/sockstat | grep UDP: UDP: inuse 1 mem 524288 4. v6.0 后的必要条件grep UDP: UDP: inuse 1 mem 1048577 应用程序将 INT_MAX 设置为 SO_RCVBUF从而触发 udp_rmem_release() 中的整数溢出。close()d 套接字时udp_destruct_common() 将清除其接收队列并对队列中的 skb->truesize 求和。此总数经过计算后存储在一个本地无符号整数变量中。然后总大小会传递到 udp_rmem_release() 以调整内存核算。但是由于该函数采用带符号的整数参数因此总大小可能回绕从而导致溢出。然后，按照如下方式计算释放量：1) 将大小添加到 sk->sk_forward_alloc。 2) 将 sk->sk_forward_alloc 向下舍入为最接近的 PAGE_SIZE 的较小倍数并将其分配给数量。 3) 从 sk->sk_forward_alloc 中减去数量。 4) 将数量 >> PAGE_SHIFT 传递至 __sk_mem_reduce_allocating()。发生 问题时udp_destruct_common() 中的总数为 2147484480 (INT_MAX + 833)在 udp_rmem_release() 中被转换为 -2147482816。
    在 1) sk->sk_forward_alloc 已从 3264 更改为 -2147479552且 2) 将 -2147479552 设置为数量。 3) 恢复了环绕因此在 inet_sock_destruct() 中没有看到警告。然而，udp_memory_allocating 在 4) 处加倍结束。自提交 3cd3399dd7a8net为 memory_allocating 实现 per-cpu 预留内存使用量在套接字 close()d 后不再立即加倍因为
    __sk_mem_reduce_allocate() 缓存 udp_memory_per_cpu_fw_alloc 中的数量。但是，下次 UDP 套接字接收到数据包时，减法运算便会生效，导致 UDP 内存使用量加倍。一旦套接字的 sk->sk_rmem_alloc 超过 net.ipv4.udp_rmem_min此问题就会导致进一步的内存分配失败从而导致数据包丢弃。为防止此问题我们使用 unsigned int 进行计算并且仅对较小的 delta 调用一次 sk_forward_alloc_add()。请注意first_packet_length() 也可能存在相同的问题。 [0]from socket import * SO_RCVBUFFORCE = 33 INT_MAX = (2 ** 31) - 1 s = socket(AF_INET, SOCK_DGRAM) s.bind(('', 0)) s.setsockopt(SOL_SOCKET, SO_RCVBUFFORCE, INT_MAX) c = socket(AF_INET, SOCK_DGRAM) c.connect(s.getsockname()) data = b'a' * 100 while Truec.send(data) (CVE-2025-22058)

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

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

  - tcpcdg允许多次调用 tcp_cdg_release() 显然 mptcp 能够在已断开连接的流上调用 tcp_disconnect()。除非当前的拥塞控制为 CDG 否则这通常没有问题因为可能触发双重释放 [1] 我们可以使 tcp_disconnect() 更具弹性而不是修复 MPTCP 以及未来的缺陷。 [1] BUGKASAN在 slab_free mm/slub.c:3539 [内联] 中发生双重释放 mm/slub.c:4567 CPU: 0 PID: 3645 Comm kworker/0:7 未受感染 6.0.0-syzkaller-02734-g0326074ff465 #0 硬件名称Google Google Compute Engine/Google Compute Engine、BIOS Google 09/22/2022 Workqueue事件 mptcp_worker 调用跟踪 <TASK> __dump_stack lib/dump_stack。 c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:317 [inline] print_report.cold+0x2ba/0x719 mm/kasan/report.c:433 kasan_report_invalid_free+0x81 /0x190 mm/kasan/report.c:462____kasan_slab_free+0x18b/0x1c0 mm/kasan/common.c:356 kasan_slab_free include/linux/kasan.h:200 [内联] slab_free_hook mm/slub.c:1759 [内联] slab_free_freelist_hook +0x8b/0x1c0 mm/slub.c:1785 slab_free mm/slub.c:3539 [inline] kfree+0xe2/0x580 mm/slub.c:4567 tcp_disconnect+0x980/0x1e20 net/ipv4/tcp.c:3145 __mptcp_close_ssk+ 0x5ca/0x7e0 net/mptcp/protocol.c:2327 mptcp_do_fastclose net/mptcp/prot ocol.c:2592 [inline] mptcp_worker+0x78c/0xff0 net/mptcp/protocol.c:2627 process_one_work+0x991/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/ 0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> 由任务分配 3671kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38 kasan_set_track mm/kasan/ common.c:45 [内联] set_alloc_info mm/kasan/common.c:437 [内联]____kasan_kmalloc mm/kasan/common.c:516 [内联]____kasan_kmalloc mm/kasan/common.c:475 [内联]
    __kasan_kmalloc+0xa9/0xd0 mm/kasan/common.c:525 kmalloc_array include/linux/slab.h:640 [内联] kcalloc include/linux/slab.h:671 [内联] tcp_cdg_init+0x10d/0x170 net/ipv4/tcp_cdg .c:380 tcp_init_congestion_control+0xab/0x550 net/ipv4/tcp_cong.c:193 tcp_reinit_congestion_control net/ipv4/tcp_cong.c:217 [内联] tcp_set_congestion_control+0x96c/0xaa0 net/ipv4/tcp_cong.c:391 do_tcp_cong.c:391do_tcp_congestion_control+0x96c/0xaa0net/ipv4/tcp_cong.c:391 net/ipv4/tcp.c:3513 tcp_setsockopt+0xd4/0x100 net/ipv4/tcp.c:3801 mptcp_setsockopt+0x35f/0x2570 net/mptcp/sockopt.c:844 __sys_setsockopt+0x2d6/0x690 net/socket.c:2252
    __do_sys_setsockopt net/socket.c:2263 [内联] __se_sys_setsockopt net/socket.c:2260 [内联]
    __x64_sys_setsockopt+0xba/0x150 net/socket.c:2260 do_syscall_x64 arch/x86/entry/common.c:50 [内联] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd 由任务 16kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38 kasan_set_track+0x21/0x30 mm/kasan/common.c:45 kasan_set_free_info+0x20/0x30 mm/kasan/generic.c:370____kasan_slab_free mm/kasan/ common.c:367 [内联]
    ____kasan_slab_free+0x166/0x1c0 mm/kasan/common.c:329 kasan_slab_free include/linux/kasan.h:200 [内联] slab_free_hook mm/slub.c:1759 [内联] slab_free_freelist_hook+0x8b/0x1c0 mm/slub.c:1785 slab_free mm/slub.c:3539 [inline] kfree+0xe2/0x580 mm/slub.c:4567 tcp_cleanup_congestion_control+0x70/0x120 net/ipv4/tcp_cong.c:226 tcp_v4_destroy_sock+0xdd/0x750 net/ipv4/tcp_ipv4.c 2254 tcp_v6_destroy_sock+0x11/0x20 net/ipv6/tcp_ipv6.c:1969 inet_csk_destroy_sock+0x196/0x440 net/ipv4/inet_connection_sock.c:1157 tcp_done+0x23b/0x340 net/ipv4/tcp.c:4649 tcp_rcv_state_process+0x40e7/0x4990 net/ ipv4/tcp_input.c:6624 tcp_v6_do_rcv+0x3fc/0x13c0 net/ipv6/tcp_ipv6.c:1525 tcp_v6_rcv+0x2e8e/0x3830 net/ipv6/tcp_ipv6.c:1759 ip6_protocol_deliver_rcu+0x2db/0x1950 net/ipv6/ip6_input.c:439 ip6_input_finish +0x14c/0x2c0 net/ipv6/ip6_input.c:484 NF_HOOK include/linux/netfilter.h:302 [内联] NF_HOOK include/linux/netfilter.h:296 [内联] ip6_input+0x9c/0xd ---truncated--- (CVE-2022-49775)

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

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

  - ipmi修复卸载 ipmi_si 和 ipmi_msghandler 模块时的 UAF 您好， 当测试安装和卸载 ipmi_si.ko 和 ipmi_msghandler.ko 时系统崩溃。日志如下[ 141.087026] 缺陷无法处理 ffffffffc09b3a5a 上的内核分页请求 [ 141.087241] PGD 8fe4c0d067 P4D 8fe4c0d067 PUD 8fe4c0f067 PMD 103ad89067 PTE 0 [ 141.087464] Oops: 0010 [#1] SMP NOPTI [ 141.087580] CPU: 67 PID: 668 Comm: kworker/67:1 Kdump已加载未受感染 4.18.0.x86_64 #47 [ 141.088009] Workqueue事件 0xffffffffc09b3a40 [ 141.088009] RIP0010:0xffffffffc09b3a5a [ 141.088009] 代码错误的 RIP 值。 [141.088009] RSP: 0018:ffffb9094e2c3e88 EFLAGS: 00010246 [ 141.088009] RAX: 0000000000000000 RBX
    ffff9abfdb1f04a0 RCX 0000000000000000 [ 141.088009] RDX000000000000000 RSI0000000000000246 RDI
    0000000000000246 [ 141.088009] RBP: 0000000000000000 R08: ffff9abfffee3cb8 R09: 00000000000002e1 [141.088009] R10: ffffb9094cb73d90 R11: 00000000000f4240 R12: ffff9abfffee8700 [ 141.088009] R13:
     R140000000000000000  : ffff9abfdb1f04a0 R15: ffff9abfdb1f04a8 [ 141.088009] FS: 0000000000000000(0000) GS:ffff9abfffec0000(0000) knlGS:0000000000000000 [ 141.088009] CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 [ 141.088009] CR2: ffffffffc09b3a30 CR3: 0000008fe4c0a001 CR4: 00000000007606e0 [141.088009] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 141.088009] DR3:
    0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 141.088009] PKRU55555554 [ 141.088009] 调用跟踪 [ 141.088009] ? process_one_work+0x195/0x390 [ 141.088009] ? worker_thread+0x30/0x390 [141.088009] process_one_work+0x390/0x390 [ 141.088009] ? kthread+0x10d/0x130 [ 141.088009] ? kthread_flush_work_fn+0x10/0x10 [ 141.088009] ? ret_from_fork+0x35/0x40] 缺陷无法处理 ffffffffc0b28a5a 上的内核分页请求 [ 200.223240] PGD 97fe00d067 P4D 200.22357997fe00d067 PUD 97fe00f067 PMD a580cbf067 PTE 0 [ 200.223464] Oops: 0010 [#1] SMP ] NOPTI: [63] PID: 664 Comm: kworker/63:1 Kdump: supported Not tainted 4.18.0.x86_64 #46 [ 200.224008] Workqueue事件 0xffffffffc0b28a40 [200.224008] RIP0010:0xffffffffc0b28a5a [ 200.224008] 代码错误的 RIP 值。 [ 200.224008] RSP
    0018ffffbf3c8e2a3e88 EFLAGS00010246 [ 200.224008] RAX: 0000000000000000 RBX: ffffa0799ad6bca0 RCX
    0000000000000000 [ 200.224008] RDX: 0000000000000000 RSI: 0000000000000246 RDI: 0000000000000246 [200.224008] RBP: 0000000000000000 R08: ffff9fe43fde3cb8 R09: 00000000000000d5 [ 200.224008] R10:
    ffffbf3c8cb53d90 R1100000000000f4240 R12ffff9fe43fde8700 [ 200.224008] R130000000000000000 R14
     R15ffffa0799ad6bca0  : ffffa0799ad6bca8 [ 200.224008] FS: 0000000000000000(0000) GS:ffff9fe43fdc0000(0000) knlGS:0000000000000000 [ 200.224008] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 200.224008] CR2:
    ffffffffc0b28a30 CR3: 00000097fe00a002 CR4: 00000000007606e0 [ 200.224008] DR0: 0000000000000000 DR1:
    0000000000000000 DR2：0000000000000000 [ 200.224008] DR3：0000000000000000 DR6：00000000fffe0ff0 DR7：
    0000000000000400 [ 200.224008] PKRU: 55555554 [ 200.224008] 调用跟踪 [ 200.224008] ? process_one_work+0x195/0x390 [ 200.224008] ? worker_thread+0x30/0x390 [ 200.224008] process_one_work+0x390/0x390 [ 200.224008] ? kthread+0x10d/0x130 [ 200.224008] ? kthread_flush_work_fn+0x10/0x10 [ 200.224008] ? ret_from_fork+0x35/0x40 [ 200.224008] 在 CPU 63 上启动内核错误 (0x1) 通知 [ 200.224008] 在 CPU 63 上完成内核错误 (0x1) 通知 [200.224008] CR2: ffffffffc0b28a5a [ 200.224008] ---[ 结束跟踪 c82a412d93f57412 ]--- 原因如下 T1rmmod ipmi_si。 ->ipmi_unregister_smi() -> ipmi_bmc_unregister() -> __ipmi_bmc_unregister() -> kref_put(&bmc->usecount, cleanup_bmc_device); -> schedule_work(&bmc->remove_work); T2rmmod ipmi_msghandl
    ---truncated--- (CVE-2021-47100)

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

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

  - dma-buf/dma-resv检查新隔离是否确实更晚以前当我们向 dma_resv 对象添加隔离时我们始终假定比所有现有的隔离更新。Jason 将 UAPI 添加至显式导出/导入后这种情况不再必要。因此如果不进行此检查将允许用户空间强制内核进入释放后使用错误。由于此变更规模非常小且具有防御性因此最好将此变更也向后移植到稳定内核以防其他人以相同方式使用 dma_resv 对象。 (CVE-2022-49935)

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

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

  - 已修复 Linux 内核中的下列漏洞：drivers/thermal/loongson2_thermal: Fix incorrect PTR_ERR() judgment PTR_ERR() returns -ENODEV when thermal-zones are undefined, and we need
    -ENODEV as the right value for comparison. Otherwise, tz->type is NULL when thermal-zones is undefined, resulting in the following error: [ 12.290030] CPU 1 Unable to handle kernel paging request at virtual address fffffffffffffff1, era == 900000000355f410, ra == 90000000031579b8 [ 12.302877] Oops[#1]: [12.305190] CPU: 1 PID: 181 Comm: systemd-udevd Not tainted 6.6.0-rc7+ #5385 [ 12.312304] pc 900000000355f410 ra 90000000031579b8 tp 90000001069e8000 sp 90000001069eba10 [ 12.320739] a0 0000000000000000 a1 fffffffffffffff1 a2 0000000000000014 a3 0000000000000001 [ 12.329173] a4 90000001069eb990 a5 0000000000000001 a6 0000000000001001 a7 900000010003431c [ 12.337606] t0 fffffffffffffff1 t1 54567fd5da9b4fd4 t2 900000010614ec40 t3 00000000000dc901 [ 12.346041] t4 0000000000000000 t5 0000000000000004 t6 900000010614ee20 t7 900000000d00b790 [ 12.354472] t8 00000000000dc901 u0 54567fd5da9b4fd4 s9 900000000402ae10 s0 900000010614ec40 [ 12.362916] s1 90000000039fced0 s2 ffffffffffffffed s3 ffffffffffffffed s4 9000000003acc000 [ 12.362931] s5 0000000000000004 s6 fffffffffffff000 s7 0000000000000490 s8 90000001028b2ec8 [ 12.362938] ra:
    90000000031579b8 thermal_add_hwmon_sysfs+0x258/0x300 [ 12.386411] ERA: 900000000355f410 strscpy+0xf0/0x160 [ 12.391626] CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE) [ 12.397898] PRMD: 00000004 (PPLV0 +PIE
    -PWE) [ 12.403678] EUEN: 00000000 (-FPE -SXE -ASXE -BTE) [ 12.409859] ECFG: 00071c1c (LIE=2-4,10-12 VS=7) [ 12.415882] ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0) [ 12.415907] BADV: fffffffffffffff1 [12.415911] PRID: 0014a000 (Loongson-64bit, Loongson-2K1000) [ 12.415917] Modules linked in:
    loongson2_thermal(+) vfat fat uio_pdrv_genirq uio fuse zram zsmalloc [ 12.415950] Process systemd-udevd (pid: 181, threadinfo=00000000358b9718, task=00000000ace72fe3) [ 12.415961] Stack : 0000000000000dc0 54567fd5da9b4fd4 900000000402ae10 9000000002df9358 [ 12.415982] ffffffffffffffed 0000000000000004 9000000107a10aa8 90000001002a3410 [ 12.415999] ffffffffffffffed ffffffffffffffed 9000000107a11268 9000000003157ab0 [ 12.416016] 9000000107a10aa8 ffffff80020fc0c8 90000001002a3410 ffffffffffffffed [12.416032] 0000000000000024 ffffff80020cc1e8 900000000402b2a0 9000000003acc000 [ 12.416048] 90000001002a3410 0000000000000000 ffffff80020f4030 90000001002a3410 [ 12.416065] 0000000000000000 9000000002df6808 90000001002a3410 0000000000000000 [ 12.416081] ffffff80020f4030 0000000000000000 90000001002a3410 9000000002df2ba8 [ 12.416097] 00000000000000b4 90000001002a34f4 90000001002a3410 0000000000000002 [ 12.416114] ffffff80020f4030 fffffffffffffff0 90000001002a3410 9000000002df2f30 [12.416131] ... [ 12.416138] Call Trace: [ 12.416142] [<900000000355f410>] strscpy+0xf0/0x160 [ 12.416167] [<90000000031579b8>] thermal_add_hwmon_sysfs+0x258/0x300 [ 12.416183] [<9000000003157ab0>] devm_thermal_add_hwmon_sysfs+0x50/0xe0 [ 12.416200] [<ffffff80020cc1e8>] loongson2_thermal_probe+0x128/0x200 [loongson2_thermal] [ 12.416232] [<9000000002df6808>] platform_probe+0x68/0x140 [ 12.416249] [<9000000002df2ba8>] really_probe+0xc8/0x3c0 [ 12.416269] [<9000000002df2f30>] __driver_probe_device+0x90/0x180 [ 12.416286] [<9000000002df3058>] driver_probe_device+0x38/0x160 [ 12.416302] [<9000000002df33a8>] __driver_attach+0xa8/0x200 [ 12.416314] [<9000000002deffec>] bus_for_each_dev+0x8c/0x120 [ 12.416330] [<9000000002df198c>] bus_add_driver+0x10c/0x2a0 [ 12.416346] [<9000000002df46b4>] driver_register+0x74/0x160 [ 12.416358] [<90000000022201a4>] do_one_initcall+0x84/0x220 [ 12.416372] [<90000000022f3ab8>] do_init_module+0x58/0x2c0 [ ---truncated--- (CVE-2023-52613)

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

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

  - 已修复 Linux 内核中的下列漏洞：media: hantro: Check whether reset op is defined before use The i.MX8MM/N/P does not define the .reset op since reset of the VPU is done by genpd. Check whether the .reset op is defined before calling it to avoid NULL pointer dereference. Note that the Fixes tag is set to the commit which removed the reset op from i.MX8M Hantro G2 implementation, this is because before this commit all the implementations did define the .reset op. (CVE-2023-52850)

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

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

  - 6.x 之前的 Drupal 6.38 和 7.x 之前的 7.43 中的 XML-RPC 系统可能使远程攻击者更容易通过同时对同一方法进行大量调用来进行暴力破解攻击。
    (CVE-2016-3163)

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

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

  - 已修复 Linux 内核中的下列漏洞：thermal/netlink: Prevent userspace segmentation fault by adjusting UAPI header The intel-lpmd tool [1], which uses the THERMAL_GENL_ATTR_CPU_CAPABILITY attribute to receive HFI events from kernel space, encounters a segmentation fault after commit 1773572863c4 (thermal: netlink: Add the commands and the events for the thresholds). The issue arises because the THERMAL_GENL_ATTR_CPU_CAPABILITY raw value was changed while intel_lpmd still uses the old value. Although intel_lpmd can be updated to check the THERMAL_GENL_VERSION and use the appropriate THERMAL_GENL_ATTR_CPU_CAPABILITY value, the commit itself is questionable. The commit introduced a new element in the middle of enum thermal_genl_attr, which affects many existing attributes and introduces potential risks and unnecessary maintenance burdens for userspace thermal netlink event users. Solve the issue by moving the newly introduced THERMAL_GENL_ATTR_TZ_PREV_TEMP attribute to the end of the enum thermal_genl_attr. This ensures that all existing thermal generic netlink attributes remain unaffected. [ rjw: Subject edits ] (CVE-2025-21840)

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

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

  - drm/imagination避免隔离释放上的死锁使计划程序在工作队列上而不是在释放函数本身中对隔离释放处理排队。修复了如下所示的死锁问题 [607.400437] ====================================== ====== [ 607.405755] 警告检测到可能递归锁定 [ 607.415500] ------------------------------ -------------- [ 607.420817] weston:zfq0/24149 正在尝试获取锁定[ 607.426131] ffff000017d041a0 (reservation_ww_class_mutex){+.+.}-{3:3}位于其他
    pvr_gem_object_vunmap+0x40/0xc0 [powervr] [ 607.436728] 但任务已持有锁定[ 607.442554] ffff0000017d105a0 (reservation_ww_class_mutex){+.+.}-{3:3}位于 dma_buf_ioctl+0x250/0x554 [ 607.451727]可能有助于我们调试此问题的其他信息[ 607.458245] 可能不安全的锁定情况[ 607.464155] CPU0 [ 607.466601] ---- [ 607.469044] lock(reservation_ww_class_mutex); [ 607.473584] lock(reservation_ww_class_mutex); [ 607.478114] *** DEADLOCK *** (CVE-2025-21911

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

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

  - 在 Linux 内核 4.17 之前版本中，BPF 子系统未正确处理指令序列上的长跳转，其中内部指令要求大量扩展为多个 BPF 指令，从而导致溢出问题。此问题会影响 kernel/bpf/core.c 和 net/core/filter.c。
    (CVE-2018-25020)

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

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

  - 已修复 Linux 内核中的下列漏洞：nfsd: decrease sc_count directly if fail to queue dl_recall A deadlock warning occurred when invoking nfs4_put_stid following a failed dl_recall queue operation: T1 T2 nfs4_laundromat nfs4_get_client_reaplist nfs4_anylock_blockers
    __break_lease spin_lock // ctx->flc_lock spin_lock // clp->cl_lock nfs4_lockowner_has_blockers locks_owner_has_blockers spin_lock // flctx->flc_lock nfsd_break_deleg_cb nfsd_break_one_deleg nfs4_put_stid refcount_dec_and_lock spin_lock // clp->cl_lock When a file is opened, an nfs4_delegation is allocated with sc_count initialized to 1, and the file_lease holds a reference to the delegation. The file_lease is then associated with the file through kernel_setlease. The disassociation is performed in nfsd4_delegreturn via the following call chain: nfsd4_delegreturn --> destroy_delegation --> destroy_unhashed_deleg --> nfs4_unlock_deleg_lease --> kernel_setlease --> generic_delete_lease The corresponding sc_count reference will be released after this disassociation. Since nfsd_break_one_deleg executes while holding the flc_lock, the disassociation process becomes blocked when attempting to acquire flc_lock in generic_delete_lease. This means: 1) sc_count in nfsd_break_one_deleg will not be decremented to 0; 2) The nfs4_put_stid called by nfsd_break_one_deleg will not attempt to acquire cl_lock; 3) Consequently, no deadlock condition is created. Given that sc_count in nfsd_break_one_deleg remains non-zero, we can safely perform refcount_dec on sc_count directly. This approach effectively avoids triggering deadlock warnings. (CVE-2025-37871)

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

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

  - 已修复 Linux 内核中的下列漏洞：leds: trigger: netdev: Fix kernel panic on interface rename trig notify Commit d5e01266e7f5 (leds: trigger: netdev: add additional specific link speed mode) in the various changes, reworked the way to set the LINKUP mode in commit cee4bd16c319 (leds: trigger: netdev: Recheck NETDEV_LED_MODE_LINKUP on dev rename) and moved it to a generic function. This changed the logic where, in the previous implementation the dev from the trigger event was used to check if the carrier was ok, but in the new implementation with the generic function, the dev in trigger_data is used instead. This is problematic and cause a possible kernel panic due to the fact that the dev in the trigger_data still reference the old one as the new one (passed from the trigger event) still has to be hold and saved in the trigger_data struct (done in the NETDEV_REGISTER case). On calling of get_device_state(), an invalid net_dev is used and this cause a kernel panic. To handle this correctly, move the call to get_device_state() after the new net_dev is correctly set in trigger_data (in the NETDEV_REGISTER case) and correctly parse the new dev. (CVE-2024-27063)

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

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

  - Google Chrome 84.0.4147.89 之前版本的 V8 中存在类型混淆漏洞，远程攻击者可能利用此漏洞，通过构建的 HTML 页面来利用堆损坏。(CVE-2020-6512)

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

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

  - 在 janus-gateway也称为 Janus WebRTC 服务器中发现一个问题 0.10.0。
    plugins/janus_streaming.c 中的 janus_streaming_rtsp_parse_sdp 通过特制的 RTSP 服务器导致缓冲区溢出。 (CVE-2020-14033)

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

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

  - wifiar5523启用正确的端点验证 Syzkaller 报告 [1] 命中关于正在使用的且不具有预期类型的端点的警告。通过检查是否存在所有适当的端点及其未受损的相应类型来修复 问题。遗憾的是此修补程序尚未在实际硬件上进行测试。 [1] Syzkaller 报告------------[ cut here ]------------ usb 1-1: BOGUS urb xfer管道 3 != 类型 1 警告CPU0 PID 3643 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 ... 调用跟踪 <TASK> ar5523_cmd+0x41b/0x780 drivers/net/wireless/ath/ar5523/ar5523.c:275 ar5523_cmd_read drivers/net/wireless/ath/ar5523/ar5523.c:302 [内联] ar5523_host_available drivers/net/wireless /ath/ar5523/ar5523.c:1376 [inline] ar5523_probe+0x14b0/0x1d10 drivers/net/wireless/ath/ar5523/ar5523.c:1655 usb_probe_interface+0x30f/0x7f0 drivers/usb/core/driver.c:396 call_driver_probe drivers/base/dd.c:560 [内联] real_probe+0x249/0xb90 drivers/base/dd.c:639 __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778 driver_probe_device+0x4c/0x1a0 drivers/base/dd .c:808 __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936 bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427 __device_attach+0x1e4/0x530 drivers/base/dd.c:1008 bus_probe_device+0x1e8/ 0x2a0 drivers/base/bus.c:487 device_add+0xbd9/0x1e90 drivers/base/core.c:3517 usb_set_configuration+0x101d/0x1900 drivers/usb/core/message.c:2170 usb_generic_driver_probe+0xbe/0x100 drivers/usb/core /generic.c:238 usb_probe_device+0xd8/0x2c0 驱动程序s/usb/core/driver.c:293 call_driver_probe drivers/base/dd.c:560 [inline] real_probe+0x249/0xb90 drivers/base/dd.c:639 __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c 778 driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808 __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936 bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427 __device_attach+0x1e4/0x530 驱动程序/base/dd.c:1008 bus_probe_device+0x1e8/0x2a0 drivers/base/bus.c:487 device_add+0xbd9/0x1e90 drivers/base/core.c:3517 usb_new_device.cold+0x685/0x10ad drivers/usb/core/hub .c:2573 hub_port_connect drivers/usb/core/hub.c:5353 [内联] hub_port_connect_change drivers/usb/core/hub.c:5497 [内联] port_event drivers/usb/core/hub.c:5653 [内联] hub_event +0x26cb/0x45d0 drivers/usb/core/hub.c:5735 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289 work_thread+0x669/0x1090 kernel/workqueue.c:2436 kthread+0x2e8/0x3a0 kernel/kthread.c 376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> (CVE-2024-38565)

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

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

  - 在 Firefox 119 中修复了内存安全缺陷。其中某些错误展示出内存损坏迹象，我们推测如果攻击者进行足够的尝试，则可以利用此漏洞运行任意代码。此漏洞影响 Firefox < 120。(CVE-2023-6213)

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

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

  - 已修复 Linux 内核中的下列漏洞：HID: bigbenff: prevent null pointer dereference When emulating the device through uhid, there is a chance we don't have output reports and so report_field is null. (CVE-2021-47522)

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

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

  - 已修复 Linux 内核中的下列漏洞：mm/slub: avoid zeroing outside-object freepointer for single free Commit 284f17ac13fe (mm/slub: handle bulk and single object freeing separately) splits single and bulk object freeing in two functions slab_free() and slab_free_bulk() which leads slab_free() to call slab_free_hook() directly instead of slab_free_freelist_hook(). If `init_on_free` is set, slab_free_hook() zeroes the object. Afterward, if `slub_debug=F` and `CONFIG_SLAB_FREELIST_HARDENED` are set, the do_slab_free() slowpath executes freelist consistency checks and try to decode a zeroed freepointer which leads to a Freepointer corrupt detection in check_object().
    During bulk free, slab_free_freelist_hook() isn't affected as it always sets it objects freepointer using set_freepointer() to maintain its reconstructed freelist after `init_on_free`. For single free, object's freepointer thus needs to be avoided when stored outside the object if `init_on_free` is set. The freepointer left as is, check_object() may later detect an invalid pointer value due to objects overflow.
    To reproduce, set `slub_debug=FU init_on_free=1 log_level=7` on the command line of a kernel build with `CONFIG_SLAB_FREELIST_HARDENED=y`. dmesg sample log: [ 10.708715] ============================================================================= [ 10.710323] BUG kmalloc-rnd-05-32 (Tainted: G B T ): Freepointer corrupt [ 10.712695]
    ----------------------------------------------------------------------------- [ 10.712695] [ 10.712695] Slab 0xffffd8bdc400d580 objects=32 used=4 fp=0xffff9d9a80356f80 flags=0x200000000000a00(workingset|slab|node=0|zone=2) [ 10.716698] Object 0xffff9d9a80356600 @offset=1536 fp=0x7ee4f480ce0ecd7c [ 10.716698] [ 10.716698] Bytes b4 ffff9d9a803565f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [ 10.720703] Object ffff9d9a80356600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [ 10.720703] Object ffff9d9a80356610: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [ 10.724696] Padding ffff9d9a8035666c: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [ 10.724696] Padding ffff9d9a8035667c: 00 00 00 00 .... [ 10.724696] FIX kmalloc-rnd-05-32: Object at 0xffff9d9a80356600 not freed (CVE-2024-36892)

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

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

  - perfarm-ni探测失败时取消注册 PMU。当 NI 设备的一个时钟域中的资源分配失败时我们需要正确回滚相同设备的其他时钟域中之前注册的所有 perf PMU。否则会导致内核错误。调用 arm_ni_init+0x0/0xff8 [arm_ni] @ 2374 arm-ni ARMHCB70:00无法请求 PMU 区域 0x1f3c13000 arm-ni ARMHCB70:00使用驱动程序 arm-ni 的探测失败并出现错误 -16 list_add 损坏next-> prev 应为 prev (fffffd01e9698a18)但却是 0000000000000000。(next=ffff10001a0decc8)。 pstate6340009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) pc list_add_valid_or_report+0x7c/0xb8 lr : list_add_valid_or_report+0x7c/0xb8 调用跟踪
    __list_add_valid_or_report+0x7c/0xb8 perf_pmu_register+0x22c/0x3a0 arm_ni_probe+0x554/0x70c [arm_ni] platform_probe+0x70/0xe8 really_probe+0xc6/0x4d8 driver_probe_device+0x48/0x170 __driver_attach+0x8e/0x1c0 bus_for_each_dev+0x64/0xf0 driver_add+0x138/0x260 bus_add_driver+ 0x68/0x138
    __platform_driver_register+0x2c/0x40 arm_ni_init+0x14/0x2a [arm_ni] do_init_module+0x36/0x298 ---[ end trace 0000000000000000 ]--- 内核错误 - 不同步Oops - 缺陷致命异常 SMP停止辅助 CPU (CVE-2025-38168)

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

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

  - 已修复 Linux 内核中的下列漏洞：tcp: prevent concurrent execution of tcp_sk_exit_batch Its possible that two threads call tcp_sk_exit_batch() concurrently, once from the cleanup_net workqueue, once from a task that failed to clone a new netns. In the latter case, error unwinding calls the exit handlers in reverse order for the 'failed' netns. tcp_sk_exit_batch() calls tcp_twsk_purge(). Problem is that since commit b099ce2602d8 (net: Batch inet_twsk_purge), this function picks up twsk in any dying netns, not just the one passed in via exit_batch list. This means that the error unwind of setup_net() can steal and destroy timewait sockets belonging to the exiting netns. This allows the netns exit worker to proceed to call WARN_ON_ONCE(!refcount_dec_and_test(&net->ipv4.tcp_death_row.tw_refcount)); without the expected 1 -> 0 transition, which then splats. At same time, error unwind path that is also running inet_twsk_purge() will splat as well: WARNING: .. at lib/refcount.c:31 refcount_warn_saturate+0x1ed/0x210 ... refcount_dec include/linux/refcount.h:351 [inline] inet_twsk_kill+0x758/0x9c0 net/ipv4/inet_timewait_sock.c:70 inet_twsk_deschedule_put net/ipv4/inet_timewait_sock.c:221 inet_twsk_purge+0x725/0x890 net/ipv4/inet_timewait_sock.c:304 tcp_sk_exit_batch+0x1c/0x170 net/ipv4/tcp_ipv4.c:3522 ops_exit_list+0x128/0x180 net/core/net_namespace.c:178 setup_net+0x714/0xb40 net/core/net_namespace.c:375 copy_net_ns+0x2f0/0x670 net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110 ... because refcount_dec() of tw_refcount unexpectedly dropped to 0. This doesn't seem like an actual bug (no tw sockets got lost and I don't see a use-after-free) but as erroneous trigger of debug check. Add a mutex to force strict ordering: the task that calls tcp_twsk_purge() blocks other task from doing final _dec_and_test before mutex-owner has removed all tw sockets of dying netns.
    (CVE-2024-44991)

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

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

  - 已修复 Linux 内核中的下列漏洞：seg6: fix the iif in the IPv6 socket control block When an IPv4 packet is received, the ip_rcv_core(...) sets the receiving interface index into the IPv4 socket control block (v5.16-rc4, net/ipv4/ip_input.c line 510): IPCB(skb)->iif = skb->skb_iif; If that IPv4 packet is meant to be encapsulated in an outer IPv6+SRH header, the seg6_do_srh_encap(...) performs the required encapsulation. In this case, the seg6_do_srh_encap function clears the IPv6 socket control block (v5.16-rc4 net/ipv6/seg6_iptunnel.c line 163): memset(IP6CB(skb), 0, sizeof(*IP6CB(skb))); The memset(...) was introduced in commit ef489749aae5 (ipv6: sr: clear IP6CB(skb) on SRH ip4ip6 encapsulation) a long time ago (2019-01-29). Since the IPv6 socket control block and the IPv4 socket control block share the same memory area (skb->cb), the receiving interface index info is lost (IP6CB(skb)->iif is set to zero). As a side effect, that condition triggers a NULL pointer dereference if commit 0857d6f8c759 (ipv6: When forwarding count rx stats on the orig netdev) is applied. To fix that issue, we set the IP6CB(skb)->iif with the index of the receiving interface once again. (CVE-2021-47515)

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

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

  - 在某些情况下，异步函数会导致导航失败，从而暴露目标 URL。此漏洞会影响版本低于 91.4.0 的 Thunderbird、版本低于 91.4.0 的 Firefox ESR 以及版本低于 95 的 Firefox。
    (CVE-2021-43536)

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

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

  - 在运行 ansible-galaxy 集合安装时，在 2.9.7 之前的所有 ansible-engine 版本 2.9.x 中发现了存档遍历缺陷。提取集合 .tar.gz 文件时，会在未正确清理文件名的情况下创建目录。攻击者可利用此问题以覆盖系统的任意文件。
    (CVE-2020-10691)

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

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

  - 已修复 Linux 内核中的下列漏洞：net: dsa: fix panic when DSA master device unbinds on shutdown Rafael reports that on a system with LX2160A and Marvell DSA switches, if a reboot occurs while the DSA master (dpaa2-eth) is up, the following panic can be seen: systemd-shutdown[1]: Rebooting. Unable to handle kernel paging request at virtual address 00a0000800000041 [00a0000800000041] address between user and kernel address ranges Internal error: Oops: 96000004 [#1] PREEMPT SMP CPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32 pc :
    dsa_slave_netdevice_event+0x130/0x3e4 lr : raw_notifier_call_chain+0x50/0x6c Call trace:
    dsa_slave_netdevice_event+0x130/0x3e4 raw_notifier_call_chain+0x50/0x6c call_netdevice_notifiers_info+0x54/0xa0 __dev_close_many+0x50/0x130 dev_close_many+0x84/0x120 unregister_netdevice_many+0x130/0x710 unregister_netdevice_queue+0x8c/0xd0 unregister_netdev+0x20/0x30 dpaa2_eth_remove+0x68/0x190 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver_internal+0xac/0xb0 device_links_unbind_consumers+0xd4/0x100
    __device_release_driver+0x94/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_device_remove+0x24/0x40 __fsl_mc_device_remove+0xc/0x20 device_for_each_child+0x58/0xa0 dprc_remove+0x90/0xb0 fsl_mc_driver_remove+0x20/0x5c
    __device_release_driver+0x21c/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_bus_remove+0x80/0x100 fsl_mc_bus_shutdown+0xc/0x1c platform_shutdown+0x20/0x30 device_shutdown+0x154/0x330 __do_sys_reboot+0x1cc/0x250
    __arm64_sys_reboot+0x20/0x30 invoke_syscall.constprop.0+0x4c/0xe0 do_el0_svc+0x4c/0x150 el0_svc+0x24/0xb0 el0t_64_sync_handler+0xa8/0xb0 el0t_64_sync+0x178/0x17c It can be seen from the stack trace that the problem is that the deregistration of the master causes a dev_close(), which gets notified as NETDEV_GOING_DOWN to dsa_slave_netdevice_event(). But dsa_switch_shutdown() has already run, and this has unregistered the DSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts to call dev_close_many() on those slave interfaces, leading to the problem. The previous attempt to avoid the NETDEV_GOING_DOWN on the master after dsa_switch_shutdown() was called seems improper. Unregistering the slave interfaces is unnecessary and unhelpful. Instead, after the slaves have stopped being uppers of the DSA master, we can now reset to NULL the master->dsa_ptr pointer, which will make DSA start ignoring all future notifier events on the master. (CVE-2022-48808)

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

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

  - 已修复 Linux 内核中的下列漏洞：mm, slub: fix potential use-after-free in slab_debugfs_fops When sysfs_slab_add failed, we shouldn't call debugfs_slab_add() for s because s will be freed soon. And slab_debugfs_fops will use s later leading to a use-after-free. (CVE-2021-47470)

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

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

  - 已修复 Linux 内核中的下列漏洞：drm/meson: Fix refcount bugs in meson_vpu_has_available_connectors() In this function, there are two refcount leak bugs: (1) when breaking out of for_each_endpoint_of_node(), we need call the of_node_put() for the 'ep'; (2) we should call of_node_put() for the reference returned by of_graph_get_remote_port() when it is not used anymore.
    (CVE-2022-50038)

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

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

  - 执行附加组件更新时，以非内建 root 终止的证书链会被拒绝（即使由管理员合法添加）。这可导致附加组件在未通知用户的情况下静默过期。此漏洞会影响 Firefox ESR < 68.10、Firefox < 78 和 Thunderbird < 68.10.0。(CVE-2020-12421)

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

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

  - Oracle MySQL 的 MySQL Server 产品中存在漏洞（组件：Server: DDL）。支持的版本中受影响的是 8.0.28 和较早版本。利用此漏洞的难度较低，通过多种协议进行网络访问的高权限攻击者可借此破坏 MySQL Server。成功利用此漏洞进行攻击可导致在未经授权的情况下造成 MySQL Server 挂起或频繁出现崩溃（完整 DOS），以及未经授权更新、插入或删除某些 MySQL Server 可访问数据的访问权限。(CVE-2022-21425)

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

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

  - 内核 scsi 驱动程序中存在权限提升漏洞。产品：Android。版本：Android 内核。Android ID A-65023233。(CVE-2017-13168)

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

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

  - 已修复 Linux 内核中的下列漏洞：x86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro In the TDX_HYPERCALL asm, after the TDCALL instruction returns from the untrusted VMM, the registers that the TDX guest shares to the VMM need to be cleared to avoid speculative execution of VMM-provided values. RSI is specified in the bitmap of those registers, but it is missing when zeroing out those registers in the current TDX_HYPERCALL. It was there when it was originally added in commit 752d13305c78 (x86/tdx: Expand __tdx_hypercall() to handle more arguments), but was later removed in commit 1e70c680375a (x86/tdx: Do not corrupt frame-pointer in __tdx_hypercall()), which was correct because %rsi is later restored in the pop %rsi. However a later commit 7a3a401874be (x86/tdx: Drop flags from __tdx_hypercall()) removed that pop %rsi but forgot to add the xor %rsi, %rsi back. Fix by adding it back. (CVE-2023-52874)

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

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

  - 已修复 Linux 内核中的下列漏洞：mtd: parsers: qcom: Fix kernel panic on skipped partition In the event of a skipped partition (case when the entry name is empty) the kernel panics in the cleanup function as the name entry is NULL. Rework the parser logic by first checking the real partition number and then allocate the space and set the data for the valid partitions. The logic was also fundamentally wrong as with a skipped partition, the parts number returned was incorrect by not decreasing it for the skipped partitions. (CVE-2022-48777)

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

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

  - 启用响应式设计模式时，它会使用对之前已释放的对象的引用。我们推测若攻击者有意操控，就能利用此漏洞运行任意代码。此漏洞会影响 Firefox ESR < 78.10、Thunderbird < 78.10 和 Firefox < 88。(CVE-2021-23995)

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

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

  - 已修复 Linux 内核中的下列漏洞：usb: ulpi: Fix debugfs directory leak The ULPI per-device debugfs root is named after the ulpi device's parent, but ulpi_unregister_interface tries to remove a debugfs directory named after the ulpi device itself. This results in the directory sticking around and preventing subsequent (deferred) probes from succeeding. Change the directory name to match the ulpi device. (CVE-2024-26919)

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

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

  - 在适用于 Windows 和 Linux 的 NVIDIA CUDA 工具包中，nvdisasm 命令行工具中存在一个漏洞，导致攻击者可通过诱骗用户在恶意 ELF 文件中运行 nvdisasm，造成输入验证不当问题。成功利用此漏洞可导致拒绝服务。
    (CVE-2024-0123)

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

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

  - Linux 内核中的 io_uring 子系统允许在 PROVIDE_BUFFERS 运算中绕过 MAX_RW_COUNT 限制，从而导致读取 /proc/<PID>/mem 时在 mem_rw 中使用负值。
    此问题可用于引发堆溢出，继而导致在内核中执行任意代码。此问题已通过提交 d1f82808877b (io_uring：在提供缓冲区时截断大于 MAX_RW_COUNT 的长度) (v5.13-rc1) 解决，并向后移植到 v5.12.4、v5.11.21 和 v5.10.37 版的稳定内核中。此问题是在 ddf0322db79c (io_uring: 添加 IORING_OP_PROVIDE_BUFFERS) (v5.7-rc1) 中引入。(CVE-2021-3491)

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

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

  - 在 32 位平台上运行的 3.15.2 之前的 Linux 内核中，lib/lz4/lz4_decompress.c 中的 lz4_uncompress 函数和 r118 之前的 Yann Collet LZ4 中使用的 LZ4 算法实现中存在整数溢出漏洞，可能允许上下文有关的攻击者通过构建的由编译时无 API 限制的程序错误处理的 Literal Run 来造成拒绝服务（内存损坏）或者可能产生其他不明影响，此漏洞与 CVE-2014-4715 不同。(CVE-2014-4611)

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

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

  - Firefox 的 HTML 解析器未正确解释 HTML 注释标签，从而导致与其他浏览器之间存在不一致问题。这可被用来在放置了用户控制数据的页面上转义 HTML 注释。此漏洞会影响 101 版本之前的 Firefox。(CVE-2022-31743)

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

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

  - 上游 Linux 文件系统存在权限提升漏洞。产品：Android。版本：
    Android 内核。Android ID: A-36817013。 (CVE-2017-0750)

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

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

  - requestPointerLock() 和 setTimeout() 的争用条件可导致用户在认为自己位于别的选项卡上的情况下，与某个选项卡互动。结合某些元素例如 <input type=file>如果用户对网页的来源产生混淆并且可能泄露他们不想要的信息这可能会导致攻击。此漏洞影响 Firefox < 88。(CVE-2021-24000

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

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

  - 在 5.14.12 之前版本的 Linux 内核中，kernel/bpf/stackmap.c 中的 prealloc_elems_and_freelist 允许非特权用户触发 eBPF 乘法整数溢出，从而导致越界写入。(CVE-2021-41864)

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

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

  - 已修复 Linux 内核中的下列漏洞：smb: Fix regression in writes when non-standard maximum write size negotiated The conversion to netfs in the 6.3 kernel caused a regression when maximum write size is set by the server to an unexpected value which is not a multiple of 4096 (similarly if the user overrides the maximum write size by setting mount parm wsize, but sets it to a value that is not a multiple of 4096). When negotiated write size is not a multiple of 4096 the netfs code can skip the end of the final page when doing large sequential writes, causing data corruption. This section of code is being rewritten/removed due to a large netfs change, but until that point (ie for the 6.3 kernel until now) we can not support non-standard maximum write sizes. Add a warning if a user specifies a wsize on mount that is not a multiple of 4096 (and round down), also add a change where we round down the maximum write size if the server negotiates a value that is not a multiple of 4096 (we also have to check to make sure that we do not round it down to zero). (CVE-2024-26692)

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

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

  - 已修复 Linux 内核中的下列漏洞：mm: vmalloc: ensure vmap_block is initialised before adding to queue Commit 8c61291fd850 (mm: fix incorrect vbq reference in purge_fragmented_block) extended the 'vmap_block' structure to contain a 'cpu' field which is set at allocation time to the id of the initialising CPU. When a new 'vmap_block' is being instantiated by new_vmap_block(), the partially initialised structure is added to the local 'vmap_block_queue' xarray before the 'cpu' field has been initialised. If another CPU is concurrently walking the xarray (e.g. via vm_unmap_aliases()), then it may perform an out-of-bounds access to the remote queue thanks to an uninitialised index. This has been observed as UBSAN errors in Android: | Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP | | Call trace: | purge_fragmented_block+0x204/0x21c | _vm_unmap_aliases+0x170/0x378 | vm_unmap_aliases+0x1c/0x28 | change_memory_common+0x1dc/0x26c | set_memory_ro+0x18/0x24 | module_enable_ro+0x98/0x238 | do_init_module+0x1b0/0x310 Move the initialisation of 'vb->cpu' in new_vmap_block() ahead of the addition to the xarray. (CVE-2024-46847)

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

ID	名称	严重性
247884	Linux Distros 未修补的漏洞：CVE-2024-21243	low
247883	Linux Distros 未修补的漏洞：CVE-2022-50141	medium
247882	Linux Distros 未修补的漏洞：CVE-2021-38509	medium
247881	Linux Distros 未修补的漏洞：CVE-2024-26789	high
247880	Linux Distros 未修补的漏洞：CVE-2021-3564	medium
247879	Linux Distros 未修补的漏洞：CVE-2022-48956	high
247878	Linux Distros 未修补的漏洞：CVE-2022-21457	medium
247877	Linux Distros 未修补的漏洞：CVE-2021-47329	medium
247876	Linux Distros 未修补的漏洞：CVE-2025-22058	medium
247875	Linux Distros 未修补的漏洞：CVE-2022-49775	high
247874	Linux Distros 未修补的漏洞：CVE-2021-47100	medium
247873	Linux Distros 未修补的漏洞：CVE-2022-49935	high
247872	Linux Distros 未修补的漏洞：CVE-2023-52613	medium
247871	Linux Distros 未修补的漏洞：CVE-2023-52850	medium
247870	Linux Distros 未修补的漏洞：CVE-2016-3163	high
247869	Linux Distros 未修补的漏洞：CVE-2025-21840	medium
247868	Linux Distros 未修补的漏洞：CVE-2025-21911	medium
247867	Linux Distros 未修补的漏洞：CVE-2018-25020	high
247866	Linux Distros 未修补的漏洞：CVE-2025-37871	medium
247865	Linux Distros 未修补的漏洞：CVE-2024-27063	medium
247864	Linux Distros 未修补的漏洞：CVE-2020-6512	high
247863	Linux Distros 未修补的漏洞：CVE-2020-14033	critical
247862	Linux Distros 未修补的漏洞：CVE-2024-38565	medium
247861	Linux Distros 未修补的漏洞：CVE-2023-6213	high
247860	Linux Distros 未修补的漏洞：CVE-2021-47522	medium
247859	Linux Distros 未修补的漏洞：CVE-2024-36892	medium
247858	Linux Distros 未修补的漏洞：CVE-2025-38168	medium
247857	Linux Distros 未修补的漏洞：CVE-2024-44991	medium
247856	Linux Distros 未修补的漏洞：CVE-2021-47515	medium
247855	Linux Distros 未修补的漏洞：CVE-2021-43536	medium
247854	Linux Distros 未修补的漏洞：CVE-2020-10691	medium
247853	Linux Distros 未修补的漏洞：CVE-2022-48808	medium
247852	Linux Distros 未修补的漏洞：CVE-2021-47470	high
247851	Linux Distros 未修补的漏洞：CVE-2022-50038	high
247850	Linux Distros 未修补的漏洞：CVE-2020-12421	medium
247849	Linux Distros 未修补的漏洞：CVE-2022-21425	medium
247848	Linux Distros 未修补的漏洞：CVE-2017-13168	high
247847	Linux Distros 未修补的漏洞：CVE-2023-52874	high
247846	Linux Distros 未修补的漏洞：CVE-2022-48777	medium
247845	Linux Distros 未修补的漏洞：CVE-2021-23995	high
247844	Linux Distros 未修补的漏洞：CVE-2024-26919	medium
247843	Linux Distros 未修补的漏洞：CVE-2024-0123	low
247842	Linux Distros 未修补的漏洞：CVE-2021-3491	high
247841	Linux Distros 未修补的漏洞：CVE-2014-4611	high
247840	Linux Distros 未修补的漏洞：CVE-2022-31743	medium
247839	Linux Distros 未修补的漏洞：CVE-2017-0750	high
247838	Linux Distros 未修补的漏洞：CVE-2021-24000	low
247837	Linux Distros 未修补的漏洞：CVE-2021-41864	high
247818	Linux Distros 未修补的漏洞：CVE-2024-26692	medium
247817	Linux Distros 未修补的漏洞：CVE-2024-46847	medium

检测

Nessus 的 Misc. 系列

low

medium

medium

high

medium

high

medium

medium

medium

high

medium

high

medium

medium

high

medium

medium

high

medium

medium

high

critical

medium

high

medium

medium

medium

medium

medium

medium

medium

medium

high

high

medium

medium

high

high

medium

high

medium

low

high

high

medium

high

low

high

medium

medium