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 node footer for non inode dnode As syzbot reported below: ------------[     cut here ]------------ kernel BUG at fs/f2fs/file.c:1243! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI     CPU: 0 UID: 0 PID: 5354 Comm: syz.0.0 Not tainted 6.17.0-rc1-syzkaller-00211-g90d970cade8e #0     PREEMPT(full) RIP: 0010:f2fs_truncate_hole+0x69e/0x6c0 fs/f2fs/file.c:1243 Call Trace: <TASK>     f2fs_punch_hole+0x2db/0x330 fs/f2fs/file.c:1306 f2fs_fallocate+0x546/0x990 fs/f2fs/file.c:2018     vfs_fallocate+0x666/0x7e0 fs/open.c:342 ksys_fallocate fs/open.c:366 [inline] __do_sys_fallocate     fs/open.c:371 [inline] __se_sys_fallocate fs/open.c:369 [inline] __x64_sys_fallocate+0xc0/0x110     fs/open.c:369 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0     arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f1e65f8ebe9 w/ a     fuzzed image, f2fs may encounter panic due to it detects inconsistent truncation range in direct node in     f2fs_truncate_hole(). The root cause is: a non-inode dnode may has the same footer.ino and footer.nid, so     the dnode will be parsed as an inode, then ADDRS_PER_PAGE() may return wrong blkaddr count which may be     923 typically, by chance, dn.ofs_in_node is equal to 923, then count can be calculated to 0 in below     statement, later it will trigger panic w/ f2fs_bug_on(, count == 0 || ...). count = min(end_offset -     dn.ofs_in_node, pg_end - pg_start); This patch introduces a new node_type NODE_TYPE_NON_INODE, then     allowing passing the new_type to sanity_check_node_footer in f2fs_get_node_folio() to detect corruption     that a non-inode dnode has the same footer.ino and footer.nid. Scripts to reproduce: mkfs.f2fs -f /dev/vdb     mount /dev/vdb /mnt/f2fs touch /mnt/f2fs/foo touch /mnt/f2fs/bar dd if=/dev/zero of=/mnt/f2fs/foo bs=1M     count=8 umount /mnt/f2fs inject.f2fs --node --mb i_nid --nid 4 --idx 0 --val 5 /dev/vdb mount /dev/vdb     /mnt/f2fs xfs_io /mnt/f2fs/foo -c fpunch 6984k 4k (CVE-2025-40025)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2025-40025

medium Nessus Plugin ID 271879

Version 1.10

Version 1.9

Version 1.8

Version 1.7

Version 1.6

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.1

Version 1.10 Jan 21, 2026, 5:00 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601211700
Version 1.9 Jan 15, 2026, 2:04 PM Detection (updated detection logic) Plugin Feed: 202601151404
Version 1.8 Jan 13, 2026, 2:35 AM Detection (updated detection logic) Plugin Feed: 202601130235
Version 1.7 Dec 15, 2025, 9:39 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202512152139
Version 1.6 Dec 12, 2025, 5:16 PM Detection (updated detection logic) Plugin Feed: 202512121716
Version 1.5 Dec 8, 2025, 6:20 PM Detection (updated detection logic) Plugin Feed: 202512081820
Version 1.4 Dec 4, 2025, 7:43 PM Detection (updated detection logic) Plugin Feed: 202512041943
Version 1.3 Nov 23, 2025, 4:41 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202511230441
Version 1.2 Oct 29, 2025, 12:22 PM CVSS metrics ("CVSSv2 score" set to 4.7) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:M/Au:N/C:N/I:N/A:C") CVSS metrics ("CVSSv3 score" set to 6.6) CVSS metrics ("CVSSv3 vector" set to "CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H") CVSSv2 severity (based on CVE-2025-40025, severity decreased from "High" to "Medium") CVSSv3 severity (based on None, severity decreased from "High" to "Medium") Detection (updated detection logic) Plugin metadata Plugin Feed: 202510291222
Version 1.1 Oct 29, 2025, 3:03 AM New Plugin Feed: 202510290303