The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1778896895 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: can: raw: fix ro->uniq use-after-free     in raw_rcv() raw_release() unregisters raw CAN receive filters via can_rx_unregister(), but receiver     deletion is deferred with call_rcu(). This leaves a window where raw_rcv() may still be running in an RCU     read-side critical section after raw_release() frees ro->uniq, leading to a use-after-free of the percpu     uniq storage. Move free_percpu(ro->uniq) out of raw_release() and into a raw-specific socket destructor.
    can_rx_unregister() takes an extra reference to the socket and only drops it from the RCU callback, so     freeing uniq from sk_destruct ensures the percpu area is not released until the relevant callbacks have     drained. [mkl: applied manually] (CVE-2026-31532)

  - In the Linux kernel, the following vulnerability has been resolved: ptrace: slightly saner     'get_dumpable()' logic The 'dumpability' of a task is fundamentally about the memory image of the task -     the concept comes from whether it can core dump or not - and makes no sense when you don't have an     associated mm. And almost all users do in fact use it only for the case where the task has a mm pointer.
    But we have one odd special case: ptrace_may_access() uses 'dumpable' to check various other things     entirely independently of the MM (typically explicitly using flags like PTRACE_MODE_READ_FSCREDS).
    Including for threads that no longer have a VM (and maybe never did, like most kernel threads). It's not     what this flag was designed for, but it is what it is. The ptrace code does check that the uid/gid     matches, so you do have to be uid-0 to see kernel thread details, but this means that the traditional     drop capabilities model doesn't make any difference for this all. Make it all make a *bit* more sense by     saying that if you don't have a MM pointer, we'll use a cached last dumpability flag if the thread ever     had a MM (it will be zero for kernel threads since it is never set), and require a proper CAP_SYS_PTRACE     capability to override. (CVE-2026-46333)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1778896895)

high Nessus Plugin ID 360237

Version 1.3

Version 1.2

Version 1.1

Version 1.3 Oct 22, 2026, 12:02 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202610220002
Version 1.2 Oct 15, 2026, 8:27 AM CVSS temporal metrics ("CVSSv2 temporal vector" set to "CVSS2#E:H/RL:OF/RC:C") CVSS temporal metrics ("CVSSv3 temporal vector" set to "CVSS:3.0/E:H/RL:O/RC:C") Exploit attributes ("Exploited by malware" set to "True") Plugin Feed: 202610150827
Version 1.1 Oct 1, 2026, 9:59 PM New Plugin Feed: 202610012159