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 do sanity check on destination blkaddr during recovery As Wenqing Liu reported in bugzilla:
    https://bugzilla.kernel.org/show_bug.cgi?id=216456 loop5: detected capacity change from 0 to 131072 F2FS-     fs (loop5): recover_inode: ino = 6, name = hln, inline = 1 F2FS-fs (loop5): recover_data: ino = 6 (i_size:
    recover) err = 0 F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1 F2FS-fs (loop5):
    recover_data: ino = 6 (i_size: recover) err = 0 F2FS-fs (loop5): recover_inode: ino = 6, name = hln,     inline = 1 F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0 F2FS-fs (loop5): Bitmap was     wrongly set, blk:5634 ------------[ cut here ]------------ WARNING: CPU: 3 PID: 1013 at     fs/f2fs/segment.c:2198 RIP: 0010:update_sit_entry+0xa55/0x10b0 [f2fs] Call Trace: <TASK>     f2fs_do_replace_block+0xa98/0x1890 [f2fs] f2fs_replace_block+0xeb/0x180 [f2fs] recover_data+0x1a69/0x6ae0     [f2fs] f2fs_recover_fsync_data+0x120d/0x1fc0 [f2fs] f2fs_fill_super+0x4665/0x61e0 [f2fs]     mount_bdev+0x2cf/0x3b0 legacy_get_tree+0xed/0x1d0 vfs_get_tree+0x81/0x2b0 path_mount+0x47e/0x19d0     do_mount+0xce/0xf0 __x64_sys_mount+0x12c/0x1a0 do_syscall_64+0x38/0x90     entry_SYSCALL_64_after_hwframe+0x63/0xcd If we enable CONFIG_F2FS_CHECK_FS config, it will trigger a     kernel panic instead of warning. The root cause is: in fuzzed image, SIT table is inconsistent with inode     mapping table, result in triggering such warning during SIT table update. This patch introduces a new flag     DATA_GENERIC_ENHANCE_UPDATE, w/ this flag, data block recovery flow can check destination blkaddr's     validation in SIT table, and skip f2fs_replace_block() to avoid inconsistent status. (CVE-2022-50273)

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

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

    f2fs: fix to do sanity check on destination blkaddr during recovery

    As Wenqing Liu reported in bugzilla:

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

    loop5: detected capacity change from 0 to 131072     F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1     F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0     F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1     F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0     F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1     F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0     F2FS-fs (loop5): Bitmap was wrongly set, blk:5634
    ------------[ cut here ]------------     WARNING: CPU: 3 PID: 1013 at fs/f2fs/segment.c:2198     RIP: 0010:update_sit_entry+0xa55/0x10b0 [f2fs]     Call Trace:
     <TASK>      f2fs_do_replace_block+0xa98/0x1890 [f2fs]      f2fs_replace_block+0xeb/0x180 [f2fs]      recover_data+0x1a69/0x6ae0 [f2fs]      f2fs_recover_fsync_data+0x120d/0x1fc0 [f2fs]      f2fs_fill_super+0x4665/0x61e0 [f2fs]      mount_bdev+0x2cf/0x3b0      legacy_get_tree+0xed/0x1d0      vfs_get_tree+0x81/0x2b0      path_mount+0x47e/0x19d0      do_mount+0xce/0xf0
     __x64_sys_mount+0x12c/0x1a0      do_syscall_64+0x38/0x90      entry_SYSCALL_64_after_hwframe+0x63/0xcd

    If we enable CONFIG_F2FS_CHECK_FS config, it will trigger a kernel panic     instead of warning.

    The root cause is: in fuzzed image, SIT table is inconsistent with inode     mapping table, result in triggering such warning during SIT table update.

    This patch introduces a new flag DATA_GENERIC_ENHANCE_UPDATE, w/ this     flag, data block recovery flow can check destination blkaddr's validation     in SIT table, and skip f2fs_replace_block() to avoid inconsistent status.

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

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

    f2fs: fix to do sanity check on destination blkaddr during recovery

    As Wenqing Liu reported in bugzilla:

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

    loop5: detected capacity change from 0 to 131072     F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1     F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0     F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1     F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0     F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1     F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0     F2FS-fs (loop5): Bitmap was wrongly set, blk:5634
    ------------[ cut here ]------------     WARNING: CPU: 3 PID: 1013 at fs/f2fs/segment.c:2198     RIP: 0010:update_sit_entry+0xa55/0x10b0 [f2fs]     Call Trace:
     <TASK>      f2fs_do_replace_block+0xa98/0x1890 [f2fs]      f2fs_replace_block+0xeb/0x180 [f2fs]      recover_data+0x1a69/0x6ae0 [f2fs]      f2fs_recover_fsync_data+0x120d/0x1fc0 [f2fs]      f2fs_fill_super+0x4665/0x61e0 [f2fs]      mount_bdev+0x2cf/0x3b0      legacy_get_tree+0xed/0x1d0      vfs_get_tree+0x81/0x2b0      path_mount+0x47e/0x19d0      do_mount+0xce/0xf0
     __x64_sys_mount+0x12c/0x1a0      do_syscall_64+0x38/0x90      entry_SYSCALL_64_after_hwframe+0x63/0xcd

    If we enable CONFIG_F2FS_CHECK_FS config, it will trigger a kernel panic     instead of warning.

    The root cause is: in fuzzed image, SIT table is inconsistent with inode     mapping table, result in triggering such warning during SIT table update.

    This patch introduces a new flag DATA_GENERIC_ENHANCE_UPDATE, w/ this     flag, data block recovery flow can check destination blkaddr's validation     in SIT table, and skip f2fs_replace_block() to avoid inconsistent status.

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	Name	Product	Family	Published	Updated	Severity
265170	Linux Distros Unpatched Vulnerability : CVE-2022-50273	Nessus	Misc.	9/17/2025	7/17/2026	medium
280632	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992314)	Nessus	Unity Linux Local Security Checks	12/30/2025	12/30/2025	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	9/15/2026	high
281340	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-992745)	Nessus	Unity Linux Local Security Checks	12/31/2025	12/31/2025	medium

Detections

Analytics

Plugins Search

medium

medium

high

medium