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

  - f2fs修正以清除 f2fs_evict_inode() 中的已變更 inode。如 Yanming 在 bugzilla 中所報告
    https://bugzilla.kernel.org/show_bug.cgi?id=215904 核心訊息如下所示fs/f2fs/inode.c:825! 的核心錯誤Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 shrink_dentry_list+0x17c/0x4f0 shrink_dcache_parent+0x143/0x1e0 do_one_tree+0x9/0x30 shrink_dcache_for_umount+0x51/0x120 generic_shutdown_super+0x5c/0x3a0 kill_block_super+0x90/0xd0 kill_f2fs_super+0x225/0x310 deactivate_locked_super+ 0x78/0xc0 cleanup_mnt+0x2b7/0x480 task_work_run+0xc8/0x150 exit_to_user_mode_prepare+0x14a/0x150 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0x90 根本原因是inode 節點和 dnodes 節點共用相同的 nid因此在 2dnode_evict 期間節點截斷會使其 NAT 項目失效因此在截斷 inode 節點時會因為無效的 NAT 項目而失敗進而導致 inode 仍標記為已變更請清除 inode 的已變更項目並在檔案系統中設定 SBI_NEED_FSCK 旗標以修正此問題。 dump.f2fs 的輸出[print_node_info: 354] 節點 ID [0xf:15] 為 inode i_nid[0] [0x f: 15] (CVE-2022-49364)

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

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

  - f2fs修复以清除 f2fs_evict_inode() 中的脏 inode 正如 Yanming 在 bugzilla 中报告的
    https://bugzilla.kernel.org/show_bug.cgi?id=215904 内核消息显示如下kernel BUG at fs/f2fs/inode.c:825! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 shrink_dentry_list+0x17c/0x4f0 shrink_dcache_parent+0x143/0x1e0 do_one_tree+0x9/0x30 shrink_dcache_for_umount+0x51/0x120 generic_shutdown_super+0x5c/0x3a0 kill_block_super+0x90/0xd0 kill_f2fs_super+0x225/0x310 deactivate_locked_super+ 0x78/0xc0 cleanup_mnt+0x2b7/0x480 task_work_run+0xc8/0x150 exit_to_user_mode_prepare+0x14a/0x150 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0x90 根本原因为 inode 节点和 dnode 节点共享相同的 nid因此在 f2node_evict_node_evict 期间节点截断会使其 NAT 条目无效因此截断 inode 节点时会因 NAT 条目无效而失败导致 inode 仍被标记为脏请通过清除 inode 的脏并在文件系统中设置 SBI_NEED_FSCK 标记来修复此问题。来自 dump.f2fs 的输出[print_node_info354] 节点 ID [0xf:15] 是 inode i_nid[0] [0x f : 15] (CVE-2022-49364)

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

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

  - f2fsf2fs_evict_inode() のダーティな inode をクリアするために修正します Yanming が bugzilla で報告したように
    https://bugzilla.kernel.org/show_bug.cgi?id=215904 カーネルメッセージは以下のとおりです。fs/f2fs/inode.c:825! でカーネルのバグCall Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 shrink_dentry_list+0x17c/0x4f0 shrink_dcache_parent+0x143/0x1e0 do_one_tree+0x9/0x30 shrink_dcache_for_umount+0x51/0x120 generic_shutdown_super+0x5c/0x3a0 kill_block_super+0x90/0xd0 kill_f2fs_super+0x225/0x310 deactivate_locked_super+ 0x78/0xc0 cleanup_mnt+0x2b7/0x480 task_work_run+0xc8/0x150 exit_to_user_mode_prepare+0x14a/0x150 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0x90 root の原因は次のとおりですinode および dnode 、同じ nid、node を共有しますノード切り捨ては NAT エントリを無効にするため、inode ノードを切り捨てる際には、無効な NAT エントリのために失敗します。結果として inode は依然としてダーティとしてマークされます。inode に対してダーティをクリアし、ファイルシステムに SBI_NEED_FSCK フラグを設定することで、この問題を修正します。 dump.f2fs からの出力[print_node_info: 354] Node ID [0xf:15] は inode i_nid[0] [0x f : 15] ですCVE-2022-49364

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

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - f2fs: fix to clear dirty inode in f2fs_evict_inode() As Yanming reported in bugzilla:
    https://bugzilla.kernel.org/show_bug.cgi?id=215904 The kernel message is shown below: kernel BUG at     fs/f2fs/inode.c:825! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0     shrink_dentry_list+0x17c/0x4f0 shrink_dcache_parent+0x143/0x1e0 do_one_tree+0x9/0x30     shrink_dcache_for_umount+0x51/0x120 generic_shutdown_super+0x5c/0x3a0 kill_block_super+0x90/0xd0     kill_f2fs_super+0x225/0x310 deactivate_locked_super+0x78/0xc0 cleanup_mnt+0x2b7/0x480     task_work_run+0xc8/0x150 exit_to_user_mode_prepare+0x14a/0x150 syscall_exit_to_user_mode+0x1d/0x40     do_syscall_64+0x48/0x90 The root cause is: inode node and dnode node share the same nid, so during     f2fs_evict_inode(), dnode node truncation will invalidate its NAT entry, so when truncating inode node, it     fails due to invalid NAT entry, result in inode is still marked as dirty, fix this issue by clearing dirty     for inode and setting SBI_NEED_FSCK flag in filesystem. output from dump.f2fs: [print_node_info: 354] Node     ID [0xf:15] is inode i_nid[0] [0x f : 15] (CVE-2022-49364)

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-989778 advisory.

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

    f2fs: fix to clear dirty inode in f2fs_evict_inode()

    As Yanming reported in bugzilla:

    https://bugzilla.kernel.org/show_bug.cgi?id=215904

    The kernel message is shown below:

    kernel BUG at fs/f2fs/inode.c:825!     Call Trace:
     evict+0x282/0x4e0
     __dentry_kill+0x2b2/0x4d0      shrink_dentry_list+0x17c/0x4f0      shrink_dcache_parent+0x143/0x1e0      do_one_tree+0x9/0x30      shrink_dcache_for_umount+0x51/0x120      generic_shutdown_super+0x5c/0x3a0      kill_block_super+0x90/0xd0      kill_f2fs_super+0x225/0x310      deactivate_locked_super+0x78/0xc0      cleanup_mnt+0x2b7/0x480      task_work_run+0xc8/0x150      exit_to_user_mode_prepare+0x14a/0x150      syscall_exit_to_user_mode+0x1d/0x40      do_syscall_64+0x48/0x90

    The root cause is: inode node and dnode node share the same nid,     so during f2fs_evict_inode(), dnode node truncation will invalidate     its NAT entry, so when truncating inode node, it fails due to     invalid NAT entry, result in inode is still marked as dirty, fix     this issue by clearing dirty for inode and setting SBI_NEED_FSCK     flag in filesystem.

    output from dump.f2fs:
    [print_node_info: 354] Node ID [0xf:15] is inode     i_nid[0]                                [0x       f : 15]

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-2025-988977 advisory.

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

    f2fs: fix to clear dirty inode in f2fs_evict_inode()

    As Yanming reported in bugzilla:

    https://bugzilla.kernel.org/show_bug.cgi?id=215904

    The kernel message is shown below:

    kernel BUG at fs/f2fs/inode.c:825!     Call Trace:
     evict+0x282/0x4e0
     __dentry_kill+0x2b2/0x4d0      shrink_dentry_list+0x17c/0x4f0      shrink_dcache_parent+0x143/0x1e0      do_one_tree+0x9/0x30      shrink_dcache_for_umount+0x51/0x120      generic_shutdown_super+0x5c/0x3a0      kill_block_super+0x90/0xd0      kill_f2fs_super+0x225/0x310      deactivate_locked_super+0x78/0xc0      cleanup_mnt+0x2b7/0x480      task_work_run+0xc8/0x150      exit_to_user_mode_prepare+0x14a/0x150      syscall_exit_to_user_mode+0x1d/0x40      do_syscall_64+0x48/0x90

    The root cause is: inode node and dnode node share the same nid,     so during f2fs_evict_inode(), dnode node truncation will invalidate     its NAT entry, so when truncating inode node, it fails due to     invalid NAT entry, result in inode is still marked as dirty, fix     this issue by clearing dirty for inode and setting SBI_NEED_FSCK     flag in filesystem.

    output from dump.f2fs:
    [print_node_info: 354] Node ID [0xf:15] is inode     i_nid[0]                                [0x       f : 15]

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	名称	产品	系列	发布时间	最近更新时间	严重程度
225313	Linux Distros 未修補的弱點：CVE-2022-49364	Nessus	Misc.	2025/3/5	2025/10/28	medium
225313	Linux Distros 未修补的漏洞：CVE-2022-49364	Nessus	Misc.	2025/3/5	2025/10/28	medium
225313	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49364	Nessus	Misc.	2025/3/5	2025/10/28	medium
225313	Linux Distros Unpatched Vulnerability : CVE-2022-49364	Nessus	Misc.	2025/3/5	2025/10/28	medium
272869	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989778)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	2021/7/22	2026/3/23	high
275906	TencentOS Server 4: kernel (TSSA-2025:0346)	Nessus	Tencent Local Security Checks	2025/11/20	2026/3/11	high
273389	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988977)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	medium

检测

插件搜索

medium

medium

medium

medium

medium

high

high

medium