There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In the Linux kernel, the following vulnerability has been resolved: net/mlx5: HWS, change error flow on
    matcher disconnect Currently, when firmware failure occurs during matcher disconnect flow, the error flow
    of the function reconnects the matcher back and returns an error, which continues running the calling
    function and eventually frees the matcher that is being disconnected. This leads to a case where we have a
    freed matcher on the matchers list, which in turn leads to use-after-free and eventual crash. This patch
    fixes that by not trying to reconnect the matcher back when some FW command fails during disconnect. Note
    that we're dealing here with FW error. We can't overcome this problem. This might lead to bad steering
    state (e.g. wrong connection between matchers), and will also lead to resource leakage, as it is the case
    with any other error handling during resource destruction. However, the goal here is to allow the driver
    to continue and not crash the machine with use-after-free error. (CVE-2025-21751)

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

  - In the Linux kernel, the following vulnerability has been resolved: net: hns3: add vlan list lock to     protect vlan list When adding port base VLAN, vf VLAN need to remove from HW and modify the vlan state in     vf VLAN list as false. If the periodicity task is freeing the same node, it may cause use after free     error. This patch adds a vlan list lock to protect the vlan list. (CVE-2022-49182)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix reading strings from     synthetic events The follow commands caused a crash: # cd /sys/kernel/tracing # echo 's:open char file[]'     > dynamic_events # echo 'hist:keys=common_pid:file=filename:onchange($file).trace(open,$file)' >     events/syscalls/sys_enter_openat/trigger' # echo 1 > events/synthetic/open/enable BOOM! The problem is     that the synthetic event field char file[] will read the value given to it as a string without any     memory checks to make sure the address is valid. The above example will pass in the user space address and     the sythetic event code will happily call strlen() on it and then strscpy() where either one will cause an     oops when accessing user space addresses. Use the helper functions from trace_kprobe and trace_eprobe that     can read strings safely (and actually succeed when the address is from user space and the memory is mapped     in). Now the above can show: packagekitd-1721 [000] ...2. 104.597170: open:
    file=/usr/lib/rpm/fileattrs/cmake.attr in:imjournal-978 [006] ...2. 104.599642: open:
    file=/var/lib/rsyslog/imjournal.state.tmp packagekitd-1721 [000] ...2. 104.626308: open:
    file=/usr/lib/rpm/fileattrs/debuginfo.attr (CVE-2022-50255)

  - In the Linux kernel, the following vulnerability has been resolved: ipc: fix memleak if msg_init_ns failed     in create_ipc_ns Percpu memory allocation may failed during create_ipc_ns however this fail is not handled     properly since ipc sysctls and mq sysctls is not released properly. Fix this by release these two resource     when failure. Here is the kmemleak stack when percpu failed: unreferenced object 0xffff88819de2a600 (size     512): comm shmem_2nstest, pid 120711, jiffies 4300542254 hex dump (first 32 bytes): 60 aa 9d 84 ff ff ff     ff fc 18 48 b2 84 88 ff ff `.........H..... 04 00 00 00 a4 01 00 00 20 e4 56 81 ff ff ff ff ........
    .V..... backtrace (crc be7cba35): [<ffffffff81b43f83>] __kmalloc_node_track_caller_noprof+0x333/0x420     [<ffffffff81a52e56>] kmemdup_noprof+0x26/0x50 [<ffffffff821b2f37>] setup_mq_sysctls+0x57/0x1d0     [<ffffffff821b29cc>] copy_ipcs+0x29c/0x3b0 [<ffffffff815d6a10>] create_new_namespaces+0x1d0/0x920     [<ffffffff815d7449>] copy_namespaces+0x2e9/0x3e0 [<ffffffff815458f3>] copy_process+0x29f3/0x7ff0     [<ffffffff8154b080>] kernel_clone+0xc0/0x650 [<ffffffff8154b6b1>] __do_sys_clone+0xa1/0xe0     [<ffffffff843df8ff>] do_syscall_64+0xbf/0x1c0 [<ffffffff846000b0>]     entry_SYSCALL_64_after_hwframe+0x4b/0x53 (CVE-2024-53175)

  - In the Linux kernel, the following vulnerability has been resolved: net/mlx5: HWS, change error flow on     matcher disconnect Currently, when firmware failure occurs during matcher disconnect flow, the error flow     of the function reconnects the matcher back and returns an error, which continues running the calling     function and eventually frees the matcher that is being disconnected. This leads to a case where we have a     freed matcher on the matchers list, which in turn leads to use-after-free and eventual crash. This patch     fixes that by not trying to reconnect the matcher back when some FW command fails during disconnect. Note     that we're dealing here with FW error. We can't overcome this problem. This might lead to bad steering     state (e.g. wrong connection between matchers), and will also lead to resource leakage, as it is the case     with any other error handling during resource destruction. However, the goal here is to allow the driver     to continue and not crash the machine with use-after-free error. (CVE-2025-21751)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Avoid memory leak while     enabling statistics Driver uses monitor destination rings for extended statistics mode and standalone     monitor mode. In extended statistics mode, TLVs are parsed from the buffer received from the monitor     destination ring and assigned to the ppdu_info structure to update per-packet statistics. In standalone     monitor mode, along with per-packet statistics, the packet data (payload) is captured, and the driver     updates per MSDU to mac80211. When the AP interface is enabled, only extended statistics mode is     activated. As part of enabling monitor rings for collecting statistics, the driver subscribes to     HAL_RX_MPDU_START TLV in the filter configuration. This TLV is received from the monitor destination ring,     and kzalloc for the mon_mpdu object occurs, which is not freed, leading to a memory leak. The kzalloc for     the mon_mpdu object is only required while enabling the standalone monitor interface. This causes a memory     leak while enabling extended statistics mode in the driver. Fix this memory leak by removing the kzalloc     for the mon_mpdu object in the HAL_RX_MPDU_START TLV handling. Additionally, remove the standalone monitor     mode handlings in the HAL_MON_BUF_ADDR and HAL_RX_MSDU_END TLVs. These TLV tags will be handled properly     when enabling standalone monitor mode in the future. Tested-on: QCN9274 hw2.0 PCI     WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1 Tested-on: WCN7850 hw2.0 PCI     WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 (CVE-2025-37743)

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

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: net/mlx5: HWS, change error flow on     matcher disconnect Currently, when firmware failure occurs during matcher disconnect flow, the error flow     of the function reconnects the matcher back and returns an error, which continues running the calling     function and eventually frees the matcher that is being disconnected. This leads to a case where we have a     freed matcher on the matchers list, which in turn leads to use-after-free and eventual crash. This patch     fixes that by not trying to reconnect the matcher back when some FW command fails during disconnect. Note     that we're dealing here with FW error. We can't overcome this problem. This might lead to bad steering     state (e.g. wrong connection between matchers), and will also lead to resource leakage, as it is the case     with any other error handling during resource destruction. However, the goal here is to allow the driver     to continue and not crash the machine with use-after-free error. (CVE-2025-21751)

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

The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1789986443 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: net: hns3: add vlan list lock to     protect vlan list When adding port base VLAN, vf VLAN need to remove from HW and modify the vlan state in     vf VLAN list as false. If the periodicity task is freeing the same node, it may cause use after free     error. This patch adds a vlan list lock to protect the vlan list. (CVE-2022-49182)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix reading strings from     synthetic events The follow commands caused a crash: # cd /sys/kernel/tracing # echo 's:open char file[]'     > dynamic_events # echo 'hist:keys=common_pid:file=filename:onchange($file).trace(open,$file)' >     events/syscalls/sys_enter_openat/trigger' # echo 1 > events/synthetic/open/enable BOOM! The problem is     that the synthetic event field char file[] will read the value given to it as a string without any     memory checks to make sure the address is valid. The above example will pass in the user space address and     the sythetic event code will happily call strlen() on it and then strscpy() where either one will cause an     oops when accessing user space addresses. Use the helper functions from trace_kprobe and trace_eprobe that     can read strings safely (and actually succeed when the address is from user space and the memory is mapped     in). Now the above can show: packagekitd-1721 [000] ...2. 104.597170: open:
    file=/usr/lib/rpm/fileattrs/cmake.attr in:imjournal-978 [006] ...2. 104.599642: open:
    file=/var/lib/rsyslog/imjournal.state.tmp packagekitd-1721 [000] ...2. 104.626308: open:
    file=/usr/lib/rpm/fileattrs/debuginfo.attr (CVE-2022-50255)

  - In the Linux kernel, the following vulnerability has been resolved: ipc: fix memleak if msg_init_ns failed     in create_ipc_ns Percpu memory allocation may failed during create_ipc_ns however this fail is not handled     properly since ipc sysctls and mq sysctls is not released properly. Fix this by release these two resource     when failure. Here is the kmemleak stack when percpu failed: unreferenced object 0xffff88819de2a600 (size     512): comm shmem_2nstest, pid 120711, jiffies 4300542254 hex dump (first 32 bytes): 60 aa 9d 84 ff ff ff     ff fc 18 48 b2 84 88 ff ff `.........H..... 04 00 00 00 a4 01 00 00 20 e4 56 81 ff ff ff ff ........
    .V..... backtrace (crc be7cba35): [<ffffffff81b43f83>] __kmalloc_node_track_caller_noprof+0x333/0x420     [<ffffffff81a52e56>] kmemdup_noprof+0x26/0x50 [<ffffffff821b2f37>] setup_mq_sysctls+0x57/0x1d0     [<ffffffff821b29cc>] copy_ipcs+0x29c/0x3b0 [<ffffffff815d6a10>] create_new_namespaces+0x1d0/0x920     [<ffffffff815d7449>] copy_namespaces+0x2e9/0x3e0 [<ffffffff815458f3>] copy_process+0x29f3/0x7ff0     [<ffffffff8154b080>] kernel_clone+0xc0/0x650 [<ffffffff8154b6b1>] __do_sys_clone+0xa1/0xe0     [<ffffffff843df8ff>] do_syscall_64+0xbf/0x1c0 [<ffffffff846000b0>]     entry_SYSCALL_64_after_hwframe+0x4b/0x53 (CVE-2024-53175)

  - In the Linux kernel, the following vulnerability has been resolved: net/mlx5: HWS, change error flow on     matcher disconnect Currently, when firmware failure occurs during matcher disconnect flow, the error flow     of the function reconnects the matcher back and returns an error, which continues running the calling     function and eventually frees the matcher that is being disconnected. This leads to a case where we have a     freed matcher on the matchers list, which in turn leads to use-after-free and eventual crash. This patch     fixes that by not trying to reconnect the matcher back when some FW command fails during disconnect. Note     that we're dealing here with FW error. We can't overcome this problem. This might lead to bad steering     state (e.g. wrong connection between matchers), and will also lead to resource leakage, as it is the case     with any other error handling during resource destruction. However, the goal here is to allow the driver     to continue and not crash the machine with use-after-free error. (CVE-2025-21751)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Avoid memory leak while     enabling statistics Driver uses monitor destination rings for extended statistics mode and standalone     monitor mode. In extended statistics mode, TLVs are parsed from the buffer received from the monitor     destination ring and assigned to the ppdu_info structure to update per-packet statistics. In standalone     monitor mode, along with per-packet statistics, the packet data (payload) is captured, and the driver     updates per MSDU to mac80211. When the AP interface is enabled, only extended statistics mode is     activated. As part of enabling monitor rings for collecting statistics, the driver subscribes to     HAL_RX_MPDU_START TLV in the filter configuration. This TLV is received from the monitor destination ring,     and kzalloc for the mon_mpdu object occurs, which is not freed, leading to a memory leak. The kzalloc for     the mon_mpdu object is only required while enabling the standalone monitor interface. This causes a memory     leak while enabling extended statistics mode in the driver. Fix this memory leak by removing the kzalloc     for the mon_mpdu object in the HAL_RX_MPDU_START TLV handling. Additionally, remove the standalone monitor     mode handlings in the HAL_MON_BUF_ADDR and HAL_RX_MSDU_END TLVs. These TLV tags will be handled properly     when enabling standalone monitor mode in the future. Tested-on: QCN9274 hw2.0 PCI     WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1 Tested-on: WCN7850 hw2.0 PCI     WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 (CVE-2025-37743)

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

An update of the linux package has been released.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2025-948 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    PCI/ASPM: Fix link state exit during switch upstream function removal (CVE-2024-58093)

    In the Linux kernel, the following vulnerability has been resolved:

    net/mlx5: HWS, change error flow on matcher disconnect (CVE-2025-21751)

    In the Linux kernel, the following vulnerability has been resolved:

    nfsd: fix management of listener transports (CVE-2025-22024)

    In the Linux kernel, the following vulnerability has been resolved:

    nfsd: put dl_stid if fail to queue dl_recall (CVE-2025-22025)

    In the Linux kernel, the following vulnerability has been resolved:

    media: streamzap: fix race between device disconnection and urb callback (CVE-2025-22027)

    In the Linux kernel, the following vulnerability has been resolved:

    mm: zswap: fix crypto_free_acomp() deadlock in zswap_cpu_comp_dead() (CVE-2025-22030)

    In the Linux kernel, the following vulnerability has been resolved:

    arm64: Don't call NULL in do_compat_alignment_fixup() (CVE-2025-22033)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/gup: reject FOLL_SPLIT_PMD with hugetlb VMAs (CVE-2025-22034)

    In the Linux kernel, the following vulnerability has been resolved:

    tracing: Fix use-after-free in print_graph_function_flags during tracer switching (CVE-2025-22035)

    In the Linux kernel, the following vulnerability has been resolved:

    exfat: fix random stack corruption after get_block (CVE-2025-22036)

    In the Linux kernel, the following vulnerability has been resolved:

    acpi: nfit: fix narrowing conversion in acpi_nfit_ctl (CVE-2025-22044)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs (CVE-2025-22045)

    In the Linux kernel, the following vulnerability has been resolved:

    uprobes/x86: Harden uretprobe syscall trampoline check (CVE-2025-22046)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/microcode/AMD: Fix __apply_microcode_amd()'s return value (CVE-2025-22047)

    In the Linux kernel, the following vulnerability has been resolved:

    net: fix geneve_opt length integer overflow (CVE-2025-22055)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nft_tunnel: fix geneve_opt type confusion addition (CVE-2025-22056)

    In the Linux kernel, the following vulnerability has been resolved:

    net: decrease cached dst counters in dst_release (CVE-2025-22057)

    In the Linux kernel, the following vulnerability has been resolved:

    udp: Fix memory accounting leak. (CVE-2025-22058)

    In the Linux kernel, the following vulnerability has been resolved:

    udp: Fix multiple wraparounds of sk->sk_rmem_alloc. (CVE-2025-22059)

    In the Linux kernel, the following vulnerability has been resolved:

    sctp: add mutual exclusion in proc_sctp_do_udp_port() (CVE-2025-22062)

    In the Linux kernel, the following vulnerability has been resolved:

    netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets (CVE-2025-22063)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nf_tables: don't unregister hook when table is dormant (CVE-2025-22064)

    In the Linux kernel, the following vulnerability has been resolved:

    rtnetlink: Allocate vfinfo size for VF GUIDs when supported (CVE-2025-22075)

    In the Linux kernel, the following vulnerability has been resolved:

    exfat: fix missing shutdown check (CVE-2025-22076)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: Prevent integer overflow in hdr_first_de() (CVE-2025-22080)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: Fix a couple integer overflows on 32bit systems (CVE-2025-22081)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/core: Fix use-after-free when rename device name (CVE-2025-22085)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow (CVE-2025-22086)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Fix array bounds error with may_goto (CVE-2025-22087)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/core: Don't expose hw_counters outside of init net namespace (CVE-2025-22089)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() (CVE-2025-22090)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/mlx5: Fix page_size variable overflow (CVE-2025-22091)

    In the Linux kernel, the following vulnerability has been resolved:

    thermal: int340x: Add NULL check for adev (CVE-2025-23136)

    In the Linux kernel, the following vulnerability has been resolved:

    watch_queue: fix pipe accounting mismatch (CVE-2025-23138)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: fix OOB read when checking dotdot dir (CVE-2025-37785)

    In the Linux kernel, the following vulnerability has been resolved:

    net_sched: skbprio: Remove overly strict queue assertions (CVE-2025-38637)

    In the Linux kernel, the following vulnerability has been resolved:

    nfsd: allow SC_STATUS_FREEABLE when searching via nfs4_lookup_stateid() (CVE-2025-39688)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/mce: use is_copy_from_user() to determine copy-from-user context (CVE-2025-39989)

Tenable has extracted the preceding description block directly from the tested product security advisory.

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

The remote Debian 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6008 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6008-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     September 22, 2025                    https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2025-21751 CVE-2025-22103 CVE-2025-22113 CVE-2025-22124                      CVE-2025-22125 CVE-2025-23133 CVE-2025-38272 CVE-2025-38306                      CVE-2025-38453 CVE-2025-38502 CVE-2025-38556 CVE-2025-38676                      CVE-2025-38677 CVE-2025-38730 CVE-2025-38732 CVE-2025-38733                      CVE-2025-38734 CVE-2025-38735 CVE-2025-38736 CVE-2025-38737                      CVE-2025-39673 CVE-2025-39675 CVE-2025-39676 CVE-2025-39679                      CVE-2025-39681 CVE-2025-39682 CVE-2025-39683 CVE-2025-39684                      CVE-2025-39685 CVE-2025-39686 CVE-2025-39687 CVE-2025-39689                      CVE-2025-39691 CVE-2025-39692 CVE-2025-39693 CVE-2025-39694                      CVE-2025-39695 CVE-2025-39697 CVE-2025-39698 CVE-2025-39700                      CVE-2025-39701 CVE-2025-39702 CVE-2025-39703 CVE-2025-39705                      CVE-2025-39706 CVE-2025-39707 CVE-2025-39709 CVE-2025-39710                      CVE-2025-39711 CVE-2025-39712 CVE-2025-39713 CVE-2025-39714                      CVE-2025-39715 CVE-2025-39716 CVE-2025-39718 CVE-2025-39719                      CVE-2025-39720 CVE-2025-39721 CVE-2025-39722 CVE-2025-39723                      CVE-2025-39724 CVE-2025-39759 CVE-2025-39765 CVE-2025-39766                      CVE-2025-39767 CVE-2025-39770 CVE-2025-39772 CVE-2025-39773                      CVE-2025-39776 CVE-2025-39779 CVE-2025-39780 CVE-2025-39781                      CVE-2025-39782 CVE-2025-39783 CVE-2025-39787 CVE-2025-39788                      CVE-2025-39790 CVE-2025-39791 CVE-2025-39800 CVE-2025-39801                      CVE-2025-39805 CVE-2025-39806 CVE-2025-39807 CVE-2025-39808                      CVE-2025-39810 CVE-2025-39811 CVE-2025-39812 CVE-2025-39813                      CVE-2025-39815 CVE-2025-39817 CVE-2025-39819 CVE-2025-39823                      CVE-2025-39824 CVE-2025-39825 CVE-2025-39826 CVE-2025-39827                      CVE-2025-39828 CVE-2025-39829 CVE-2025-39831 CVE-2025-39832                      CVE-2025-39835 CVE-2025-39836 CVE-2025-39838 CVE-2025-39839                      CVE-2025-39841 CVE-2025-39842 CVE-2025-39843 CVE-2025-39844                      CVE-2025-39845 CVE-2025-39846 CVE-2025-39847 CVE-2025-39848                      CVE-2025-39849 CVE-2025-39850 CVE-2025-39851 CVE-2025-39852                      CVE-2025-39853 CVE-2025-39854 CVE-2025-39857 CVE-2025-39860                      CVE-2025-39861 CVE-2025-39863 CVE-2025-39864 CVE-2025-39865                      CVE-2025-39866 CVE-2025-40300

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For the stable distribution (trixie), these problems have been fixed in     version 6.12.48-1.

    We recommend that you upgrade your linux packages.

    For the detailed security status of linux please refer to its security     tracker page at:
    https://security-tracker.debian.org/tracker/linux

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

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

ID	Name	Product	Family	Published	Updated	Severity
428155	Bottlerocket: bottlerocket-kernel-6.12, kernel-6.12: security update to 6.12.23	Tenable Self-Hosted Container Security	Bottlerocket Local Security Checks	6/30/2025	10/16/2026	high
428155	Bottlerocket: bottlerocket-kernel-6.12, kernel-6.12: security update to 6.12.23	Tenable Cloud Security	Bottlerocket Local Security Checks	6/30/2025	10/16/2026	high
352548	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1789986443)	Nessus	Alma Linux Local Security Checks	9/30/2026	9/30/2026	high
231715	Linux Distros Unpatched Vulnerability : CVE-2025-21751	Nessus	Misc.	3/6/2025	7/18/2026	high
352273	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1789986443)	Nessus	Rocky Linux Local Security Checks	9/30/2026	9/30/2026	high
313507	Photon OS 5.0: Linux PHSA-2026-5.0-0842	Nessus	PhotonOS Local Security Checks	5/9/2026	10/13/2026	high
332421	Photon OS 5.0: Linux PHSA-2026-5.0-91-0842	Nessus	PhotonOS Local Security Checks	8/5/2026	8/18/2026	high
234946	Amazon Linux 2023 : bpftool, kernel6.12, kernel6.12-modules-extra (ALAS2023-2025-948)	Nessus	Amazon Linux Local Security Checks	4/29/2025	2/13/2026	high
332386	Photon OS 5.0: Linux PHSA-2026-5.0-92-0842	Nessus	PhotonOS Local Security Checks	8/5/2026	8/22/2026	high
265710	Debian dsa-6008 : ata-modules-6.12.31-armmp-di - security update	Nessus	Debian Local Security Checks	9/22/2025	9/18/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high

high

high

high