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

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

    drm: Fix potential null-ptr-deref due to drmm_mode_config_init() (CVE-2022-50556)

    A double-free vulnerability was found in the handling of IORING_OP_SOCKET operation with io_uring on the     Linux kernel. (CVE-2023-1032)

    Due to a type confusion during initializations, the tun and tap sockets in the Linux Kernel have their     socket UID hardcoded to 0, i.e. root. While it will be often correct, as TUN/TAP devices require     CAP_NET_ADMIN, it may not always be the case. The socket UID may be used for network filtering and     routing, thus TUN/TAP sockets may be incorrectly managed, potentially bypassing network filters based on     UID. (CVE-2023-1076)

    kernel: Type confusion in pick_next_rt_entity(), which can result in memory corruption. (CVE-2023-1077)

    A flaw use after free in the Linux kernel integrated infrared receiver/transceiver driver was found in the     way user detaching rc device. A local user could use this flaw to crash the system or potentially escalate     their privileges on the system. (CVE-2023-1118)

    A use-after-free vulnerability in the Linux Kernel traffic control index filter (tcindex) can be exploited     to achieve local privilege escalation. The tcindex_delete function which does not properly deactivate     filters in case of a perfect hashes while deleting the underlying structure which can later lead to double     freeing the structure. A local attacker user can use this vulnerability to elevate its privileges to     root.We recommend upgrading past commit 8c710f75256bb3cf05ac7b1672c82b92c43f3d28. (CVE-2023-1829)

    When plain IBRS is enabled (not enhanced IBRS), the logic in spectre_v2_user_select_mitigation()     determines that STIBP is not needed. The IBRS bit implicitly protects against cross-thread branch     targetinjection. However, with legacy IBRS, the IBRS bit is cleared on returning to userspace for     performance reasons which leaves userspace threads vulnerable to cross-thread branch target injection     against which STIBP protects. (CVE-2023-1998)

    A use-after-free flaw was found in hfsplus_put_super in fs/hfsplus/super.c in the Linux Kernel. This flaw     could allow a local user to cause a denial of service. (CVE-2023-2985)

    An issue was discovered in lib/kobject.c in the Linux kernel before 6.2.3. With root access, an attacker     can trigger a race condition that results in a fill_kobj_path out-of-bounds write. (CVE-2023-45863)

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

    vfio/type1: prevent underflow of locked_vm via exec() (CVE-2023-53171)

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

    USB: uhci: fix memory leak with using debugfs_lookup() (CVE-2023-53197)

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

    netfilter: x_tables: fix percpu counter block leak on error path when creating new netns (CVE-2023-53200)

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

    PM: domains: fix memory leak with using debugfs_lookup() (CVE-2023-53202)

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

    driver core: location: Free struct acpi_pld_info *pld before return false (CVE-2023-53211)

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

    arm64: efi: Make efi_rt_lock a raw_spinlock (CVE-2023-53216)

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

    watchdog: Fix kmemleak in watchdog_cdev_register (CVE-2023-53234)

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

    xsk: check IFF_UP earlier in Tx path (CVE-2023-53240)

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

    firmware: dmi-sysfs: Fix null-ptr-deref in dmi_sysfs_register_handle (CVE-2023-53250)

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

    cacheinfo: Fix shared_cpu_map to handle shared caches at different levels (CVE-2023-53254)

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

    VMCI: check context->notify_page after call to get_user_pages_fast() to avoid GPF (CVE-2023-53259)

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

    misc: vmw_balloon: fix memory leak with using debugfs_lookup() (CVE-2023-53279)

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

    udf: Do not update file length for failed writes to inline files (CVE-2023-53295)

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

    rbd: avoid use-after-free in do_rbd_add() when rbd_dev_create() fails (CVE-2023-53307)

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

    genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask() (CVE-2023-53332)

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

    USB: fix memory leak with using debugfs_lookup() (CVE-2023-53359)

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

    block: be a bit more careful in checking for NULL bdev while polling (CVE-2023-53366)

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

    crypto: seqiv - Handle EBUSY correctly (CVE-2023-53373)

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

    NFSD: fix leaked reference count of nfsd4_ssc_umount_item (CVE-2023-53381)

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

    drivers: base: dd: fix memory leak with using debugfs_lookup() (CVE-2023-53390)

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

    trace/blktrace: fix memory leak with using debugfs_lookup() (CVE-2023-53408)

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

    drivers: base: component: fix memory leak with using debugfs_lookup() (CVE-2023-53409)

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

    PM: EM: fix memory leak with using debugfs_lookup() (CVE-2023-53411)

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

    objtool: Fix memory leak in create_static_call_sections() (CVE-2023-53423)

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

    cifs: Fix warning and UAF when destroy the MR list (CVE-2023-53427)

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

    ipv6: Add lwtunnel encap size of all siblings in nexthop calculation (CVE-2023-53477)

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

    iommu: Fix error unwind in iommu_group_alloc() (CVE-2023-53482)

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

    crypto: xts - Handle EBUSY correctly (CVE-2023-53494)

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

    udf: Do not bother merging very long extents (CVE-2023-53506)

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

    io_uring: fix fget leak when fs don't support nowait buffered read (CVE-2023-53511)

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

    sctp: add a refcnt in sctp_stream_priorities to avoid a nested loop (CVE-2023-53590)

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

    driver core: fix resource leak in device_add() (CVE-2023-53594)

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

    nfsd: clean up potential nfsd_file refcount leaks in COPY codepath (CVE-2023-53606)

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

    irqchip: Fix refcount leak in platform_irqchip_probe (CVE-2023-53610)

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

    nvme-tcp: don't access released socket during error recovery (CVE-2023-53643)

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

    srcu: Delegate work to the boot cpu if using SRCU_SIZE_SMALL (CVE-2023-53671)

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

    drm/i915: Fix system suspend without fbdev being initialized (CVE-2023-53678)

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

    udf: Detect system inodes linked into directory hierarchy (CVE-2023-53695)

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

    ring-buffer: Handle race between rb_move_tail and rb_check_pages (CVE-2023-53709)

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

    KVM: VMX: Fix crash due to uninitialized current_vmcs (CVE-2023-53756)

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

    dm cache: free background tracker's queued work in btracker_destroy (CVE-2023-53765)

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

    blk-iocost: fix divide by 0 error in calc_lcoefs() (CVE-2023-53783)

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

    iommu/amd: Improve page fault error reporting (CVE-2023-53789)

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

    bpf: Zeroing allocated object from slab in bpf memory allocator (CVE-2023-53790)

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

    PCI: Fix dropping valid root bus resources with .end = zero (CVE-2023-53814)

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

    loop: loop_set_status_from_info() check before assignment (CVE-2023-53820)

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

    usb: early: xhci-dbc: Fix a potential out-of-bound memory access (CVE-2023-53840)

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

    KVM: Destroy target device if coalesced MMIO unregistration fails (CVE-2023-54024)

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

    crypto: essiv - Handle EBUSY correctly (CVE-2023-54046)

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

    iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter (CVE-2023-54057)

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

    blk-cgroup: dropping parent refcount after pd_free_fn() is done (CVE-2023-54107)

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

    leds: led-core: Fix refcount leak in of_led_get() (CVE-2023-54190)

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

    tty: fix out-of-bounds access in tty_driver_lookup_tty() (CVE-2023-54198)

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

    netfilter: ebtables: fix table blob use-after-free (CVE-2023-54243)

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

    cifs: Fix lost destroy smbd connection when MR allocate failed (CVE-2023-54260)

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

    ext4: refuse to create ea block when umounted (CVE-2023-54305)

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

    net: tls: avoid hanging tasks on the tx_lock (CVE-2023-54306)

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

    dm flakey: don't corrupt the zero page (CVE-2023-54317)

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

    driver core: fix potential null-ptr-deref in device_add() (CVE-2023-54321)

    kernel: refcount leak in ctnetlink_create_conntrack() (CVE-2023-7192)

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 AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1767864313 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scpi: Ensure scpi_info     is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the     scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then it could     result use-after-free as the value is exported via get_scpi_ops() and could refer to a memory allocated     via devm_kzalloc() but freed when the probe fails. (CVE-2022-50087)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: rtlwifi: Fix global-out-of-     bounds bug in _rtl8812ae_phy_set_txpower_limit() There is a global-out-of-bounds reported by KASAN: BUG:
    KASAN: global-out-of-bounds in _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] Read of size 1 at addr     ffffffffa0773c43 by task NetworkManager/411 CPU: 6 PID: 411 Comm: NetworkManager Tainted: G D 6.1.0-rc8+     #144 e15588508517267d37 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), Call Trace: <TASK> ...
    kasan_report+0xbb/0x1c0 _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae]     rtl8821ae_phy_bb_config.cold+0x346/0x641 [rtl8821ae] rtl8821ae_hw_init+0x1f5e/0x79b0 [rtl8821ae] ...
    </TASK> The root cause of the problem is that the comparison order of prate_section in
    _rtl8812ae_phy_set_txpower_limit() is wrong. The _rtl8812ae_eq_n_byte() is used to compare the first n     bytes of the two strings from tail to head, which causes the problem. In the
    _rtl8812ae_phy_set_txpower_limit(), it was originally intended to meet this requirement by carefully     designing the comparison order. For example, pregulation and pbandwidth are compared in order of     length from small to large, first is 3 and last is 4. However, the comparison order of prate_section     dose not obey such order requirement, therefore when prate_section is HT, when comparing from tail to     head, it will lead to access out of bounds in _rtl8812ae_eq_n_byte(). As mentioned above, the
    _rtl8812ae_eq_n_byte() has the same function as strcmp(), so just strcmp() is enough. Fix it by removing
    _rtl8812ae_eq_n_byte() and use strcmp() barely. Although it can be fixed by adjusting the comparison order     of prate_section, this may cause the value of rate_section to not be from 0 to 5. In addition, commit     21e4b0726dc6 not only moved driver from staging to regular tree, but also added setting txpower limit     function during the driver config phase, so the problem was introduced by this commit. (CVE-2022-50279)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix monitor mode bringup     crash When the interface is brought up in monitor mode, it leads to NULL pointer dereference crash. This     crash happens when the packet type is extracted for a SKB. This extraction which is present in the     received msdu delivery path,is not needed for the monitor ring packets since they are all RAW packets.
    Hence appending the flags with RX_FLAG_ONLY_MONITOR to skip that extraction. Observed calltrace: Unable     to handle kernel NULL pointer dereference at virtual address 0000000000000064 Mem abort info: ESR =     0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC =     0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004 CM = 0, WnR = 0 user pgtable:
    4k pages, 48-bit VAs, pgdp=0000000048517000 [0000000000000064] pgd=0000000000000000, p4d=0000000000000000     Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: ath11k_pci ath11k qmi_helpers     CPU: 2 PID: 1781 Comm: napi/-271 Not tainted 6.1.0-rc5-wt-ath-656295-gef907406320c-dirty #6 Hardware name:
    Qualcomm Technologies, Inc. IPQ8074/AP-HK10-C2 (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS     BTYPE=--) pc : ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60 [ath11k] lr :
    ath11k_hw_qcn9074_rx_desc_get_decap_type+0x5c/0x60 [ath11k] sp : ffff80000ef5bb10 x29: ffff80000ef5bb10     x28: 0000000000000000 x27: ffff000007baafa0 x26: ffff000014a91ed0 x25: 0000000000000000 x24:
    0000000000000000 x23: ffff800002b77378 x22: ffff000014a91ec0 x21: ffff000006c8d600 x20: 0000000000000000     x19: ffff800002b77740 x18: 0000000000000006 x17: 736564203634343a x16: 656e694c20657079 x15:
    0000000000000143 x14: 00000000ffffffea x13: ffff80000ef5b8b8 x12: ffff80000ef5b8c8 x11: ffff80000a591d30     x10: ffff80000a579d40 x9 : c0000000ffffefff x8 : 0000000000000003 x7 : 0000000000017fe8 x6 :
    ffff80000a579ce8 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 3a35ec12ed7f8900     x1 : 0000000000000000 x0 : 0000000000000052 Call trace: ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60     [ath11k] ath11k_dp_rx_deliver_msdu.isra.42+0xa4/0x3d0 [ath11k]     ath11k_dp_rx_mon_deliver.isra.43+0x2f8/0x458 [ath11k] ath11k_dp_rx_process_mon_rings+0x310/0x4c0 [ath11k]     ath11k_dp_service_srng+0x234/0x338 [ath11k] ath11k_pcic_ext_grp_napi_poll+0x30/0xb8 [ath11k]
    __napi_poll+0x5c/0x190 napi_threaded_poll+0xf0/0x118 kthread+0xf4/0x110 ret_from_fork+0x10/0x20 Tested-on:
    QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 (CVE-2022-50627)

  - In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: fix UAF in     hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and     reacquire them again after handle_userfault(), but reacquire the vma_lock could lead to UAF[1,2] due to     the following race, hugetlb_fault hugetlb_no_page /*unlock vma_lock */ hugetlb_handle_userfault     handle_userfault /* unlock mm->mmap_lock*/ vm_mmap_pgoff do_mmap mmap_region munmap_vma_range /* clean old     vma */ /* lock vma_lock again <--- UAF */ /* unlock vma_lock */ Since the vma_lock will unlock immediately     after hugetlb_handle_userfault(), let's drop the unneeded lock and unlock in hugetlb_handle_userfault() to     fix the issue. [1] https://lore.kernel.org/linux-mm/000000000000d5e00a05e834962e@google.com/ [2]     https://lore.kernel.org/linux-mm/20220921014457.1668-1-liuzixian4@huawei.com/ (CVE-2022-50630)

  - In the Linux kernel, the following vulnerability has been resolved: PCI: Fix pci_device_is_present() for     VFs by checking PF pci_device_is_present() previously didn't work for VFs because it reads the Vendor and     Device ID, which are 0xffff for VFs, which looks like they aren't present. Check the PF instead. Wei Gong     reported that if virtio I/O is in progress when the driver is unbound or 0 is written to     /sys/.../sriov_numvfs, the virtio I/O operation hangs, which may result in output like this: task:bash     state:D stack: 0 pid: 1773 ppid: 1241 flags:0x00004002 Call Trace: schedule+0x4f/0xc0     blk_mq_freeze_queue_wait+0x69/0xa0 blk_mq_freeze_queue+0x1b/0x20 blk_cleanup_queue+0x3d/0xd0     virtblk_remove+0x3c/0xb0 [virtio_blk] virtio_dev_remove+0x4b/0x80 ... device_unregister+0x1b/0x60     unregister_virtio_device+0x18/0x30 virtio_pci_remove+0x41/0x80 pci_device_remove+0x3e/0xb0 This happened     because pci_device_is_present(VF) returned false in virtio_pci_remove(), so it called     virtio_break_device(). The broken vq meant that vring_interrupt() skipped the vq.callback() that would     have completed the virtio I/O operation via virtblk_done(). [bhelgaas: commit log, simplify to always use     pci_physfn(), add stable tag] (CVE-2022-50636)

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.

  - iommu/amd: Improve page fault error reporting If IOMMU domain for device group is not setup properly then     we may hit IOMMU page fault. Current page fault handler assumes that domain is always setup and it will     hit NULL pointer derefence (see below sample log). Lets check whether domain is setup or not and log     appropriate message. Sample log: ---------- amdgpu 0000:00:01.0: amdgpu: SE 1, SH per SE 1, CU per SH 8,     active_cu_number 6 BUG: kernel NULL pointer dereference, address: 0000000000000058 #PF: supervisor read     access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP     NOPTI CPU: 2 PID: 56 Comm: irq/24-AMD-Vi Not tainted 6.2.0-rc2+ #89 Hardware name: xxx RIP:
    0010:report_iommu_fault+0x11/0x90 [...] Call Trace: <TASK> amd_iommu_int_thread+0x60c/0x760 ?
    __pfx_irq_thread_fn+0x10/0x10 irq_thread_fn+0x1f/0x60 irq_thread+0xea/0x1a0 ? preempt_count_add+0x6a/0xa0     ? __pfx_irq_thread_dtor+0x10/0x10 ? __pfx_irq_thread+0x10/0x10 kthread+0xe9/0x110 ?
    __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 </TASK> [joro: Edit commit message] (CVE-2023-53789)

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

ID	Name	Product	Family	Published	Updated	Severity
173340	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2023-138)	Nessus	Amazon Linux Local Security Checks	3/23/2023	2/10/2026	high
360579	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1767864313)	Nessus	Alma Linux Local Security Checks	10/1/2026	10/1/2026	high
277896	Linux Distros Unpatched Vulnerability : CVE-2023-53789	Nessus	Misc.	12/9/2025	10/17/2026	medium

Detections

Analytics

Plugins Search

high

high

medium