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.

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.

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	Severity
273868	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989484)	Nessus	Unity Linux Local Security Checks	medium
273341	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989685)	Nessus	Unity Linux Local Security Checks	medium
225282	Linux Distros Unpatched Vulnerability : CVE-2022-49380	Nessus	Misc.	medium

Detections

Analytics

CVE-2022-49380

medium

Tenable Plugins

medium

medium

medium