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

  - In the Linux kernel, the following vulnerability has been resolved: futex: Fix race in     futex_pivot_pending() during private hash resize A task performing a custom private hash resize can remain     blocked in uninterruptible sleep indefinitely. The hung-task detector reports: INFO: task futex-     resizer:314 blocked for more than 10 seconds. task:futex-resizer state:D stack:14824 pid:314 tgid:312     ppid:311 Call Trace: __schedule+0x521/0xf30 schedule+0x22/0xa0 futex_hash_allocate+0x3db/0x490
    __do_sys_prctl+0x6f5/0xbd0 do_syscall_64+0xf9/0x530 entry_SYSCALL_64_after_hwframe+0x77/0x7f Kernel panic
    - not syncing: hung_task: blocked tasks futex_pivot_pending() allows the resize request to continue when     either no replacement hash is pending (hash_new == NULL) or the current hash reference count has reached     zero. After the final-reference wake, another futex task can complete the pivot between the two     observations: T1 T2 futex_hash_allocate() wait_var_event(mm, ...) futex_pivot_pending(mm) hash_new != NULL     futex_hash() futex_ref_get(old) -> false futex_pivot_hash(mm) hash_new = NULL __futex_pivot_hash(mm, new)     rcu_assign_pointer(hash, new) fph = rcu_dereference(hash) /* new */ futex_ref_is_dead(fph) -> false     schedule() The pivot changes the state from hash_new != NULL with a dead current hash to hash_new == NULL     with a live current hash. Because futex_pivot_pending() reads hash_new and hash without serialization, the     resize task can observe hash_new in the pre-pivot state and hash in the post-pivot state, causing     futex_pivot_pending() to return false even though the pivot has completed. The task then goes to sleep     after the wakeup has already been consumed. Serialize state reads in futex_pivot_pending() using     futex_mm_phash::lock. This guarantees that futex_pivot_pending() observes hash_new and hash atomically,     eliminating the race condition. (CVE-2026-80776)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2026-80776

medium Nessus Plugin ID 343475

Version 1.6

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.1

Version 1.6 Nov 6, 2026, 7:31 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202611060731
Version 1.5 Nov 4, 2026, 12:13 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202611041213
Version 1.4 Nov 1, 2026, 6:47 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 4.7) CVSS metrics ("CVSSv3 vector" set to "CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H") CVSSv2 severity (based on CVE-2026-80776, severity increased from "Low" to "Medium") Detection (updated detection logic) Plugin metadata Plugin Feed: 202611011847
Version 1.3 Sep 10, 2026, 1:56 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202609100156
Version 1.2 Sep 8, 2026, 12:57 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202609080057
Version 1.1 Sep 7, 2026, 2:57 PM New Plugin Feed: 202609071457