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

  - RISC-V使連接埠 I/O 字串存取子實際運作修正連接埠 I/O 字串存取子 (例如「insb」、「outsb」等)這些存取子使用實體 PCI 連接埠 I/O 位址而不是將對應的記憶體對應至get 至所要求的位置其進而中斷至少我們的 parport 驅動程式對 PCIe 平行連接埠進行的存取例如偵測到 PCI 平行連接埠1415:c118、I/O 位於 0x1000(0x1008)、IRQ 20 parport0: PC- 0x1000 的樣式 (0x1008)irq 20使用 FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP] 造成記憶體存取錯誤無法在虛擬位址 0000000000001008 處處理沒有 uaccess 常式就對使用者記憶體進行的存取錯誤 Oops [#1] 模組連結位置CPU1 PID350 Comm: cat 未受污染 6.0.0-rc2-00283-g10d4879f9ef0-dirty #23 硬體名稱 SiFive HiFive Unmatched A00 (DT) epc
    parport_pc_fifo_write_block_pio+0x266/0x416 ra parport_pc_fifo_write_block_pio+0xb4/0x416 epc
    ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60 gp : ffffffff80fa2700 tp : ffffffd882b1e900 t0 : ffffffd883d0b000 t1 : ffffffffff000002 t2 : 4646393043330a38 s0 : ffffffd88899fcf0 s1 :
    0000000000001000 a0 : 0000000000000010 a1 : 0000000000000000 a2 : ffffffd883d0a010 a3 : 0000000000000023 a4 : 00000000ffff8fbb a5 : ffffffd883d0a001 a6 : 0000000100000000 a7 : ffffffc800000000 s2 :
    ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50 s5 : 0000000000001008 s6 : 0000000000000008 s7 : ffffffd883d0a000 s8 : 0004000000000000 s9 : ffffffff80dc1d80 s10: ffffffd8807e4000 s11:
    0000000000000000 t3 : 00000000000000ff t4 : 393044410a303930 t5 : 0000000000001000 t6 : 0000000000040000 status: 0000000200000120 badaddr: 0000000000001008 cause: 000000000000000f [<ffffffff80543212>] parport_pc_compat_write_block_pio+0xfe/0x200 [<ffffffff8053bbc0>] parport_write+0x46/0xf8 [<ffffffff8050530e>] lp_write+0x158/0x2d2 [<ffffffff80185716>] vfs_write+0x8e/0x2c2 [<ffffffff80185a74>] ksys_write+0x52/0xc2 [<ffffffff80185af2>] sys_write+0xe/0x16 [<ffffffff80003770>] ret_from_syscall+0x0/0x2
    ---[ end trace 0000000000000000 ]--- 為簡單起見解決問題方法是新增 PCI_IOBASE 至僅個別包裝函式巨集所要求的實體位址並觀察如「__insb」、「__outsb」等原始存取子不應由上述巨集使用。移除「addr」上不再需要的「long」轉換為 PCI_IOBASE 現在不再需要它並在「addr」周圍新增可預測評估巨集擴充所需的括號。鑑於目前的程式碼已嚴重損毀且無法正常運作因此無需在個別的變更中進行上述調整。 (CVE-2022-50647)

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

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

  - RISC-V使 端口 I/O 字符串访问器实际工作 修复端口 I/O 字符串访问器如“insb”、“outsb”等此类访问器使用物理 PCI 端口 I/O 地址而不是映射到 的相应内存获得从而反过来至少中断 parport 驱动程序对 PCIe 并行端口进行的访问例如: 0x1000 时的 style (0x1008)irq 20 使用 FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP] 造成内存访问错误没有虚拟地址 0000000000001008 Oops 的 uaccess 例程无法处理对用户内存的内核访问 [#1] 模块中链接了 CPU: 1 PID: 350 Comm: cat Not tainted 6.0.0-rc2-00283-g10d4879f9ef0-dirty #23 硬件名称SiFive HiFive 不匹配 A00 (DT) epc
    parport_pc_fifo_write_block_pio+0x266/0x416 ra parport_pc_fifo_write_block_pio+0xb4/0x416 epc
    ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60 gp : ffffffff80fa2700 tp : ffffffd882b1e900 t0 : ffffffd883d0b000 t1 : ffffffffff000002 t2 : 4646393043330a38 s0 : ffffffd88899fcf0 s1 :
    0000000000001000 a0 : 0000000000000010 a1 : 0000000000000000 a2 : ffffffd883d0a010 a3 : 0000000000000023 a4 : 00000000ffff8fbb a5 : ffffffd883d0a001 a6 : 0000000100000000 a7 : ffffffc800000000 s2 :
    ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50 s5 : 0000000000001008 s6 : 0000000000000008 s7 : ffffffd883d0a000 s8 : 0004000000000000 s9 : ffffffff80dc1d80 s10: ffffffd8807e4000 s11:
    0000000000000000 t3 : 00000000000000ff t4 : 393044410a303930 t5 : 0000000000001000 t6 : 0000000000040000 status: 0000000200000120 badaddr: 0000000000001008 cause: 000000000000000f [<ffffffff80543212>] parport_pc_compat_write_block_pio+0xfe/0x200 [<ffffffff8053bbc0>] parport_write+0x46/0xf8 [<ffffffff8050530e>] lp_write+0x158/0x2d2 [<ffffffff80185716>] vfs_write+0x8e/0x2c2 [<ffffffff80185a74>] ksys_write+0x52/0xc2 [<ffffffff80185af2>] sys_write+0xe/0x16 [<ffffffff80003770>] ret_from_syscall+0x0/0x2
    ---[ 结束跟踪 0000000000000000 ]--- 为简单起见通过仅将 PCI_IOBASE 添加到在相应封装程序宏中请求的物理地址观察未使用“__insb”、“__outsb”等原始访问器来解决此问题。推测会由上述宏以外的人使用。删除“addr”上不再需要的对“long”的转换现在用作 PCI_IOBASE 的偏移并在宏扩展中可预测评估所需的“addr”周围添加括号。鉴于当前代码已严重损坏并且根本无法工作无需在单独的更改中进行上述调整。 (CVE-2022-50647)

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

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

  - RISC-Vポート I/O 文字列アクセサーを実際に動作させます。 に対応するメモリマッピングではなく物理 PCI ポート I/O アドレスを使用する「insb」、「outsb」などのポート I/O 文字列アクセサーを修正しますリクエストされた場所で取得。これにより、parportドライバーによって行われる少なくともPCIeパラレルポートへのアクセスが中断されます。PCIパラレルポートが検出されました1415:c118、I/O at 0x10000x1008、IRQ 20 parport0PC- 0x10000x1008のスタイル、irq 20、FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]を使用、メモリアクセス障害を引き起こす仮想アドレスで uaccess ルーチンなしでユーザーメモリへのカーネルアクセスを処理できません 0000000000001008 Oops [#1] モジュールリンク済み CPU1 PID350 通信cat 汚染されていない 6.0.0-rc2-00283-g10d4879f9ef0-dirty #23 ハードウェア名SiFive HiFive 一致しない A00 DTepc
    parport_pc_fifo_write_block_pio+0x266/0x416 raparport_pc_fifo_write_block_pio+0xb4/0x416 epc
    ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60 gp : ffffffff80fa2700 tp : ffffffd882b1e900 t0 : ffffffd883d0b000 t1 : ffffffffff000002 t2 : 4646393043330a38 s0 : ffffffd88899fcf0 s1 :
    0000000000001000 a0 : 0000000000000010 a1 : 0000000000000000 a2 : ffffffd883d0a010 a3 : 0000000000000023 a4 : 00000000ffff8fbb a5 : ffffffd883d0a001 a6 : 0000000100000000 a7 : ffffffc800000000 s2 :
    ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50 s5 : 0000000000001008 s6 : 0000000000000008 s7 : ffffffd883d0a000 s8 : 0004000000000000 s9 : ffffffff80dc1d80 s10: ffffffd8807e4000 s11:
    0000000000000000 t3 : 00000000000000ff t4 : 393044410a303930 t5 : 0000000000001000 t6 : 0000000000040000 status: 0000000200000120 badaddr: 0000000000001008 cause: 000000000000000f [<ffffffff80543212>] parport_pc_compat_write_block_pio+0xfe/0x200 [<ffffffff8053bbc0>] parport_write+0x46/0xf8 [<ffffffff8050530e>] lp_write+0x158/0x2d2 [<ffffffff80185716>] vfs_write+0x8e/0x2c2 [<ffffffff80185a74>] ksys_write+0x52/0xc2 [<ffffffff80185af2>] sys_write+0xe/0x16 [<ffffffff80003770>] ret_from_syscall+0x0/0x2
    ---[ end trace 000000000000000 ]----- 単純にするために、それぞれのラッパーマクロでのみリクエストされている物理アドレスに PCI_IOBASE を追加することで、問題に対処します。「__insb」、「__outsb」などの raw アクセサーが前述のマクロ以外で使用されることが想定されています。PCI_IOBASE からのオフセットとして使用されるようになったため、「addr」で不要になった「long」へのキャストを削除し、マクロ拡張で予測可能な評価に必要な「addr」に括弧を追加します。現在のコードが大きく破損しており、機能することはないものの、個別の変更で前述の調整を行う必要はありません。CVE-2022-50647

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

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

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

    RISC-V: Make port I/O string accessors actually work

    Fix port I/O string accessors such as `insb', `outsb', etc. which use     the physical PCI port I/O address rather than the corresponding memory     mapping to get at the requested location, which in turn breaks at least     accesses made by our parport driver to a PCIe parallel port such as:

    PCI parallel port detected: 1415:c118, I/O at 0x1000(0x1008), IRQ 20     parport0: PC-style at 0x1000 (0x1008), irq 20, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]

    causing a memory access fault:

    Unable to handle kernel access to user memory without uaccess routines at virtual address 0000000000001008     Oops [#1]     Modules linked in:
    CPU: 1 PID: 350 Comm: cat Not tainted 6.0.0-rc2-00283-g10d4879f9ef0-dirty #23     Hardware name: SiFive HiFive Unmatched A00 (DT)     epc : parport_pc_fifo_write_block_pio+0x266/0x416      ra : parport_pc_fifo_write_block_pio+0xb4/0x416     epc : ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60      gp : ffffffff80fa2700 tp : ffffffd882b1e900 t0 : ffffffd883d0b000      t1 : ffffffffff000002 t2 : 4646393043330a38 s0 : ffffffd88899fcf0      s1 : 0000000000001000 a0 : 0000000000000010 a1 : 0000000000000000      a2 : ffffffd883d0a010 a3 : 0000000000000023 a4 : 00000000ffff8fbb      a5 : ffffffd883d0a001 a6 : 0000000100000000 a7 : ffffffc800000000      s2 : ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50      s5 : 0000000000001008 s6 : 0000000000000008 s7 : ffffffd883d0a000      s8 : 0004000000000000 s9 : ffffffff80dc1d80 s10: ffffffd8807e4000      s11: 0000000000000000 t3 : 00000000000000ff t4 : 393044410a303930      t5 : 0000000000001000 t6 : 0000000000040000     status: 0000000200000120 badaddr: 0000000000001008 cause: 000000000000000f     [<ffffffff80543212>] parport_pc_compat_write_block_pio+0xfe/0x200     [<ffffffff8053bbc0>] parport_write+0x46/0xf8     [<ffffffff8050530e>] lp_write+0x158/0x2d2     [<ffffffff80185716>] vfs_write+0x8e/0x2c2     [<ffffffff80185a74>] ksys_write+0x52/0xc2     [<ffffffff80185af2>] sys_write+0xe/0x16     [<ffffffff80003770>] ret_from_syscall+0x0/0x2
    ---[ end trace 0000000000000000 ]---

    For simplicity address the problem by adding PCI_IOBASE to the physical     address requested in the respective wrapper macros only, observing that     the raw accessors such as `__insb', `__outsb', etc. are not supposed to     be used other than by said macros.  Remove the cast to `long' that is no     longer needed on `addr' now that it is used as an offset from PCI_IOBASE     and add parentheses around `addr' needed for predictable evaluation in     macro expansion.  No need to make said adjustments in separate changes     given that current code is gravely broken and does not ever work.

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.

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

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

    RISC-V: Make port I/O string accessors actually work

    Fix port I/O string accessors such as `insb', `outsb', etc. which use     the physical PCI port I/O address rather than the corresponding memory     mapping to get at the requested location, which in turn breaks at least     accesses made by our parport driver to a PCIe parallel port such as:

    PCI parallel port detected: 1415:c118, I/O at 0x1000(0x1008), IRQ 20     parport0: PC-style at 0x1000 (0x1008), irq 20, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]

    causing a memory access fault:

    Unable to handle kernel access to user memory without uaccess routines at virtual address 0000000000001008     Oops [#1]     Modules linked in:
    CPU: 1 PID: 350 Comm: cat Not tainted 6.0.0-rc2-00283-g10d4879f9ef0-dirty #23     Hardware name: SiFive HiFive Unmatched A00 (DT)     epc : parport_pc_fifo_write_block_pio+0x266/0x416      ra : parport_pc_fifo_write_block_pio+0xb4/0x416     epc : ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60      gp : ffffffff80fa2700 tp : ffffffd882b1e900 t0 : ffffffd883d0b000      t1 : ffffffffff000002 t2 : 4646393043330a38 s0 : ffffffd88899fcf0      s1 : 0000000000001000 a0 : 0000000000000010 a1 : 0000000000000000      a2 : ffffffd883d0a010 a3 : 0000000000000023 a4 : 00000000ffff8fbb      a5 : ffffffd883d0a001 a6 : 0000000100000000 a7 : ffffffc800000000      s2 : ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50      s5 : 0000000000001008 s6 : 0000000000000008 s7 : ffffffd883d0a000      s8 : 0004000000000000 s9 : ffffffff80dc1d80 s10: ffffffd8807e4000      s11: 0000000000000000 t3 : 00000000000000ff t4 : 393044410a303930      t5 : 0000000000001000 t6 : 0000000000040000     status: 0000000200000120 badaddr: 0000000000001008 cause: 000000000000000f     [<ffffffff80543212>] parport_pc_compat_write_block_pio+0xfe/0x200     [<ffffffff8053bbc0>] parport_write+0x46/0xf8     [<ffffffff8050530e>] lp_write+0x158/0x2d2     [<ffffffff80185716>] vfs_write+0x8e/0x2c2     [<ffffffff80185a74>] ksys_write+0x52/0xc2     [<ffffffff80185af2>] sys_write+0xe/0x16     [<ffffffff80003770>] ret_from_syscall+0x0/0x2
    ---[ end trace 0000000000000000 ]---

    For simplicity address the problem by adding PCI_IOBASE to the physical     address requested in the respective wrapper macros only, observing that     the raw accessors such as `__insb', `__outsb', etc. are not supposed to     be used other than by said macros.  Remove the cast to `long' that is no     longer needed on `addr' now that it is used as an offset from PCI_IOBASE     and add parentheses around `addr' needed for predictable evaluation in     macro expansion.  No need to make said adjustments in separate changes     given that current code is gravely broken and does not ever work.

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.

  - RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors such as `insb',     `outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to     get at the requested location, which in turn breaks at least accesses made by our parport driver to a PCIe     parallel port such as: PCI parallel port detected: 1415:c118, I/O at 0x1000(0x1008), IRQ 20 parport0: PC-     style at 0x1000 (0x1008), irq 20, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP] causing a memory access     fault: Unable to handle kernel access to user memory without uaccess routines at virtual address     0000000000001008 Oops [#1] Modules linked in: CPU: 1 PID: 350 Comm: cat Not tainted     6.0.0-rc2-00283-g10d4879f9ef0-dirty #23 Hardware name: SiFive HiFive Unmatched A00 (DT) epc :
    parport_pc_fifo_write_block_pio+0x266/0x416 ra : parport_pc_fifo_write_block_pio+0xb4/0x416 epc :
    ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60 gp : ffffffff80fa2700 tp : ffffffd882b1e900     t0 : ffffffd883d0b000 t1 : ffffffffff000002 t2 : 4646393043330a38 s0 : ffffffd88899fcf0 s1 :
    0000000000001000 a0 : 0000000000000010 a1 : 0000000000000000 a2 : ffffffd883d0a010 a3 : 0000000000000023     a4 : 00000000ffff8fbb a5 : ffffffd883d0a001 a6 : 0000000100000000 a7 : ffffffc800000000 s2 :
    ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50 s5 : 0000000000001008 s6 : 0000000000000008     s7 : ffffffd883d0a000 s8 : 0004000000000000 s9 : ffffffff80dc1d80 s10: ffffffd8807e4000 s11:
    0000000000000000 t3 : 00000000000000ff t4 : 393044410a303930 t5 : 0000000000001000 t6 : 0000000000040000     status: 0000000200000120 badaddr: 0000000000001008 cause: 000000000000000f [<ffffffff80543212>]     parport_pc_compat_write_block_pio+0xfe/0x200 [<ffffffff8053bbc0>] parport_write+0x46/0xf8     [<ffffffff8050530e>] lp_write+0x158/0x2d2 [<ffffffff80185716>] vfs_write+0x8e/0x2c2 [<ffffffff80185a74>]     ksys_write+0x52/0xc2 [<ffffffff80185af2>] sys_write+0xe/0x16 [<ffffffff80003770>] ret_from_syscall+0x0/0x2
    ---[ end trace 0000000000000000 ]--- For simplicity address the problem by adding PCI_IOBASE to the     physical address requested in the respective wrapper macros only, observing that the raw accessors such as     `__insb', `__outsb', etc. are not supposed to be used other than by said macros. Remove the cast to `long'     that is no longer needed on `addr' now that it is used as an offset from PCI_IOBASE and add parentheses     around `addr' needed for predictable evaluation in macro expansion. No need to make said adjustments in     separate changes given that current code is gravely broken and does not ever work. (CVE-2022-50647)

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-2026-007480 advisory.

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

    RISC-V: Make port I/O string accessors actually work

    Fix port I/O string accessors such as `insb', `outsb', etc. which use     the physical PCI port I/O address rather than the corresponding memory     mapping to get at the requested location, which in turn breaks at least     accesses made by our parport driver to a PCIe parallel port such as:

    PCI parallel port detected: 1415:c118, I/O at 0x1000(0x1008), IRQ 20     parport0: PC-style at 0x1000 (0x1008), irq 20, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]

    causing a memory access fault:

    Unable to handle kernel access to user memory without uaccess routines at virtual address 0000000000001008     Oops [#1]     Modules linked in:
    CPU: 1 PID: 350 Comm: cat Not tainted 6.0.0-rc2-00283-g10d4879f9ef0-dirty #23     Hardware name: SiFive HiFive Unmatched A00 (DT)     epc : parport_pc_fifo_write_block_pio+0x266/0x416      ra : parport_pc_fifo_write_block_pio+0xb4/0x416     epc : ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60      gp : ffffffff80fa2700 tp : ffffffd882b1e900 t0 : ffffffd883d0b000      t1 : ffffffffff000002 t2 : 4646393043330a38 s0 : ffffffd88899fcf0      s1 : 0000000000001000 a0 : 0000000000000010 a1 : 0000000000000000      a2 : ffffffd883d0a010 a3 : 0000000000000023 a4 : 00000000ffff8fbb      a5 : ffffffd883d0a001 a6 : 0000000100000000 a7 : ffffffc800000000      s2 : ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50      s5 : 0000000000001008 s6 : 0000000000000008 s7 : ffffffd883d0a000      s8 : 0004000000000000 s9 : ffffffff80dc1d80 s10: ffffffd8807e4000      s11: 0000000000000000 t3 : 00000000000000ff t4 : 393044410a303930      t5 : 0000000000001000 t6 : 0000000000040000     status: 0000000200000120 badaddr: 0000000000001008 cause: 000000000000000f     [<ffffffff80543212>] parport_pc_compat_write_block_pio+0xfe/0x200     [<ffffffff8053bbc0>] parport_write+0x46/0xf8     [<ffffffff8050530e>] lp_write+0x158/0x2d2     [<ffffffff80185716>] vfs_write+0x8e/0x2c2     [<ffffffff80185a74>] ksys_write+0x52/0xc2     [<ffffffff80185af2>] sys_write+0xe/0x16     [<ffffffff80003770>] ret_from_syscall+0x0/0x2
    ---[ end trace 0000000000000000 ]---

    For simplicity address the problem by adding PCI_IOBASE to the physical     address requested in the respective wrapper macros only, observing that     the raw accessors such as `__insb', `__outsb', etc. are not supposed to     be used other than by said macros.  Remove the cast to `long' that is no     longer needed on `addr' now that it is used as an offset from PCI_IOBASE     and add parentheses around `addr' needed for predictable evaluation in     macro expansion.  No need to make said adjustments in separate changes     given that current code is gravely broken and does not ever work.

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
278322	Linux Distros 未修補的弱點：CVE-2022-50647	Nessus	Misc.	2025/12/11	2026/2/3	medium
278322	Linux Distros 未修补的漏洞：CVE-2022-50647	Nessus	Misc.	2025/12/11	2026/2/3	medium
278322	Linux Distros のパッチ未適用の脆弱性: CVE-2022-50647	Nessus	Misc.	2025/12/11	2026/2/3	medium
308807	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-011166)	Nessus	Unity Linux Local Security Checks	2026/4/21	2026/4/22	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	2021/7/22	2026/3/23	high
309226	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-013786)	Nessus	Unity Linux Local Security Checks	2026/4/22	2026/4/26	medium
278322	Linux Distros Unpatched Vulnerability : CVE-2022-50647	Nessus	Misc.	2025/12/11	2026/2/3	medium
307069	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-007480)	Nessus	Unity Linux Local Security Checks	2026/4/17	2026/4/21	medium

检测

插件搜索

medium

medium

medium

medium

high

medium

medium

medium