There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In the Linux kernel, the following vulnerability has been resolved: xfrm: clear mode callbacks after
    failed mode setup xfrm_state_gc_task can run long after a failed IPTFS state setup. In the reproduced
    case, __xfrm_init_state() cached x->mode_cbs, IPTFS setup returned -ENOMEM before publishing mode_data,
    and the temporary module reference from xfrm_get_mode_cbs() was dropped immediately. The dead state then
    kept x->mode_cbs until deferred GC ran after xfrm_iptfs had been unloaded. Clear x->mode_cbs when mode
    init or clone fails before publishing mode_data. Those states never installed mode-specific state or the
    long-term IPTFS module pin, so deferred GC has nothing mode-specific to destroy and must not retain a
    callback table pointer past the temporary lookup reference. The buggy scenario involves two paths, with
    each column showing the order within that path: failed setup path: 1. cache x->mode_cbs 2. mode setup
    fails before mode_data 3. drop the temporary module ref 4. dead state keeps x->mode_cbs cached GC/unload
    path: 1. xfrm_state_put() queues GC work 2. xfrm_iptfs unloads later 3. xfrm_state_gc_task runs 4. GC
    dereferences stale x->mode_cbs This also covers the failed clone path where clone_state() returns before
    publishing mode_data. Validation reproduced this kernel report: Kernel panic - not syncing: Fatal
    exception CONFIG_FAULT_INJECTION_STACKTRACE_FILTER=y failslab_stacktrace_filter matched xfrm_iptfs frames
    ack_error=-12 FAULT_INJECTION: forcing a failure BUG: unable to handle page fault Workqueue: events
    xfrm_state_gc_task RIP: xfrm_state_gc_task+0x142/0x650 Modules linked in: esp4_offload xfrm_user [last
    unloaded: xfrm_iptfs] Kernel panic - not syncing: Fatal exception (CVE-2026-68415)

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: xfrm: clear mode callbacks after     failed mode setup xfrm_state_gc_task can run long after a failed IPTFS state setup. In the reproduced     case, __xfrm_init_state() cached x->mode_cbs, IPTFS setup returned -ENOMEM before publishing mode_data,     and the temporary module reference from xfrm_get_mode_cbs() was dropped immediately. The dead state then     kept x->mode_cbs until deferred GC ran after xfrm_iptfs had been unloaded. Clear x->mode_cbs when mode     init or clone fails before publishing mode_data. Those states never installed mode-specific state or the     long-term IPTFS module pin, so deferred GC has nothing mode-specific to destroy and must not retain a     callback table pointer past the temporary lookup reference. The buggy scenario involves two paths, with     each column showing the order within that path: failed setup path: 1. cache x->mode_cbs 2. mode setup     fails before mode_data 3. drop the temporary module ref 4. dead state keeps x->mode_cbs cached GC/unload     path: 1. xfrm_state_put() queues GC work 2. xfrm_iptfs unloads later 3. xfrm_state_gc_task runs 4. GC     dereferences stale x->mode_cbs This also covers the failed clone path where clone_state() returns before     publishing mode_data. Validation reproduced this kernel report: Kernel panic - not syncing: Fatal     exception CONFIG_FAULT_INJECTION_STACKTRACE_FILTER=y failslab_stacktrace_filter matched xfrm_iptfs frames     ack_error=-12 FAULT_INJECTION: forcing a failure BUG: unable to handle page fault Workqueue: events     xfrm_state_gc_task RIP: xfrm_state_gc_task+0x142/0x650 Modules linked in: esp4_offload xfrm_user [last     unloaded: xfrm_iptfs] Kernel panic - not syncing: Fatal exception (CVE-2026-68415)

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

ID	Name	Product	Family	Published	Updated	Severity
470557	Google: sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_18: security update to 19999.44.21	Tenable Self-Hosted Container Security	Google COS Security Checks	10/3/2026	10/6/2026	high
471446	Google: sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_18: security update to 20085.0.0	Tenable Cloud Security	Google COS Security Checks	10/3/2026	10/6/2026	high
470557	Google: sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_18: security update to 19999.44.21	Tenable Cloud Security	Google COS Security Checks	10/3/2026	10/6/2026	high
471446	Google: sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_18: security update to 20085.0.0	Tenable Self-Hosted Container Security	Google COS Security Checks	10/3/2026	10/6/2026	high
365768	Ubuntu 26.04 LTS : Linux kernel (Azure) vulnerabilities (USN-8888-1)	Nessus	Ubuntu Local Security Checks	10/14/2026	10/14/2026	medium
334808	Linux Distros Unpatched Vulnerability : CVE-2026-68415	Nessus	Misc.	8/12/2026	10/23/2026	high
365767	Ubuntu 26.04 LTS : Linux kernel vulnerabilities (USN-8887-1)	Nessus	Ubuntu Local Security Checks	10/14/2026	10/14/2026	medium
365463	Ubuntu 26.04 LTS : Linux kernel (OEM) vulnerabilities (USN-8889-1)	Nessus	Ubuntu Local Security Checks	10/13/2026	10/13/2026	medium

Detections

Analytics

Plugins Search

high

high

high

high

medium

high

medium

medium