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

  - f2fs：修复以在恢复期间对目标 blkaddr 进行健全性检查 正如 Wenqing Liu 在 bugzilla 中报告的：
    https://bugzilla.kernel.org/show_bug.cgi?id=216456 loop5：检测到的容量从 0 变化到 131072 F2FS-fs （loop5）：recover_inode：ino = 6，名称 = hln，内联 = 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）： 位图设置错误， blk：5634 ------------[ cut here ]------------ WARNING： CPU： 3 PID： 1013 at fs/f2fs/segment.c：2198 RIP： 0010：update_sit_entry+0xa55/0x10b0 [f2fs] 调用跟踪： <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 如果启用CONFIG_F2FS_CHECK_FS配置，这将触发内核错误而非警告。根本原因是：在模糊图像中，SIT 表与 inode 映射表不一致，导致在 SIT 表更新期间触发此类警告。此修补程序引入了一个新标记DATA_GENERIC_ENHANCE_UPDATE，通过此标记，数据块恢复流可检查 SIT 表中的目标 blkaddr 验证，并跳过 f2fs_replace_block（） 以避免状态不一致。（CVE-2022-50273）

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

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

  - f2fs：修正在復原期間對目的地 blkaddr 進行健全性檢查 正如 Wenqing Liu 在 bugzilla 中報告的那樣：
    https://bugzilla.kernel.org/show_bug.cgi?id=216456 loop5：偵測到的容量從 0 到 131072 F2FS-fs （loop5）：recover_inode：ino = 6，name = hln，內嵌 = 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：恢復） 錯誤 = 0 F2FS-fs （loop5）：recover_inode：ino = 6，名稱 = hln，內聯 = 1 F2FS-fs （loop5）：recover_data：ino = 6（i_size：恢復） 錯誤 = 0 F2FS-fs （loop5）：點陣圖設定錯誤，blk：5634 ------------[ cut here ]------------ 警告： CPU：3 PID：1013 at fs/f2fs/segment.c：2198 RIP：0010：update_sit_entry+0xa55/0x10b0 [f2fs] 呼叫追蹤： <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 如果我們啟用CONFIG_F2FS_CHECK_FS配置，它會觸發核心錯誤而不是警告。根本原因是：在模糊影像中，SIT 資料表與 inode 對應資料表不一致，導致在 SIT 資料表更新期間觸發此類警告。此修補程式引進了新的旗標DATA_GENERIC_ENHANCE_UPDATE，使用此旗標，資料區塊復原流程可以檢查 SIT 資料表中目的地 blkaddr 的驗證，並跳過 f2fs_replace_block（） 以避免狀態不一致。（CVE-2022-50273）

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

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

  - f2fs:復元中の宛先 blkaddr でのサニティチェックの実行を修正します。 Wenqing Liu 氏が bugzilla で報告しているように:
    https://bugzilla.kernel.org/show_bug.cgi?id=216456 loop5:0 から 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): ビットマップが誤って設定されました、blk:5634 ------------[ cut here ]------------ WARNING: CPU: 3 PID: 1013 at fs/f2fs/segment.c:2198 RIP: 0010:update_sit_entry+0xa55/0x10b0 [f2fs] 呼び出しトレース: <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 CONFIG_F2FS_を有効にする場合構成CHECK_FS、警告の代わりにカーネルパニックをトリガーします。根本的な原因は、ファジングされたイメージで、SIT テーブルが inode マッピングテーブルと一致しないため、SIT テーブルの更新中にこのような警告がトリガーされることです。このパッチは新しいフラグDATA_GENERIC_ENHANCE_UPDATE導入します。このフラグにより、データブロックリカバリフローは、SIT テーブルの宛先 blkaddr の検証をチェックし、一貫性のないステータスを回避するために f2fs_replace_block() をスキップできます。(CVE-2022-50273)

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 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 未修补的漏洞：CVE-2022-50273	Nessus	Misc.	9/17/2025	11/12/2026	medium
265170	Linux Distros 未修補弱點：CVE-2022-50273	Nessus	Misc.	9/17/2025	11/12/2026	medium
265170	Linux Distros のパッチ未適用の脆弱性: CVE-2022-50273	Nessus	Misc.	9/17/2025	11/12/2026	medium
265170	Linux Distros Unpatched Vulnerability : CVE-2022-50273	Nessus	Misc.	9/17/2025	11/12/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	11/2/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

medium

medium

medium

high

medium