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

  - net/handshake: hand off the pinned file reference to accept_doit handshake_req_next() removes the request     from the per-net pending list and drops hn_lock before handshake_nl_accept_doit() reads     req->hr_sk->sk_socket and dereferences sock->file (once in FD_PREPARE() and again in get_file()). In that     window a consumer running tls_handshake_cancel() followed by sockfd_put() (svc_sock_free) or __fput_sync()     (xs_reset_transport) releases sock->file. sock_release() then runs sock_orphan(), zeroing sk_socket, and     frees the struct socket. The accept-side code either reads NULL through sk_socket or chases freed memory.
    The submit-side sock_hold() does not prevent this. sk_refcnt protects struct sock, but struct socket and     sock->file are independently refcounted via the file descriptor the consumer owns. Pinning sk leaves sock     and sock->file unprotected. Retarget the accept-side dereferences at req->hr_file, which was pinned at     submit time, instead of req->hr_sk->sk_socket->file. Pinning on its own is not sufficient: a consumer that     cancels between handshake_req_next() returning and accept_doit reaching FD_PREPARE() takes the     !remove_pending() branch in handshake_req_cancel() and drops hr_file before the accept side takes its own     reference. Hand off an additional file reference inside handshake_req_next(), under hn_lock, so the accept     side operates on a reference that no concurrent handshake_req_cancel() can revoke. FD_PREPARE() consumes     that handed-off reference, either by transferring it to the new fd in fd_publish() or by dropping it in     the cleanup destructor on error; the explicit get_file() that previously balanced FD_PREPARE() is     therefore redundant and goes away. Update handshake_req_cancel_test2 and _test3 to simulate the     FD_PREPARE() consumption with an fput() so the kunit file-count assertions stay balanced. (CVE-2026-63979)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2026-63979

critical Nessus Plugin ID 327939

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.1

Version 1.5 Aug 6, 2026, 3:43 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") Detection (updated detection logic) Plugin metadata Plugin Feed: 202608061543
Version 1.4 Jul 29, 2026, 6:41 AM Detection (updated detection logic) Plugin Feed: 202607290641
Version 1.3 Jul 25, 2026, 1:06 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607251306
Version 1.2 Jul 21, 2026, 12:41 AM CVSS metrics ("CVSSv2 score" set to 4.9) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:N/I:N/A:C") CVSSv2 severity (based on CVE-2026-63979, severity decreased from "High" to "Medium") Detection (updated detection logic) Plugin metadata Plugin Feed: 202607210041
Version 1.1 Jul 20, 2026, 7:40 PM New Plugin Feed: 202607201940