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

  - f2fs修正以避免在 fsync_entry_slab 上發生多檔案系統執行個體爭用如 syzbot 報告在 f2fs 復原期間存在一個釋放後使用問題在 0xffff88823bc16040 寫入的釋放後使用 (在 kfence-#10中)
    kmem_cache_destroy+0x1f/0x120 mm/slab_common.c:486 f2fs_recover_fsync_data+0x75b0/0x8380 fs/f2fs/recovery.c:869 f2fs_fill_super+0x9393/0xa420 fs/f2fs/super.c:3945 mount_bdev+0x26c/0x3a0 fs/super。 :1367 legacy_get_tree+0xea/0x180 fs/fs_context.c:592 vfs_get_tree+0x86/0x270 fs/super.c:1497 do_new_mount fs/namespace.c:2905 [內嵌] path_mount+0x196f/0x2be0 fs/namespace.c:3235 do_mount fs/namespace.c:3248 [內嵌] __do_sys_mount fs/namespace.c:3456 [內嵌] __se_sys_mount+0x2f9/0x3b0 fs/namespace.c:3433 do_syscall_64+0x3f/0xb0 arch/x86/entry/common.c:47 entry_SYSCALL_64_after_hwframe +0x44/0xae 根本原因是多個 f2fs 檔案系統執行個體會在存取全域 fsync_entry_slab 指標時發生爭用導致 slab 快取發生釋放後使用問題修正在模組 init/destroy 程序期間僅初始化/破壞此 slab 快取一次以避免此問題。
    (CVE-2021-47335)

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

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

  - f2fs修复以避免 fsync_entry_slab 上由多个文件系统实例争用正如 syzbot 所报告f2fs 恢复期间存在释放后使用问题在 0xffff88823bc16040 处的释放后使用写入 kfence-#10中
    kmem_cache_destroy+0x1f/0x120 mm/slab_common.c:486 f2fs_recover_fsync_data+0x75b0/0x8380 fs/f2fs/recovery.c:869 f2fs_fill_super+0x9393/0xa420 fs/f2fs/super.c:3945 mount_bdev+0x26c/super.a0 fs3945 :1367 Legacy_get_tree+0xea/0x180 fs/fs_context.c:592 vfs_get_tree+0x86/0x270 fs/super.c:1497 do_new_mount fs/namespace.c:2905 [inline] path_mount+0x196f/0x2be0 fs/namespace.c:3235 do_mount fs/namespace.c:3248 [内联] __do_sys_mount fs/namespace.c:3456 [内联] __se_sys_mount+0x2f9/0x3b0 fs/namespace.c:3433 do_syscall_64+0x3f/0xb0 arch/x86/entry/common.c:47 entry_SYSCALL_64_after_hwframe +0x44/0xae根本原因是多个 f2fs 文件系统实例可能会在访问全局 fsync_entry_slab 指针时争用导致 slab 缓存释放后使用问题修复以在模块 init/destroy 过程期间仅初始化/破坏此 slab 缓存一次以避免此问题。
    (CVE-2021-47335)

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

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

  - f2fsマルチファイルシステムインスタンスによる fsync_entry_slab での競合を回避するために、修正します syzbot が報告したように、f2fs リカバリ中に use-after-free の問題が発生します 0xffff88823bc16040 での use-after-free 書き込み kfence-#10
    kmem_cache_destroy+0x1f/0x120 mm/slab_common.c:486 f2fs_recover_fsync_data+0x75b0/0x8380 fs/f2fs/recovery.c:869 f2fs_fill_super+0x9393/0xa420 fs/f2fs/super.c:3945 mount_bdev+0x9393/0xa420 fs/f2fs/super.c:3945 mount_bdev+0x3ac/0x3a4.0 :1367 legacy_get_tree+0xea/0x180 fs/fs_context.c:592 vfs_get_tree+0x86/0x270 fs/super.c:1497 do_new_mount fs/namespace.c:2905 [inline] path_mount+0x196f/0x2be0 fs/namespace.c:3235 do_mount fs/namespace.c:3248 [inline] __do_sys_mount fs/namespace.c:3456 [inline] __se_sys_mount+0x2f9/0x3b0 fs/namespace.c:3433 do_syscall_64+0x3f/0xb0 arch/x86/entry/common.c:47 entry_SYSCALL_64_after_hwframe +0x44/0xae root の原因は、複数の f2fs ファイルシステムインスタンスがグローバルな fsync_entry_slab ポインターへのアクセスで競合する可能性があるため、スラブキャッシュの use-after-free 問題が発生し、モジュール init/destroy 手順中にのみ、このスラブキャッシュを init/destroy に修正して を回避しますこの問題を発見しました。
    (CVE-2021-47335)

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 avoid racing on fsync_entry_slab by multi filesystem instances As syzbot reported, there is     an use-after-free issue during f2fs recovery: Use-after-free write at 0xffff88823bc16040 (in kfence-#10):
    kmem_cache_destroy+0x1f/0x120 mm/slab_common.c:486 f2fs_recover_fsync_data+0x75b0/0x8380     fs/f2fs/recovery.c:869 f2fs_fill_super+0x9393/0xa420 fs/f2fs/super.c:3945 mount_bdev+0x26c/0x3a0     fs/super.c:1367 legacy_get_tree+0xea/0x180 fs/fs_context.c:592 vfs_get_tree+0x86/0x270 fs/super.c:1497     do_new_mount fs/namespace.c:2905 [inline] path_mount+0x196f/0x2be0 fs/namespace.c:3235 do_mount     fs/namespace.c:3248 [inline] __do_sys_mount fs/namespace.c:3456 [inline] __se_sys_mount+0x2f9/0x3b0     fs/namespace.c:3433 do_syscall_64+0x3f/0xb0 arch/x86/entry/common.c:47     entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is multi f2fs filesystem instances can race on     accessing global fsync_entry_slab pointer, result in use-after-free issue of slab cache, fixes to     init/destroy this slab cache only once during module init/destroy procedure to avoid this issue.
    (CVE-2021-47335)

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-2026-005033 advisory.

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

    f2fs: fix to avoid racing on fsync_entry_slab by multi filesystem instances

    As syzbot reported, there is an use-after-free issue during f2fs recovery:

    Use-after-free write at 0xffff88823bc16040 (in kfence-#10):
     kmem_cache_destroy+0x1f/0x120 mm/slab_common.c:486      f2fs_recover_fsync_data+0x75b0/0x8380 fs/f2fs/recovery.c:869      f2fs_fill_super+0x9393/0xa420 fs/f2fs/super.c:3945      mount_bdev+0x26c/0x3a0 fs/super.c:1367      legacy_get_tree+0xea/0x180 fs/fs_context.c:592      vfs_get_tree+0x86/0x270 fs/super.c:1497      do_new_mount fs/namespace.c:2905 [inline]      path_mount+0x196f/0x2be0 fs/namespace.c:3235      do_mount fs/namespace.c:3248 [inline]
     __do_sys_mount fs/namespace.c:3456 [inline]
     __se_sys_mount+0x2f9/0x3b0 fs/namespace.c:3433      do_syscall_64+0x3f/0xb0 arch/x86/entry/common.c:47      entry_SYSCALL_64_after_hwframe+0x44/0xae

    The root cause is multi f2fs filesystem instances can race on accessing     global fsync_entry_slab pointer, result in use-after-free issue of slab     cache, fixes to init/destroy this slab cache only once during module     init/destroy procedure to avoid this issue.

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

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

    f2fs: fix to avoid racing on fsync_entry_slab by multi filesystem instances

    As syzbot reported, there is an use-after-free issue during f2fs recovery:

    Use-after-free write at 0xffff88823bc16040 (in kfence-#10):
     kmem_cache_destroy+0x1f/0x120 mm/slab_common.c:486      f2fs_recover_fsync_data+0x75b0/0x8380 fs/f2fs/recovery.c:869      f2fs_fill_super+0x9393/0xa420 fs/f2fs/super.c:3945      mount_bdev+0x26c/0x3a0 fs/super.c:1367      legacy_get_tree+0xea/0x180 fs/fs_context.c:592      vfs_get_tree+0x86/0x270 fs/super.c:1497      do_new_mount fs/namespace.c:2905 [inline]      path_mount+0x196f/0x2be0 fs/namespace.c:3235      do_mount fs/namespace.c:3248 [inline]
     __do_sys_mount fs/namespace.c:3456 [inline]
     __se_sys_mount+0x2f9/0x3b0 fs/namespace.c:3433      do_syscall_64+0x3f/0xb0 arch/x86/entry/common.c:47      entry_SYSCALL_64_after_hwframe+0x44/0xae

    The root cause is multi f2fs filesystem instances can race on accessing     global fsync_entry_slab pointer, result in use-after-free issue of slab     cache, fixes to init/destroy this slab cache only once during module     init/destroy procedure to avoid this issue.

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

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

    f2fs: fix to avoid racing on fsync_entry_slab by multi filesystem instances

    As syzbot reported, there is an use-after-free issue during f2fs recovery:

    Use-after-free write at 0xffff88823bc16040 (in kfence-#10):
     kmem_cache_destroy+0x1f/0x120 mm/slab_common.c:486      f2fs_recover_fsync_data+0x75b0/0x8380 fs/f2fs/recovery.c:869      f2fs_fill_super+0x9393/0xa420 fs/f2fs/super.c:3945      mount_bdev+0x26c/0x3a0 fs/super.c:1367      legacy_get_tree+0xea/0x180 fs/fs_context.c:592      vfs_get_tree+0x86/0x270 fs/super.c:1497      do_new_mount fs/namespace.c:2905 [inline]      path_mount+0x196f/0x2be0 fs/namespace.c:3235      do_mount fs/namespace.c:3248 [inline]
     __do_sys_mount fs/namespace.c:3456 [inline]
     __se_sys_mount+0x2f9/0x3b0 fs/namespace.c:3433      do_syscall_64+0x3f/0xb0 arch/x86/entry/common.c:47      entry_SYSCALL_64_after_hwframe+0x44/0xae

    The root cause is multi f2fs filesystem instances can race on accessing     global fsync_entry_slab pointer, result in use-after-free issue of slab     cache, fixes to init/destroy this slab cache only once during module     init/destroy procedure to avoid this issue.

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	名称	产品	系列	发布时间	最近更新时间	严重程度
224407	Linux Distros 未修補的弱點：CVE-2021-47335	Nessus	Misc.	2025/3/5	2025/10/28	medium
224407	Linux Distros 未修补的漏洞：CVE-2021-47335	Nessus	Misc.	2025/3/5	2025/10/28	medium
224407	Linux Distros のパッチ未適用の脆弱性: CVE-2021-47335	Nessus	Misc.	2025/3/5	2025/10/28	medium
238832	TencentOS Server 3: kernel (TSSA-2024:0719)	Nessus	Tencent Local Security Checks	2025/6/16	2025/11/20	high
224407	Linux Distros Unpatched Vulnerability : CVE-2021-47335	Nessus	Misc.	2025/3/5	2025/10/28	medium
239342	TencentOS Server 4: kernel (TSSA-2024:0981)	Nessus	Tencent Local Security Checks	2025/6/16	2025/12/4	high
296724	Unity Linux 20.1050e Security Update: kernel (UTSA-2026-005033)	Nessus	Unity Linux Local Security Checks	2026/1/27	2026/1/27	medium
268111	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986984)	Nessus	Unity Linux Local Security Checks	2025/10/7	2025/10/15	medium
273298	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988846)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	medium
238604	TencentOS Server 2: kernel (TSSA-2024:0720)	Nessus	Tencent Local Security Checks	2025/6/16	2025/11/20	high

检测

插件搜索

medium

medium

medium

high

medium

high

medium

medium

medium

high