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

  - btrfs: ensure no dirty metadata is written back for an fs with errors [BUG] During development of a minor     feature (make sure all btrfs_bio::end_io() is called in task context), I noticed a crash in generic/388,     where metadata writes triggered new works after btrfs_stop_all_workers(). It turns out that it can even     happen without any code modification, just using RAID5 for metadata and the same workload from generic/388     is going to trigger the use-after-free. [CAUSE] If btrfs hits an error, the fs is marked as error, no new     transaction is allowed thus metadata is in a frozen state. But there are some metadata modifications     before that error, and they are still in the btree inode page cache. Since there will be no real     transaction commit, all those dirty folios are just kept as is in the page cache, and they can not be     invalidated by invalidate_inode_pages2() call inside close_ctree(), because they are dirty. And finally     after btrfs_stop_all_workers(), we call iput() on btree inode, which triggers writeback of those dirty     metadata. And if the fs is using RAID56 metadata, this will trigger RMW and queue new works into     rmw_workers, which is already stopped, causing warning from queue_work() and use-after-free. [FIX] Add a     special handling for write_one_eb(), that if the fs is already in an error state, immediately mark the     bbio as failure, instead of really submitting them. Then during close_ctree(), iput() will just discard     all those dirty tree blocks without really writing them back, thus no more new jobs for already stopped-     and-freed workqueues. The extra discard in write_one_eb() also acts as an extra safenet. E.g. the     transaction abort is triggered by some extent/free space tree corruptions, and since extent/free space     tree is already corrupted some tree blocks may be allocated where they shouldn't be (overwriting existing     tree blocks). In that case writing them back will further corrupting the fs. (CVE-2025-40303)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2025-40303

medium Nessus Plugin ID 277660

Version 1.7

Version 1.6

Version 1.4

Version 1.3

Version 1.2

Version 1.1

Version 1.7 Jan 21, 2026, 10:50 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601211050
Version 1.6 Jan 13, 2026, 2:35 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601130235
Version 1.4 Dec 15, 2025, 9:39 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202512152139
Version 1.3 Dec 10, 2025, 9:29 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202512100929
Version 1.2 Dec 9, 2025, 2:31 AM CVSS metrics ("CVSSv2 score" set to 7.8) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:N/AC:M/Au:N/C:N/I:P/A:C") CVSSv2 severity (based on CVE-2025-40303, severity increased from "Medium" to "High") Detection (updated detection logic) Plugin metadata Plugin Feed: 202512090231
Version 1.1 Dec 8, 2025, 6:20 PM New Plugin Feed: 202512081820