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

  - bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized When CONFIG_BPF_LSM=y is set,     BPF inode storage maps (BPF_MAP_TYPE_INODE_STORAGE) are compiled into the kernel. However, if the BPF LSM     is not explicitly enabled at boot time (e.g. omitted from the lsm= boot parameter), lsm_prepare() is     never executed for the BPF LSM. Consequently, the BPF inode security blob offset     (bpf_lsm_blob_sizes.lbs_inode) is never initialized and remains at its default compiled size of 8 bytes     instead of being updated to a valid offset past the reserved struct rcu_head (typically 16 bytes or more).
    When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGE map, bpf_inode() evaluates     inode->i_security + 8. This erroneously aliases the struct rcu_head.func callback pointer at the beginning     of the inode->i_security blob. During subsequent map element cleanup or inode destruction, writing NULL to     owner_storage clears the queued RCU callback pointer. When rcu_do_batch() later executes the queued     callback, it attempts an instruction fetch at address 0x0, triggering an immediate kernel panic. Fix this     by introducing a global bpf_lsm_initialized boolean flag marked with __ro_after_init. Set this flag to     true inside bpf_lsm_init() when the LSM framework successfully registers the BPF LSM. Gate map allocation     in inode_storage_map_alloc() on this flag, returning -EOPNOTSUPP if the BPF LSM is in turn uninitialized.
    This fail-fast approach prevents userspace from allocating inode storage maps when the supporting BPF LSM     infrastructure is absent, avoiding zombie map states. (CVE-2026-64192)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2026-64192

high Nessus Plugin ID 328344

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.5 Aug 7, 2026, 9:55 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202608072155
Version 1.4 Aug 1, 2026, 2:26 AM CVSS metrics ("CVSSv2 score" set to 6.9) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:M/Au:N/C:C/I:C/A:C") CVSSv2 severity (based on CVE-2026-64192, severity decreased from "High" to "Medium") Detection (updated detection logic) Plugin metadata Plugin Feed: 202608010226
Version 1.3 Jul 25, 2026, 1:06 PM CVSS metrics ("CVSSv2 score" set to 7.2) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:C/I:C/A:C") CVSSv2 severity (based on CVE-2026-64192, severity increased from "Medium" to "High") Detection (updated detection logic) Plugin metadata Plugin Feed: 202607251306
Version 1.2 Jul 21, 2026, 8:31 PM CVSS metrics ("CVSSv2 score" set to 6.6. "CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:N/I:C/A:C". "CVSSv3 score" set to 7.8. "CVSSv3 vector" set to "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H") CVSSv2 severity (based on CVE-2026-64192, severity decreased from "High" to "Medium") Detection (updated detection logic) New Plugin metadata Plugin Feed: 202607212031