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

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.

ID	Name	Product	Family	Published	Updated	Severity
225313	Linux Distros Unpatched Vulnerability : CVE-2022-49364	Nessus	Misc.	3/5/2025	10/28/2025	medium
273389	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988977)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	medium
272869	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989778)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	3/23/2026	high
275906	TencentOS Server 4: kernel (TSSA-2025:0346)	Nessus	Tencent Local Security Checks	11/20/2025	3/11/2026	high

Detections

Analytics

Plugins Search

medium

medium

medium

high

high