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: sched/fair: Fix zero_vruntime tracking     fix John reported that stress-ng-yield could make his machine unhappy and managed to bisect it to commit     b3d99f43c72b (sched/fair: Fix zero_vruntime tracking). The combination of yield and that commit was     specific enough to hypothesize the following scenario: Suppose we have 2 runnable tasks, both doing yield.
    Then one will be eligible and one will not be, because the average position must be in between these two     entities. Therefore, the runnable task will be eligible, and be promoted a full slice (all the tasks do is     yield after all). This causes it to jump over the other task and now the other task is eligible and     current is no longer. So we schedule. Since we are runnable, there is no {de,en}queue. All we have is the
    __{en,de}queue_entity() from {put_prev,set_next}_task(). But per the fingered commit, those two no longer     move zero_vruntime. All that moves zero_vruntime are tick and full {de,en}queue. This means, that if the     two tasks playing leapfrog can reach the critical speed to reach the overflow point inside one tick's     worth of time, we're up a creek. Additionally, when multiple cgroups are involved, there is no guarantee     the tick will in fact hit every cgroup in a timely manner. Statistically speaking it will, but that same     statistics does not rule out the possibility of one cgroup not getting a tick for a significant amount of     time -- however unlikely. Therefore, just like with the yield() case, force an update at the end of every     slice. This ensures the update is never more than a single slice behind and the whole thing is within 2     lag bounds as per the comment on entity_key(). (CVE-2026-43323)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2026-43323

medium Nessus Plugin ID 314411

Version 1.7

Version 1.6

Version 1.5

Version 1.3

Version 1.2

Version 1.1

Version 1.7 May 29, 2026, 5:27 PM CVSS metrics ("CVSSv2 score" set to 5.6) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:N/I:P/A:C") Detection (updated detection logic) Plugin metadata Plugin Feed: 202605291727
Version 1.6 May 26, 2026, 6:39 AM CVSS metrics ("CVSSv2 score" set to 4.6) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:N/I:N/A:C") Plugin Feed: 202605260639
Version 1.5 May 25, 2026, 10:30 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202605252230
Version 1.3 May 18, 2026, 10:04 AM CVSS metrics ("CVSSv2 score" set to 4.6) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:N/I:N/A:C") Plugin Feed: 202605181004
Version 1.2 May 15, 2026, 6:15 PM CVSS metrics ("CVSSv2 score" set to 5.6) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:N/I:P/A:C") CVSSv2 severity (based on CVE-2026-43323, severity increased from "Low" to "Medium") Detection (updated detection logic) Plugin metadata Plugin Feed: 202605151815
Version 1.1 May 14, 2026, 3:47 AM New Plugin Feed: 202605140347