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

  - writeback: don't block sync for filesystems with no data integrity guarantees Add a SB_I_NO_DATA_INTEGRITY     superblock flag for filesystems that cannot guarantee data persistence on sync (eg fuse). For superblocks     with this flag set, sync kicks off writeback of dirty inodes but does not wait for the flusher threads to     complete the writeback. This replaces the per-inode AS_NO_DATA_INTEGRITY mapping flag added in commit     f9a49aa302a0 (fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes()). The flag belongs at     the superblock level because data integrity is a filesystem-wide property, not a per-inode one. Having     this flag at the superblock level also allows us to skip having to iterate every dirty inode in     wait_sb_inodes() only to skip each inode individually. Prior to this commit, mappings with no data     integrity guarantees skipped waiting on writeback completion but still waited on the flusher threads to     finish initiating the writeback. Waiting on the flusher threads is unnecessary. This commit kicks off     writeback but does not wait on the flusher threads. This change properly addresses a recent report [1] for     a suspend-to-RAM hang seen on fuse-overlayfs that was caused by waiting on the flusher threads to finish:
    Workqueue: pm_fs_sync pm_fs_sync_work_fn Call Trace: <TASK> __schedule+0x457/0x1720 schedule+0x27/0xd0     wb_wait_for_completion+0x97/0xe0 sync_inodes_sb+0xf8/0x2e0 __iterate_supers+0xdc/0x160 ksys_sync+0x43/0xb0     pm_fs_sync_work_fn+0x17/0xa0 process_one_work+0x193/0x350 worker_thread+0x1a1/0x310 kthread+0xfc/0x240     ret_from_fork+0x243/0x280 ret_from_fork_asm+0x1a/0x30 </TASK> On fuse this is problematic because there     are paths that may cause the flusher thread to block (eg if systemd freezes the user session cgroups     first, which freezes the fuse daemon, before invoking the kernel suspend. The kernel suspend triggers
    ->write_node() which on fuse issues a synchronous setattr request, which cannot be processed since the     daemon is frozen. Or if the daemon is buggy and cannot properly complete writeback, initiating writeback     on a dirty folio already under writeback leads to writeback_get_folio() -> folio_prepare_writeback() ->     unconditional wait on writeback to finish, which will cause a hang). This commit restores fuse to its     prior behavior before tmp folios were removed, where sync was essentially a no-op. [1]     https://lore.kernel.org/linux-fsdevel/CAJnrk1a-     asuvfrbKXbEwwDSctvemF+6zfhdnuzO65Pt8HsFSRw@mail.gmail.com/T/#m632c4648e9cafc4239299887109ebd880ac6c5c1     (CVE-2026-31465)

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

ID	Name	Product	Family	Published	Updated	Severity
316948	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1746)	Nessus	Amazon Linux Local Security Checks	5/27/2026	7/16/2026	high
310605	Linux Distros Unpatched Vulnerability : CVE-2026-31465	Nessus	Misc.	4/28/2026	7/31/2026	medium

Detections

Analytics

Plugins Search

high

medium