Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - riscv修正保留的記憶體設定。目前 RISC-V 使用裝置樹狀結構的早期復本來設定保留的記憶體。因此當嘗試使用 of_reserved_mem_lookup() 取得保留的記憶體區域時保留記憶體區域的指標會使用較早的虛擬記憶體之前位址這會在嘗試使用緩衝區的名稱時造成核心錯誤無法處理虛擬位址 00000000401c31ac 的核心分頁要求 Oops [#1] 連結的模組CPU0 PID0 Commswapper 未受污染的 6.0.0-rc1-00001-g0d9d6953d834 #1 硬體名稱Microchip PolarFire-SoC Icicle Kit (DT) epc
    string+0x4a/0xea ra vsnprintf+0x1e4/0x336 epc ffffffff80335ea0 ra ffffffff80338936 sp
    ffffffff81203be0 gp : ffffffff812e0a98 tp : ffffffff8120de40 t0 : 0000000000000000 t1 : ffffffff81203e28 t2 : 7265736572203a46 s0 : ffffffff81203c20 s1 : ffffffff81203e28 a0 : ffffffff81203d22 a1 :
    0000000000000000 a2 : ffffffff81203d08 a3 : 0000000081203d21 a4 : ffffffffffffffff a5 : 00000000401c31ac a6 : ffff0a00ffffff04 a7 : ffffffffffffffff s2 : ffffffff81203d08 s3 : ffffffff81203d00 s4 :
    0000000000000008 s5 : ffffffff000000ff s6 : 0000000000ffffff s7 : 00000000ffffff00 s8 : ffffffff80d9821a s9 : ffffffff81203d22 s10: 0000000000000002 s11: ffffffff80d9821c t3 : ffffffff812f3617 t4 :
    ffffffff812f3617 t5 ffffffff812f3618 t6 ffffffff81203d08 狀態0000000200000100 badaddr
    00000000401c31ac 原因 000000000000000d [<ffffffff80338936>] vsnprintf+0x1e4/0x336 [<ffffffff80055ae2>] vprintk_store+0xf6/0x344 [<ffffffff80055d86>] vprintk_emit+0x56/0x192 [<ffffffff80055ed8>] vprintk_default+0x16/0x1e [<ffffffff800563d2>] 80 [k+0x72/0]<ffffffff806813b2>] _printk+0x36/0x50 [<ffffffff8068af48>] print_reserved_mem+0x1c/0x24 [<ffffffff808057ec>] paging_init+0x528/0x5bc [<ffffffff808031ae>] setup_arch+0xd0/0x592 [<ffffffff8080070e>] start_kernel+0x82/0x73c early_init_fdt_scan_reserved_mem() 不接受引數因為它在由 early_init_dt_verify() 填入的initial_boot_params 上執行。在 RISC-V 上系統呼叫了 early_init_dt_verify() 兩次。在未啟用 CONFIG_BUILTIN_DTB 的情況下直接在 setup_arch() 中一次和在開機處理程序的非常早期呼叫 early_init_dt_scan_nodes() 時間接在 setup_arch() 中一次。此第一個呼叫使用 dtb_early_va 來設定initial_boot_params其無法在稍後呼叫 early_init_fdt_scan_reserved_mem() 時用於開機處理程序。例如在 arm64 上early_init_dt_scan_nodes() 的對應呼叫會使用 fixmap 位址因此不會受到相同影響。在 setup_arch() 中直接呼叫 early_init_dt_verify() 之後沿著開機序列進一步移動 early_init_fdt_scan_reserved_mem()以便名稱使用正確的虛擬記憶體位址。上述假設未設定 CONFIG_BUILTIN_DTB但在設定的情況下應同樣運作 - unflatted_and_copy_device_tree() 也會更新initial_boot_params。
    (CVE-2022-49851)

請注意，Nessus 依賴供應商報告的套件存在。

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

  - riscv修复预留内存设置 目前RISC-V 使用设备树的早期副本设置预留内存。因此当尝试使用 of_reserved_mem_lookup() 获取保留内存区域时指向保留内存区域的指针使用较早的虚拟内存前地址在尝试使用缓冲区的名称时会造成内核错误无法处理虚拟地址 00000000401c31ac 上的内核分页请求 Oops [#1] 链接的模块CPU:0 PID: 0 Comm: swapper 未受感染 6.0.0-rc1-00001-g0d9d6953d834 #1 硬件名称Microchip PolarFire-SoC Icicle 套件 (DT) epc
    string+0x4a/0xea ra : vsnprintf+0x1e4/0x336 epc : ffffffff80335ea0 ra : ffffffff80338936 sp
    ffffffff81203be0 gp : ffffffff812e0a98 tp : ffffffff8120de40 t0 : 0000000000000000 t1 : ffffffff81203e28 t2 : 7265736572203a46 s0 : ffffffff81203c20 s1 : ffffffff81203e28 a0 : ffffffff81203d22 a1 :
    0000000000000000 a2 : ffffffff81203d08 a3 : 0000000081203d21 a4 : ffffffffffffffff a5 : 00000000401c31ac a6 : ffff0a00ffffff04 a7 : ffffffffffffffff s2 : ffffffff81203d08 s3 : ffffffff81203d00 s4 :
    0000000000000008 s5 : ffffffff000000ff s6 : 0000000000ffffff s7 : 00000000ffffff00 s8 : ffffffff80d9821a s9 : ffffffff81203d22 s10: 0000000000000002 s11: ffffffff80d9821c t3 : ffffffff812f3617 t4 :
    ffffffff812f3617 t5ffffffff812f3618 t6ffffffff81203d08 status0000000200000100 badaddr
    00000000401c31ac 原因000000000000000d [<ffffffff80338936>] vsnprintf+0x1e4/0x336 [<ffffffff80055ae2>] vprintk_store+0xf6/0x344 [<ffffffff80055d86>] vprintk_emit+0x56/0x192 [<ffffffff80055ed8>] vprintk_default+0x16/0x1e [<ffffffff800563d2>] vprint/k_default+0x16/0x1e [ [] ]<ffffffff806813b2>] _printk+0x36/0x50 [<ffffffff8068af48>] print_reserved_mem+0x1c/0x24 [<ffffffff808057ec>] paging_init+0x528/0x5bc [<ffffffff808031ae>] setup_arch+0xd0/0x592 [<ffffffff8080070e>] start_kernel+0x82/0x73c early_init_fdt_scan_reserved_mem() 不使用任何参数因为它在初始_boot_params 由 early_init_dt_verify() 填充的 上运行。在 RISC-V 上 early_init_dt_verify() 被调用两次。一次是直接在 setup_arch() 中如果未启用 CONFIG_BUILTIN_DTB 一次是间接一次在引导进程的很早阶段由 parse_dtb() 当调用 early_init_dt_scan_nodes() 时执行。此第一次调用使用 dtb_early_va 来设置initial_boot_params该参数随后在引导过程中调用 early_init_fdt_scan_reserved_mem() 时无法使用。例如在 arm64 上对 early_init_dt_scan_nodes() 的相应调用使用 fixmap 地址并且不会遭受同样的结果。在直接调用 setup_arch() 中的 early_init_dt_verify() 之后进一步移动 early_init_fdt_scan_reserved_mem() 至引导序列以便名称使用正确的虚拟内存地址。上面假设未设置 CONFIG_BUILTIN_DTB但在设置的情况下应同样工作 - unflatted_and_copy_device_tree() 也会更新initial_boot_params。
    (CVE-2022-49851)

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

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - riscv予約済みメモリセットアップを修正します。現在、RISC-V はデバイスツリーの早期コピーを使用して予約済みメモリを設定します。その結果、of_reserved_mem_lookup() を使用して予約されたメモリ領域を取得しようとすると、予約されたメモリ領域へのポインターは、早期の pre-virtual-memory アドレスを使用するため、バッファの名前を使用しようとする際に、カーネルパニックを引き起こします: 処理できない仮想アドレスでのカーネルページングリクエスト 00000000401c31ac Oops [#1] リンクされているモジュール CPU:0 PID:0 通信: swapper 汚染されていない 6.0.0-rc1-00001-g0d9d6953d834 #1 ハードウェア名: Microchip PolarFire-SoC Icicle KitDT epc
    string+0x4a/0xea ra : vsnprintf+0x1e4/0x336 epc : ffffffff80335ea0 ra : ffffffff80338936 sp :
    ffffffff81203be0 gp : ffffffff812e0a98 tp : ffffffff8120de40 t0 : 0000000000000000 t1 : ffffffff81203e28 t2 : 7265736572203a46 s0 : ffffffff81203c20 s1 : ffffffff81203e28 a0 : ffffffff81203d22 a1 :
    0000000000000000 a2 : ffffffff81203d08 a3 : 0000000081203d21 a4 : ffffffffffffffff a5 : 00000000401c31ac a6 : ffff0a00ffffff04 a7 : ffffffffffffffff s2 : ffffffff81203d08 s3 : ffffffff81203d00 s4 :
    0000000000000008 s5 : ffffffff000000ff s6 : 0000000000ffffff s7 : 00000000ffffff00 s8 : ffffffff80d9821a s9 : ffffffff81203d22 s10: 0000000000000002 s11: ffffffff80d9821c t3 : ffffffff812f3617 t4 :
    ffffffff812f3617 t5 ffffffff812f3618 t6 ffffffff81203d08 ステータス0000000200000100 badaddr
    00000000401c31acsource: 00000000000000d<ffffffff80338936>] vsnprintf+0x1e4/0x336<ffffffff80055ae2>] vprintk_store+0xf6/0x344<ffffffff80055d86>] vprintk_emit+0x56/0x192 [<ffffffff80055ed8> ] vprintk_default+0x16/0x1e [<ffffffff800563d2>] vprintk_default+0x16/0x1e []<ffffffff806813b2>] _printk+0x36/0x50 [<ffffffff8068af48>] print_reserved_mem+0x1c/0x24 [<ffffffff808057ec>] paging_init+0x528/0x5bc [<ffffffff808031ae>] setup_arch+0xd0/0x592 [<ffffffff8080070e>] start_kernel+0x82/0x73c early_init_fdt_scan_reserved_mem() に引数はありませんこれは、early_init_dt_verify() によって初期化される initial_boot_params で動作します。RISC-V で、early_init_dt_verify() が 2 回呼び出されます。CONFIG_BUILTIN_DTB が有効でない場合、setup_arch() 内で 1 度直接、また1 度間接的に、early_init_dt_scan_nodes() を呼び出すときの parse_dtb() によって、起動プロセスの非常に早い段階で。この最初の呼び出しでは、dtb_early_va を使用して initial_boot_params を設定します。これは、early_init_fdt_scan_reserved_mem() が呼び出されたときの起動プロセスで、使用できません。たとえば、arm64 では、 early_init_dt_scan_nodes() に対応する呼び出しが fixmap アドレスを使用し、同じ状況ではありません。setup_arch() の early_init_dt_verify() を直接呼び出した後に、起動シーケンスに沿って early_init_fdt_scan_reserved_mem() をさらに移動し、名前が正しい仮想メモリアドレスを使用するようにします。上記では、CONFIG_BUILTIN_DTB が設定されていないと仮定しましたが、設定されている場合でも同様に動作するはずです。- unflated_and_copy_device_tree() は、initial_boot_params も更新します。
    (CVE-2022-49851)

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-990750 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    riscv: fix reserved memory setup

    Currently, RISC-V sets up reserved memory using the early copy of the     device tree. As a result, when trying to get a reserved memory region     using of_reserved_mem_lookup(), the pointer to reserved memory regions     is using the early, pre-virtual-memory address which causes a kernel     panic when trying to use the buffer's name:

     Unable to handle kernel paging request at virtual address 00000000401c31ac      Oops [#1]      Modules linked in:
     CPU: 0 PID: 0 Comm: swapper Not tainted 6.0.0-rc1-00001-g0d9d6953d834 #1      Hardware name: Microchip PolarFire-SoC Icicle Kit (DT)      epc : string+0x4a/0xea       ra : vsnprintf+0x1e4/0x336      epc : ffffffff80335ea0 ra : ffffffff80338936 sp : ffffffff81203be0       gp : ffffffff812e0a98 tp : ffffffff8120de40 t0 : 0000000000000000       t1 : ffffffff81203e28 t2 : 7265736572203a46 s0 : ffffffff81203c20       s1 : ffffffff81203e28 a0 : ffffffff81203d22 a1 : 0000000000000000       a2 : ffffffff81203d08 a3 : 0000000081203d21 a4 : ffffffffffffffff       a5 : 00000000401c31ac a6 : ffff0a00ffffff04 a7 : ffffffffffffffff       s2 : ffffffff81203d08 s3 : ffffffff81203d00 s4 : 0000000000000008       s5 : ffffffff000000ff s6 : 0000000000ffffff s7 : 00000000ffffff00       s8 : ffffffff80d9821a s9 : ffffffff81203d22 s10: 0000000000000002       s11: ffffffff80d9821c t3 : ffffffff812f3617 t4 : ffffffff812f3617       t5 : ffffffff812f3618 t6 : ffffffff81203d08      status: 0000000200000100 badaddr: 00000000401c31ac cause: 000000000000000d      [<ffffffff80338936>] vsnprintf+0x1e4/0x336      [<ffffffff80055ae2>] vprintk_store+0xf6/0x344      [<ffffffff80055d86>] vprintk_emit+0x56/0x192      [<ffffffff80055ed8>] vprintk_default+0x16/0x1e      [<ffffffff800563d2>] vprintk+0x72/0x80      [<ffffffff806813b2>] _printk+0x36/0x50      [<ffffffff8068af48>] print_reserved_mem+0x1c/0x24      [<ffffffff808057ec>] paging_init+0x528/0x5bc      [<ffffffff808031ae>] setup_arch+0xd0/0x592      [<ffffffff8080070e>] start_kernel+0x82/0x73c

    early_init_fdt_scan_reserved_mem() takes no arguments as it operates on     initial_boot_params, which is populated by early_init_dt_verify(). On     RISC-V, early_init_dt_verify() is called twice. Once, directly, in     setup_arch() if CONFIG_BUILTIN_DTB is not enabled and once indirectly,     very early in the boot process, by parse_dtb() when it calls     early_init_dt_scan_nodes().

    This first call uses dtb_early_va to set initial_boot_params, which is     not usable later in the boot process when     early_init_fdt_scan_reserved_mem() is called. On arm64 for example, the     corresponding call to early_init_dt_scan_nodes() uses fixmap addresses     and doesn't suffer the same fate.

    Move early_init_fdt_scan_reserved_mem() further along the boot sequence,     after the direct call to early_init_dt_verify() in setup_arch() so that     the names use the correct virtual memory addresses. The above supposed     that CONFIG_BUILTIN_DTB was not set, but should work equally in the case     where it is - unflatted_and_copy_device_tree() also updates     initial_boot_params.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue 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.

  - riscv: fix reserved memory setup Currently, RISC-V sets up reserved memory using the early copy of the     device tree. As a result, when trying to get a reserved memory region using of_reserved_mem_lookup(), the     pointer to reserved memory regions is using the early, pre-virtual-memory address which causes a kernel     panic when trying to use the buffer's name: Unable to handle kernel paging request at virtual address     00000000401c31ac Oops [#1] Modules linked in: CPU: 0 PID: 0 Comm: swapper Not tainted     6.0.0-rc1-00001-g0d9d6953d834 #1 Hardware name: Microchip PolarFire-SoC Icicle Kit (DT) epc :
    string+0x4a/0xea ra : vsnprintf+0x1e4/0x336 epc : ffffffff80335ea0 ra : ffffffff80338936 sp :
    ffffffff81203be0 gp : ffffffff812e0a98 tp : ffffffff8120de40 t0 : 0000000000000000 t1 : ffffffff81203e28     t2 : 7265736572203a46 s0 : ffffffff81203c20 s1 : ffffffff81203e28 a0 : ffffffff81203d22 a1 :
    0000000000000000 a2 : ffffffff81203d08 a3 : 0000000081203d21 a4 : ffffffffffffffff a5 : 00000000401c31ac     a6 : ffff0a00ffffff04 a7 : ffffffffffffffff s2 : ffffffff81203d08 s3 : ffffffff81203d00 s4 :
    0000000000000008 s5 : ffffffff000000ff s6 : 0000000000ffffff s7 : 00000000ffffff00 s8 : ffffffff80d9821a     s9 : ffffffff81203d22 s10: 0000000000000002 s11: ffffffff80d9821c t3 : ffffffff812f3617 t4 :
    ffffffff812f3617 t5 : ffffffff812f3618 t6 : ffffffff81203d08 status: 0000000200000100 badaddr:
    00000000401c31ac cause: 000000000000000d [<ffffffff80338936>] vsnprintf+0x1e4/0x336 [<ffffffff80055ae2>]     vprintk_store+0xf6/0x344 [<ffffffff80055d86>] vprintk_emit+0x56/0x192 [<ffffffff80055ed8>]     vprintk_default+0x16/0x1e [<ffffffff800563d2>] vprintk+0x72/0x80 [<ffffffff806813b2>] _printk+0x36/0x50     [<ffffffff8068af48>] print_reserved_mem+0x1c/0x24 [<ffffffff808057ec>] paging_init+0x528/0x5bc     [<ffffffff808031ae>] setup_arch+0xd0/0x592 [<ffffffff8080070e>] start_kernel+0x82/0x73c     early_init_fdt_scan_reserved_mem() takes no arguments as it operates on initial_boot_params, which is     populated by early_init_dt_verify(). On RISC-V, early_init_dt_verify() is called twice. Once, directly, in     setup_arch() if CONFIG_BUILTIN_DTB is not enabled and once indirectly, very early in the boot process, by     parse_dtb() when it calls early_init_dt_scan_nodes(). This first call uses dtb_early_va to set     initial_boot_params, which is not usable later in the boot process when early_init_fdt_scan_reserved_mem()     is called. On arm64 for example, the corresponding call to early_init_dt_scan_nodes() uses fixmap     addresses and doesn't suffer the same fate. Move early_init_fdt_scan_reserved_mem() further along the boot     sequence, after the direct call to early_init_dt_verify() in setup_arch() so that the names use the     correct virtual memory addresses. The above supposed that CONFIG_BUILTIN_DTB was not set, but should work     equally in the case where it is - unflatted_and_copy_device_tree() also updates initial_boot_params.
    (CVE-2022-49851)

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-992781 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    riscv: fix reserved memory setup

    Currently, RISC-V sets up reserved memory using the early copy of the     device tree. As a result, when trying to get a reserved memory region     using of_reserved_mem_lookup(), the pointer to reserved memory regions     is using the early, pre-virtual-memory address which causes a kernel     panic when trying to use the buffer's name:

     Unable to handle kernel paging request at virtual address 00000000401c31ac      Oops [#1]      Modules linked in:
     CPU: 0 PID: 0 Comm: swapper Not tainted 6.0.0-rc1-00001-g0d9d6953d834 #1      Hardware name: Microchip PolarFire-SoC Icicle Kit (DT)      epc : string+0x4a/0xea       ra : vsnprintf+0x1e4/0x336      epc : ffffffff80335ea0 ra : ffffffff80338936 sp : ffffffff81203be0       gp : ffffffff812e0a98 tp : ffffffff8120de40 t0 : 0000000000000000       t1 : ffffffff81203e28 t2 : 7265736572203a46 s0 : ffffffff81203c20       s1 : ffffffff81203e28 a0 : ffffffff81203d22 a1 : 0000000000000000       a2 : ffffffff81203d08 a3 : 0000000081203d21 a4 : ffffffffffffffff       a5 : 00000000401c31ac a6 : ffff0a00ffffff04 a7 : ffffffffffffffff       s2 : ffffffff81203d08 s3 : ffffffff81203d00 s4 : 0000000000000008       s5 : ffffffff000000ff s6 : 0000000000ffffff s7 : 00000000ffffff00       s8 : ffffffff80d9821a s9 : ffffffff81203d22 s10: 0000000000000002       s11: ffffffff80d9821c t3 : ffffffff812f3617 t4 : ffffffff812f3617       t5 : ffffffff812f3618 t6 : ffffffff81203d08      status: 0000000200000100 badaddr: 00000000401c31ac cause: 000000000000000d      [<ffffffff80338936>] vsnprintf+0x1e4/0x336      [<ffffffff80055ae2>] vprintk_store+0xf6/0x344      [<ffffffff80055d86>] vprintk_emit+0x56/0x192      [<ffffffff80055ed8>] vprintk_default+0x16/0x1e      [<ffffffff800563d2>] vprintk+0x72/0x80      [<ffffffff806813b2>] _printk+0x36/0x50      [<ffffffff8068af48>] print_reserved_mem+0x1c/0x24      [<ffffffff808057ec>] paging_init+0x528/0x5bc      [<ffffffff808031ae>] setup_arch+0xd0/0x592      [<ffffffff8080070e>] start_kernel+0x82/0x73c

    early_init_fdt_scan_reserved_mem() takes no arguments as it operates on     initial_boot_params, which is populated by early_init_dt_verify(). On     RISC-V, early_init_dt_verify() is called twice. Once, directly, in     setup_arch() if CONFIG_BUILTIN_DTB is not enabled and once indirectly,     very early in the boot process, by parse_dtb() when it calls     early_init_dt_scan_nodes().

    This first call uses dtb_early_va to set initial_boot_params, which is     not usable later in the boot process when     early_init_fdt_scan_reserved_mem() is called. On arm64 for example, the     corresponding call to early_init_dt_scan_nodes() uses fixmap addresses     and doesn't suffer the same fate.

    Move early_init_fdt_scan_reserved_mem() further along the boot sequence,     after the direct call to early_init_dt_verify() in setup_arch() so that     the names use the correct virtual memory addresses. The above supposed     that CONFIG_BUILTIN_DTB was not set, but should work equally in the case     where it is - unflatted_and_copy_device_tree() also updates     initial_boot_params.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

An update of the linux package has been released.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
250040	Linux Distros 未修補的弱點：CVE-2022-49851	Nessus	Misc.	2025/8/15	2026/1/14	high
250040	Linux Distros 未修补的漏洞：CVE-2022-49851	Nessus	Misc.	2025/8/15	2026/1/14	high
250040	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49851	Nessus	Misc.	2025/8/15	2026/1/14	high
275102	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-990750)	Nessus	Unity Linux Local Security Checks	2025/11/12	2025/11/12	high
297592	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1224)	Nessus	Huawei Local Security Checks	2026/2/2	2026/2/4	high
302971	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2026-1629)	Nessus	Huawei Local Security Checks	2026/3/18	2026/3/18	high
297598	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1212)	Nessus	Huawei Local Security Checks	2026/2/2	2026/2/4	high
250040	Linux Distros Unpatched Vulnerability : CVE-2022-49851	Nessus	Misc.	2025/8/15	2026/1/14	high
281266	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-992781)	Nessus	Unity Linux Local Security Checks	2025/12/31	2025/12/31	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	2021/7/22	2026/3/23	high
302981	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2026-1637)	Nessus	Huawei Local Security Checks	2026/3/18	2026/3/18	high

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high