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

  - mm/secretmem: properly account locked pages secretmem accounts folios by treating memory as if it were     mlock()'d and thus limited by the RLIMIT_MEMLOCK limit. However the folios are unevictable and remain so     until the inode is evicted, eliminating usual mlock() semantics - mapping folios then unmapping them does     not clear their unevictable state, since it depends on AS_UNEVICTABLE, not PG_mlocked. A user can     therefore easily work around the RLIMIT_MEMLOCK limit - simply map then unmap and VmLck no longer counts     the secretmem range. Worse, folios are not accounted in the process's RSS, meaning the OOM killer won't     know to kill the process. Repeatedly mapping/unmapping (or forking) can then result in the consumption of     all available system memory with unevictable folios and cause system instability. A secretmem fd can be     passed between processes and over fork so a per-process limit simply does not make sense, so follow the     precedent set by io_uring, perf, skbuff, iommufd and xdp by tracking the number of locked pages in     user_struct->locked_vm. Since the scope tracked is actually inode lifetime, the RLIMIT_MEMLOCK applies     per-user not per-process, so it doesn't make sense to bypass for users with CAP_IPC_LOCK, therefore remove     this bypass. There is simply no reason to carry on marking the mapping as mlock()'d since it's misleading     and the lifecycle is now correctly handled, so remove this too. Note that secretmem does not support any     form of truncation (including hole punching) and the folios are unreclaimable, so the folios need only be     accounted on fault and unaccounted on inode destruction. __secretmem_account_pages() is more or less a     duplicate of the code that io_uring etc. use, but since this is a bug fix that needs backporting, defer     any de-duplication efforts to a follow-up. test_mlock_limit() asserts mlock_future_ok() on mmap(), however     this has been removed, so remove the test altogether for the fix. A new test will be sent separately for     upstream. (CVE-2026-93243)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2026-93243

medium Nessus Plugin ID 350114

Version 1.9

Version 1.8

Version 1.7

Version 1.6

Version 1.5

Version 1.2

Version 1.1

Version 1.9 Nov 7, 2026, 4:01 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202611070401
Version 1.8 Nov 4, 2026, 12:13 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202611041213
Version 1.7 Oct 31, 2026, 12:23 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202610311223
Version 1.6 Oct 29, 2026, 9:47 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202610292147
Version 1.5 Oct 22, 2026, 12:02 AM CVSS metrics ("CVSSv2 score" set to 4.9. "CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:N/I:N/A:C") CVSSv2 severity (based on CVE-2026-93243, severity increased from "Low" to "Medium") Detection (updated detection logic) Plugin metadata Plugin Feed: 202610220002
Version 1.2 Sep 25, 2026, 6:49 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202609251849
Version 1.1 Sep 25, 2026, 12:17 PM New Plugin Feed: 202609251217