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

  - f2fs修正以避免 dec_valid_node_count() 中出現 f2fs_bug_on()如 Yanming 在 bugzilla 中所報告
    https://bugzilla.kernel.org/show_bug.cgi?id=215897 我在核心 v5.17 的 F2FS 檔案系統中遇到錯誤。核心應啟用 CONFIG_KASAN=y 和 CONFIG_KASAN_INLINE=y。您可以執行下列命令來重現該錯誤： 核心訊息如下所示：fs/f2fs/f2fs.h:2511! 的核心錯誤Call Trace: f2fs_remove_inode_page+0x2a2/0x830 f2fs_evict_inode+0x9b7/0x1510 evict+0x282/0x4e0 do_unlinkat+0x33a/0x540 __x64_sys_unlinkat+0x8e/0xd0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is: .total_valid_block_count or .total_valid_node_count could fuzzed設為零則呼叫 dec_valid_node_count() 時即會造成 BUG_ON()此修補程式修正了列印警告資訊並將 SBI_NEED_FSCK 設為 CP 而非錯誤。
    (CVE-2022-49380)

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

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

  - f2fs修复以避免 dec_valid_node_count() 中的 f2fs_bug_on() 正如 Yanming 在 bugzilla 中报告的
    https://bugzilla.kernel.org/show_bug.cgi?id=215897 我在内核 v5.17 的 F2FS 文件系统中遇到一个缺陷。内核应启用 CONFIG_KASAN=y 和 CONFIG_KASAN_INLINE=y。您可以通过运行以下命令来重现该缺陷内核消息如下所示kernel BUG at fs/f2fs/f2fs.h:2511! Call Trace: f2fs_remove_inode_page+0x2a2/0x830 f2fs_evict_inode+0x9b7/0x1510 evict+0x282/0x4e0 do_unlinkat+0x33a/0x540 __x64_sys_unlinkat+0x8e/0xd0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is: .total_valid_block_count or .total_valid_node_count could fuzzed设为零那么在调用 dec_valid_node_count() 后将会导致 BUG_ON()此修补程序可修复此问题以打印警告信息并将 SBI_NEED_FSCK 设置为 CP 而不是错误。
    (CVE-2022-49380)

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

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

  - f2fsdec_valid_node_count() の f2fs_bug_on() を回避するための修正 Yanming が bugzilla で報告したように
    https://bugzilla.kernel.org/show_bug.cgi?id=215897 カーネル v5.17 の F2FS ファイルシステムでバグに遭遇しました。カーネルは CONFIG_KASAN=y および CONFIG_KASAN_INLINE=y を有効にする必要があります。次のコマンドを実行すると、このバグを複製できます。カーネルメッセージは以下に表示されます : fs/f2fs/f2fs.h:2511! でカーネルバグ。Call Trace: f2fs_remove_inode_page+0x2a2/0x830 f2fs_evict_inode+0x9b7/0x1510 evict+0x282/0x4e0 do_unlinkat+0x33a/0x540 __x64_sys_unlinkat+0x8e/0xd0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is: .total_valid_block_count or .total_valid_node_count could fuzzed dec_valid_node_count() が呼び出されると、BUG_ON() が引き起こされます。このパッチでは、警告情報が印刷され、SBI_NEED_FSCK がパニックの代わりに CP に設定されます。
    (CVE-2022-49380)

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-989484 advisory.

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

    f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()

    As Yanming reported in bugzilla:

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

    I have encountered a bug in F2FS file system in kernel v5.17.

    The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can     reproduce the bug by running the following commands:

    The kernel message is shown below:

    kernel BUG at fs/f2fs/f2fs.h:2511!     Call Trace:
     f2fs_remove_inode_page+0x2a2/0x830      f2fs_evict_inode+0x9b7/0x1510      evict+0x282/0x4e0      do_unlinkat+0x33a/0x540
     __x64_sys_unlinkat+0x8e/0xd0      do_syscall_64+0x3b/0x90      entry_SYSCALL_64_after_hwframe+0x44/0xae

    The root cause is: .total_valid_block_count or .total_valid_node_count     could fuzzed to zero, then once dec_valid_node_count() was called, it     will cause BUG_ON(), this patch fixes to print warning info and set     SBI_NEED_FSCK into CP instead of panic.

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

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

    f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()

    As Yanming reported in bugzilla:

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

    I have encountered a bug in F2FS file system in kernel v5.17.

    The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can     reproduce the bug by running the following commands:

    The kernel message is shown below:

    kernel BUG at fs/f2fs/f2fs.h:2511!     Call Trace:
     f2fs_remove_inode_page+0x2a2/0x830      f2fs_evict_inode+0x9b7/0x1510      evict+0x282/0x4e0      do_unlinkat+0x33a/0x540
     __x64_sys_unlinkat+0x8e/0xd0      do_syscall_64+0x3b/0x90      entry_SYSCALL_64_after_hwframe+0x44/0xae

    The root cause is: .total_valid_block_count or .total_valid_node_count     could fuzzed to zero, then once dec_valid_node_count() was called, it     will cause BUG_ON(), this patch fixes to print warning info and set     SBI_NEED_FSCK into CP instead of panic.

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count() As Yanming reported in bugzilla:
    https://bugzilla.kernel.org/show_bug.cgi?id=215897 I have encountered a bug in F2FS file system in kernel     v5.17. The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by     running the following commands: The kernel message is shown below: kernel BUG at fs/f2fs/f2fs.h:2511! Call     Trace: f2fs_remove_inode_page+0x2a2/0x830 f2fs_evict_inode+0x9b7/0x1510 evict+0x282/0x4e0     do_unlinkat+0x33a/0x540 __x64_sys_unlinkat+0x8e/0xd0 do_syscall_64+0x3b/0x90     entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is: .total_valid_block_count or     .total_valid_node_count could fuzzed to zero, then once dec_valid_node_count() was called, it will cause     BUG_ON(), this patch fixes to print warning info and set SBI_NEED_FSCK into CP instead of panic.
    (CVE-2022-49380)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Published	Updated	Severity
225282	Linux Distros 未修補的弱點：CVE-2022-49380	Nessus	Misc.	3/5/2025	7/17/2026	medium
225282	Linux Distros 未修补的漏洞：CVE-2022-49380	Nessus	Misc.	3/5/2025	7/17/2026	medium
225282	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49380	Nessus	Misc.	3/5/2025	7/17/2026	medium
273868	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989484)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	medium
273341	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989685)	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	10/9/2026	high
225282	Linux Distros Unpatched Vulnerability : CVE-2022-49380	Nessus	Misc.	3/5/2025	7/17/2026	medium

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

high

medium