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 total_data_blocks As Yanming reported in bugzilla:
    https://bugzilla.kernel.org/show_bug.cgi?id=215916 The kernel message is shown below: kernel BUG at     fs/f2fs/segment.c:2560! Call Trace: allocate_segment_by_default+0x228/0x440     f2fs_allocate_data_block+0x13d1/0x31f0 do_write_page+0x18d/0x710 f2fs_outplace_write_data+0x151/0x250     f2fs_do_write_data_page+0xef9/0x1980 move_data_page+0x6af/0xbc0 do_garbage_collect+0x312f/0x46f0     f2fs_gc+0x6b0/0x3bc0 f2fs_balance_fs+0x921/0x2260 f2fs_write_single_data_page+0x16be/0x2370     f2fs_write_cache_pages+0x428/0xd00 f2fs_write_data_pages+0x96e/0xd50 do_writepages+0x168/0x550
    __writeback_single_inode+0x9f/0x870 writeback_sb_inodes+0x47d/0xb20 __writeback_inodes_wb+0xb2/0x200     wb_writeback+0x4bd/0x660 wb_workfn+0x5f3/0xab0 process_one_work+0x79f/0x13e0 worker_thread+0x89/0xf60     kthread+0x26a/0x300 ret_from_fork+0x22/0x30 RIP: 0010:new_curseg+0xe8d/0x15f0 The root cause is:
    ckpt.valid_block_count is inconsistent with SIT table, stat info indicates filesystem has free blocks, but     SIT table indicates filesystem has no free segment. So that during garbage colloection, it triggers panic     when LFS allocator fails to find free segment. This patch tries to fix this issue by checking consistency     in between ckpt.valid_block_count and block accounted from SIT. (CVE-2022-49360)

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

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

    f2fs: fix to do sanity check on total_data_blocks

    As Yanming reported in bugzilla:

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

    The kernel message is shown below:

    kernel BUG at fs/f2fs/segment.c:2560!     Call Trace:
     allocate_segment_by_default+0x228/0x440      f2fs_allocate_data_block+0x13d1/0x31f0      do_write_page+0x18d/0x710      f2fs_outplace_write_data+0x151/0x250      f2fs_do_write_data_page+0xef9/0x1980      move_data_page+0x6af/0xbc0      do_garbage_collect+0x312f/0x46f0      f2fs_gc+0x6b0/0x3bc0      f2fs_balance_fs+0x921/0x2260      f2fs_write_single_data_page+0x16be/0x2370      f2fs_write_cache_pages+0x428/0xd00      f2fs_write_data_pages+0x96e/0xd50      do_writepages+0x168/0x550
     __writeback_single_inode+0x9f/0x870      writeback_sb_inodes+0x47d/0xb20
     __writeback_inodes_wb+0xb2/0x200      wb_writeback+0x4bd/0x660      wb_workfn+0x5f3/0xab0      process_one_work+0x79f/0x13e0      worker_thread+0x89/0xf60      kthread+0x26a/0x300      ret_from_fork+0x22/0x30     RIP: 0010:new_curseg+0xe8d/0x15f0

    The root cause is: ckpt.valid_block_count is inconsistent with SIT table,     stat info indicates filesystem has free blocks, but SIT table indicates     filesystem has no free segment.

    So that during garbage colloection, it triggers panic when LFS allocator     fails to find free segment.

    This patch tries to fix this issue by checking consistency in between     ckpt.valid_block_count and block accounted from SIT.

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

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

    f2fs: fix to do sanity check on total_data_blocks

    As Yanming reported in bugzilla:

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

    The kernel message is shown below:

    kernel BUG at fs/f2fs/segment.c:2560!     Call Trace:
     allocate_segment_by_default+0x228/0x440      f2fs_allocate_data_block+0x13d1/0x31f0      do_write_page+0x18d/0x710      f2fs_outplace_write_data+0x151/0x250      f2fs_do_write_data_page+0xef9/0x1980      move_data_page+0x6af/0xbc0      do_garbage_collect+0x312f/0x46f0      f2fs_gc+0x6b0/0x3bc0      f2fs_balance_fs+0x921/0x2260      f2fs_write_single_data_page+0x16be/0x2370      f2fs_write_cache_pages+0x428/0xd00      f2fs_write_data_pages+0x96e/0xd50      do_writepages+0x168/0x550
     __writeback_single_inode+0x9f/0x870      writeback_sb_inodes+0x47d/0xb20
     __writeback_inodes_wb+0xb2/0x200      wb_writeback+0x4bd/0x660      wb_workfn+0x5f3/0xab0      process_one_work+0x79f/0x13e0      worker_thread+0x89/0xf60      kthread+0x26a/0x300      ret_from_fork+0x22/0x30     RIP: 0010:new_curseg+0xe8d/0x15f0

    The root cause is: ckpt.valid_block_count is inconsistent with SIT table,     stat info indicates filesystem has free blocks, but SIT table indicates     filesystem has no free segment.

    So that during garbage colloection, it triggers panic when LFS allocator     fails to find free segment.

    This patch tries to fix this issue by checking consistency in between     ckpt.valid_block_count and block accounted from SIT.

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.

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

  - f2fs修复以对 total_data_blocks 进行健全性检查正如 Yanming 在 bugzilla 中报告的
    https://bugzilla.kernel.org/show_bug.cgi?id=215916 内核消息如下所示: kernel BUG at fs/f2fs/segment.c:2560! Call Trace: allocate_segment_by_default+0x228/0x440 f2fs_allocate_data_block+0x13d1/0x31f0 do_write_page+0x18d/0x710 f2fs_outplace_write_data+0x151/0x250 f2fs_do_write_data_page+0xef9/0x1980 move_data_page+0x6af/0xbc0 do_garbage_collect+0x312f/0x46f0 f2fs_gc+0x6b0/0x3bc0 f2fs_balance_fs+0x921/0x2260 f2fs_write_single_data_page+ 0x16be/0x2370 f2fs_write_cache_pages+0x428/0xd00 f2fs_write_data_pages+0x96e/0xd50 do_writepages+0x168/0x550
    __writeback_single_inode+0x9f/0x870 writeback_sb_inodes+0x47d/0xb20 __writeback_inodes_wb+0xb2/0x200 wb_writeback+0x4bd/0x660 wb_workfn+0x5f3/0xab0 process_one_work+0x79f/0x13e0 worker_thread+0x89/0xf60 kthread+0x26a/0x300 ret_from_fork+0x22/0x30 RIP: 0010:new_curseg +0xe8d/0x15f0 根本原因为
    ckpt.valid_block_count 与 SIT 表不一致stat 信息表示文件系统有空闲区块但 SIT 表表示文件系统没有空闲段。因此在垃圾回收期间LFS 分配器找不到可用段时会触发错误。此修补程序尝试通过检查 ckpt.valid_block_count 和从 SIT 解释的区块之间的一致性来修复此问题。 (CVE-2022-49360)

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

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

  - f2fstotal_data_blocks でサニティーチェックを行うように修正します As Yanming が bugzilla で報告しました
    https://bugzilla.kernel.org/show_bug.cgi?id=215916 カーネルメッセージは以下のとおりです。fs/f2fs/segment.c:2560! でカーネルのバグ。Call Trace: allocate_segment_by_default+0x228/0x440 f2fs_allocate_data_block+0x13d1/0x31f0 do_write_page+0x18d/0x710 f2fs_outplace_write_data+0x151/0x250 f2fs_do_write_data_page+0xef9/0x1980 move_data_page+0x6af/0xbc0 do_garbage_collect+0x312f/0x46f0 f2fs_gc+0x6b0/0x3bc0 f2fs_balance_fs+0x921/0x2260 f2fs_write_single_data_page+ 0x16be/0x2370 f2fs_write_cache_pages+0x428/0xd00 f2fs_write_data_pages+0x96e/0xd50 do_writepages+0x168/0x550
    __writeback_single_inode+0x9f/0x870 writeback_sb_inodes+0x47d/0xb20 __writeback_inodes_wb+0xb2/0x200 wb_writeback+0x4bd/0x660 wb_workfn+0x5f3/0xab0 process_one_work+0x79f/0x13e0 worker_thread+0x89/0xf60 kthread+0x26a/0x300 ret_from_fork+0x22/0x30 RIP: 0010:new_curseg +0xe8d/0x15f0 根本原因は次のとおりです。
    ckpt.valid_block_count は SIT テーブルと一致しません。stat info はファイルシステムに解放済みブロックがあることを示していますが、SIT テーブルはファイルシステムに解放済みセグメントがないことを示しています。そのため、ガベージコレクト中に、LFS アロケーターが空きセグメントを見つけられなかった場合にパニックが発生します。このパッチは、ckpt.valid_block_count と SIT からのブロックアカウントの間の一貫性をチェックすることで、この問題の修正を試みます。CVE-2022-49360

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

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

  - f2fs修正以對 total_data_blocks 執行功能健全檢查如 Yanming 在 bugzilla 中所報告
    https://bugzilla.kernel.org/show_bug.cgi?id=215916 核心訊息如下所示fs/f2fs/segment.c:2560! 的核心錯誤Call Trace: allocate_segment_by_default+0x228/0x440 f2fs_allocate_data_block+0x13d1/0x31f0 do_write_page+0x18d/0x710 f2fs_outplace_write_data+0x151/0x250 f2fs_do_write_data_page+0xef9/0x1980 move_data_page+0x6af/0xbc0 do_garbage_collect+0x312f/0x46f0 f2fs_gc+0x6b0/0x3bc0 f2fs_balance_fs+0x921/0x2260 f2fs_write_single_data_page+ 0x16be/0x2370 f2fs_write_cache_pages+0x428/0xd00 f2fs_write_data_pages+0x96e/0xd50 do_writepages+0x168/0x550
    __writeback_single_inode+0x9f/0x870 writeback_sb_inodes+0x47d/0xb20 __writeback_inodes_wb+0xb2/0x200 wb_writeback+0x4bd/0x660 wb_workfn+0x5f3/0xab0 process_one_work+0x79f/0x13e0 worker_thread+0x89/0xf60 kthread+0x26a/0x300 ret_from_fork+0x22/0x30 RIP: 0010:new_curseg +0xe8d/0x15f0 根本原因是
    ckpt.valid_block_count 與 SIT 表格不一致統計資訊表示檔案系統有可用區塊但 SIT 表格表示檔案系統沒有可用區段。因此在記憶體集合期間LFS 配置器無法找到可用區段時會觸發不穩定。此修補程式會檢查 SIT 的 ckpt.valid_block_count 和 block accounting 之間的一致性以嘗試修正此問題。 (CVE-2022-49360)

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

ID	名前	製品	ファミリー	公開日	更新日	深刻度
225208	Linux Distros Unpatched Vulnerability : CVE-2022-49360	Nessus	Misc.	2025/3/5	2025/10/28	medium
273363	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989647)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	medium
273989	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989219)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	medium
225208	Linux Distros 未修补的漏洞：CVE-2022-49360	Nessus	Misc.	2025/3/5	2025/10/28	medium
225208	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49360	Nessus	Misc.	2025/3/5	2025/10/28	medium
225208	Linux Distros 未修補的弱點：CVE-2022-49360	Nessus	Misc.	2025/3/5	2025/10/28	medium

検出

プラグインの検索

medium

medium

medium

medium

medium

medium