The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - nilfs2: do not force clear folio if buffer is referenced Patch series nilfs2: protect busy buffer heads     from being force-cleared. This series fixes the buffer head state inconsistency issues reported by syzbot     that occurs when the filesystem is corrupted and falls back to read-only, and the associated buffer head     use-after-free issue. This patch (of 2): Syzbot has reported that after nilfs2 detects filesystem     corruption and falls back to read-only, inconsistencies in the buffer state may occur. One of the     inconsistencies is that when nilfs2 calls mark_buffer_dirty() to set a data or metadata buffer as dirty,     but it detects that the buffer is not in the uptodate state: WARNING: CPU: 0 PID: 6049 at fs/buffer.c:1177     mark_buffer_dirty+0x2e5/0x520 fs/buffer.c:1177 ... Call Trace: <TASK>     nilfs_palloc_commit_alloc_entry+0x4b/0x160 fs/nilfs2/alloc.c:598 nilfs_ifile_create_inode+0x1dd/0x3a0     fs/nilfs2/ifile.c:73 nilfs_new_inode+0x254/0x830 fs/nilfs2/inode.c:344 nilfs_mkdir+0x10d/0x340     fs/nilfs2/namei.c:218 vfs_mkdir+0x2f9/0x4f0 fs/namei.c:4257 do_mkdirat+0x264/0x3a0 fs/namei.c:4280
    __do_sys_mkdirat fs/namei.c:4295 [inline] __se_sys_mkdirat fs/namei.c:4293 [inline]
    __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4293 do_syscall_x64 arch/x86/entry/common.c:52 [inline]     do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The other is     when nilfs_btree_propagate(), which propagates the dirty state to the ancestor nodes of a b-tree that     point to a dirty buffer, detects that the origin buffer is not dirty, even though it should be: WARNING:
    CPU: 0 PID: 5245 at fs/nilfs2/btree.c:2089 nilfs_btree_propagate+0xc79/0xdf0 fs/nilfs2/btree.c:2089 ...
    Call Trace: <TASK> nilfs_bmap_propagate+0x75/0x120 fs/nilfs2/bmap.c:345 nilfs_collect_file_data+0x4d/0xd0     fs/nilfs2/segment.c:587 nilfs_segctor_apply_buffers+0x184/0x340 fs/nilfs2/segment.c:1006     nilfs_segctor_scan_file+0x28c/0xa50 fs/nilfs2/segment.c:1045 nilfs_segctor_collect_blocks     fs/nilfs2/segment.c:1216 [inline] nilfs_segctor_collect fs/nilfs2/segment.c:1540 [inline]     nilfs_segctor_do_construct+0x1c28/0x6b90 fs/nilfs2/segment.c:2115 nilfs_segctor_construct+0x181/0x6b0     fs/nilfs2/segment.c:2479 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2587 [inline]     nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2701 kthread+0x2f0/0x390 kernel/kthread.c:389     ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30     arch/x86/entry/entry_64.S:244 </TASK> Both of these issues are caused by the callbacks that handle the     page/folio write requests, forcibly clear various states, including the working state of the buffers they     hold, at unexpected times when they detect read-only fallback. Fix these issues by checking if the buffer     is referenced before clearing the page/folio state, and skipping the clear if it is. (CVE-2025-21722)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2025-21722

high Nessus Plugin ID 231046

Version 1.16

Version 1.15

Version 1.14

Version 1.13

Version 1.12

Version 1.11

Version 1.10

Version 1.9

Version 1.8

Version 1.7

Version 1.5

Version 1.4

Version 1.3

Version 1.1

Version 1.16 Jan 21, 2026, 10:50 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601211050
Version 1.15 Jan 16, 2026, 10:12 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601162212
Version 1.14 Jan 10, 2026, 7:58 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601101958
Version 1.13 Dec 17, 2025, 4:56 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202512171656
Version 1.12 Dec 15, 2025, 9:39 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202512152139
Version 1.11 Dec 5, 2025, 1:34 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202512051334
Version 1.10 Dec 4, 2025, 7:43 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202512041943
Version 1.9 Dec 3, 2025, 8:52 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202512032052
Version 1.8 Oct 29, 2025, 3:03 AM Detection (updated detection logic) Plugin Feed: 202510290303
Version 1.7 Oct 27, 2025, 11:56 PM CVSS temporal metrics ("CVSSv2 temporal vector" set to "CVSS2#E:U/RL:U/RC:C") CVSS temporal metrics ("CVSSv3 temporal vector" set to "CVSS:3.0/E:U/RL:U/RC:C") Detection (updated detection logic) Plugin Feed: 202510272356
Version 1.5 Sep 6, 2025, 7:55 PM CVSS metrics ("Cvssv4 score" set to 0.0) CVSSv2 severity (based on None, severity decreased from "High" to "Low") Detection (updated detection logic) Plugin metadata Plugin Feed: 202509061955
Version 1.4 Sep 2, 2025, 6:30 AM CVSS metrics ("Cvssv4 score" set to 0.0) CVSSv2 severity (based on None, severity decreased from "High" to "Low") Detection (updated detection logic) Plugin metadata Plugin Feed: 202509020630
Version 1.3 Aug 23, 2025, 2:29 AM CVSS metrics ("Cvssv4 score" set to 0.0) CVSSv2 severity (based on None, severity decreased from "High" to "Low") Detection (updated detection logic) Plugin metadata Plugin Feed: 202508230229
Version 1.1 Mar 6, 2025, 5:02 PM New Plugin Feed: 202503061702