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

  - namespace: don't inherit MNT_UMOUNT in clone_mnt() MNT_UMOUNT gets raised on a mount that umount_tree() or     umount_one() has taken out of its namespace. It's never cleared. __detach_mounts() unhooks a mount that     carries it instead of unmounting it. disconnect_mount() lets an unmounted child stay attached only if its     parent carries it. propagate_umount() takes it as the sign that a mount is going to be unmounted when it     decides what else can be unmounted, where a chain of locked mounts ends and where a for reparenting an     overmount. clone_mnt() copies the flags of the source and only masks MNT_INTERNAL_FLAGS which doesn't     include MNT_UMOUNT. A mount that was lazily unmounted but is kept alive by a file descriptor can still be     copied when its root is an nsfs or pidfs file because may_copy_tree() accepts those before checking     whether the source is mounted at all: mount --bind /proc/self/ns/net /tmp/x exec 3< /tmp/x umount -l     /tmp/x mount --bind /proc/self/fd/3 /tmp/y The mount on /tmp/y is attached to the caller's namespace with     MNT_UMOUNT already set and every copy of it inherits the flag again. That causes a number of bugs: -     Unlink its mountpoint from a mount namespace where it isn't one. __detach_mounts() takes it for a mount     that was unmounted earlier, unhooks it from its parent and drops the reference the namespace holds on it.
    It stays in the namespace with one reference too few and as its own parent, so it can't be unmounted     through the file descriptor anymore and the namespace never finds it again. When the namespace goes away     it's leaked and points to a freed struct mnt_namespace that may_change_propagation() and anon_ns_root()     read on the next propagation change or mount_setattr() through the file descriptor. - Make it shared and     unmount a peer. trace_transfers() follows the flag from the peer into it and strips it from its peer     group. - Let a propagated umount reach it. gather_candidates() marks it with T_UMOUNT_CANDIDATE but never     puts it on the candidate list, so the mark is never cleared and every later propagated umount skips it. If     it's the parent of a locked mount handle_locked() takes it as the cutoff and commits the locked child that     should have stayed and disconnect_mount() leaves that child attached to it, unmounted under a mounted     parent, which is what disconnect_mount() exists to prevent. When the namespace goes away umount_tree()     visits the child a second time. And once __detach_mounts() has made it its own parent reparent() never     finds the end of the chain of unmounted parents. A clone is a new mount that has never been unmounted. Add     MNT_UMOUNT to MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when umount_tree() reaches a     mount that already has it set. (CVE-2026-98993)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2026-98993

high Nessus Plugin ID 371582

Version 1.12

Version 1.11

Version 1.10

Version 1.9

Version 1.8

Version 1.6

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.1

Version 1.12 Nov 12, 2026, 7:08 AM CVSS metrics ("CVSSv2 score" set to 6.9. "CVSSv2 vector" set to "CVSS2#AV:L/AC:M/Au:N/C:C/I:C/A:C") Detection (updated detection logic) Plugin metadata Plugin Feed: 202611120708
Version 1.11 Nov 9, 2026, 3:50 PM CVSS metrics ("CVSSv2 score" set to 6.8. "CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C") Plugin Feed: 202611091550
Version 1.10 Nov 7, 2026, 10:50 AM Detection (updated detection logic) Plugin Feed: 202611071050
Version 1.9 Nov 6, 2026, 2:22 PM CVSS metrics ("CVSSv2 score" set to 6.9. "CVSSv2 vector" set to "CVSS2#AV:L/AC:M/Au:N/C:C/I:C/A:C") Detection (updated detection logic) Plugin metadata Plugin Feed: 202611061422
Version 1.8 Nov 4, 2026, 12:13 PM CVSS metrics ("CVSSv2 score" set to 6.8. "CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C") Plugin Feed: 202611041213
Version 1.6 Oct 30, 2026, 8:32 AM CVSS metrics ("CVSSv2 score" set to 6.8) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C") Plugin Feed: 202610300832
Version 1.5 Oct 29, 2026, 3:00 PM 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") Detection (updated detection logic) Plugin metadata Plugin Feed: 202610291500
Version 1.4 Oct 28, 2026, 8:56 AM CVSS metrics ("CVSSv2 score" set to 6.8. "CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C") Detection (updated detection logic) Plugin metadata Plugin Feed: 202610280856
Version 1.3 Oct 27, 2026, 4:13 PM 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") Detection (updated detection logic) Plugin metadata Plugin Feed: 202610271613
Version 1.2 Oct 27, 2026, 9:59 AM CVSS metrics ("CVSSv2 score" set to 6.8) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C") CVSS metrics ("CVSSv3 score" set to 7.8) CVSS metrics ("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-98993, severity decreased from "High" to "Medium") Plugin Feed: 202610270959
Version 1.1 Oct 24, 2026, 2:50 AM New Plugin Feed: 202610240250