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

  - vfs: fix race between evice_inodes() and find_inode()&iput() Hi, all Recently I noticed a bug[1] in btrfs,     after digged it into and I believe it'a race in vfs. Let's assume there's a inode (ie ino 261) with     i_count 1 is called by iput(), and there's a concurrent thread calling generic_shutdown_super(). cpu0:
    cpu1: iput() // i_count is 1 ->spin_lock(inode) ->dec i_count to 0 ->iput_final() generic_shutdown_super()
    ->__inode_add_lru() ->evict_inodes() // cause some reason[2] ->if (atomic_read(inode->i_count)) continue;
    // return before // inode 261 passed the above check // list_lru_add_obj() // and then schedule out
    ->spin_unlock() // note here: the inode 261 // was still at sb list and hash list, // and     I_FREEING|I_WILL_FREE was not been set btrfs_iget() // after some function calls ->find_inode() // found     the above inode 261 ->spin_lock(inode) // check I_FREEING|I_WILL_FREE // and passed ->__iget()
    ->spin_unlock(inode) // schedule back ->spin_lock(inode) // check (I_NEW|I_FREEING|I_WILL_FREE) flags, //     passed and set I_FREEING iput() ->spin_unlock(inode) ->spin_lock(inode) ->evict() // dec i_count to 0
    ->iput_final() ->spin_unlock() ->evict() Now, we have two threads simultaneously evicting the same inode,     which may trigger the BUG(inode->i_state & I_CLEAR) statement both within clear_inode() and iput(). To fix     the bug, recheck the inode->i_count after holding i_lock. Because in the most scenarios, the first check     is valid, and the overhead of spin_lock() can be reduced. If there is any misunderstanding, please let me     know, thanks. [1]: https://lore.kernel.org/linux-btrfs/000000000000eabe1d0619c48986@google.com/ [2]: The     reason might be 1. SB_ACTIVE was removed or 2. mapping_shrinkable() return false when I reproduced the     bug. (CVE-2024-47679)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2024-47679

medium Nessus Plugin ID 228532

Version 1.14

Version 1.12

Version 1.11

Version 1.10

Version 1.9

Version 1.8

Version 1.5

Version 1.4

Version 1.1

Version 1.14 Feb 4, 2026, 8:43 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202602042043
Version 1.12 Jan 16, 2026, 10:12 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601162212
Version 1.11 Jan 10, 2026, 7:58 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601101958
Version 1.10 Nov 12, 2025, 12:37 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202511120037
Version 1.9 Oct 29, 2025, 3:03 AM Detection (updated detection logic) Plugin Feed: 202510290303
Version 1.8 Oct 28, 2025, 5: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: 202510281756
Version 1.5 Sep 4, 2025, 5:30 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: 202509041730
Version 1.4 Aug 31, 2025, 7:32 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: 202508311932
Version 1.1 Mar 6, 2025, 7:23 AM New Plugin Feed: 202503060723