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

  - mm/mseal: update VMA end correctly on merge Previously we stored the end of the current VMA in curr_end,     and then upon iterating to the next VMA updated curr_start to curr_end to advance to the next VMA.
    However, this doesn't take into account the fact that a VMA might be updated due to a merge by     vma_modify_flags(), which can result in curr_end being stale and thus, upon setting curr_start to     curr_end, ending up with an incorrect curr_start on the next iteration. Resolve the issue by setting     curr_end to vma->vm_end unconditionally to ensure this value remains updated should this occur. While     we're here, eliminate this entire class of bug by simply setting const curr_[start/end] to be clamped to     the input range and VMAs, which also happens to simplify the logic. (CVE-2026-23416)

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

ID	Name	Product	Family	Published	Updated	Severity
316948	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1746)	Nessus	Amazon Linux Local Security Checks	5/27/2026	7/16/2026	high
304752	Linux Distros Unpatched Vulnerability : CVE-2026-23416	Nessus	Misc.	4/3/2026	7/31/2026	medium

Detections

Analytics

Plugins Search

high

medium