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: drm/i915/active: Fix misuse of non-     idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a     number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier     processing code -- a race among perf open / close replacing active barriers with perf requests on kernel     context and concurrent barrier preallocate / acquire operations performed during user context first pin /     last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker,     already allocated and registered with that composite. The tracker we obtain may already track another     fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then     we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we     don't respect return value from a function that performs the barrier deletion. Should the deletion ever     fail, we would end up reusing the tracker still registered as a barrier task. Since the same structure     field is reused with both fence callback lists and barrier tasks list, list corruptions would likely     occur. Barriers are now deleted from a barrier tasks list by temporarily removing the list content,     traversing that content with skip over the node to be deleted, then populating the list back with the     modified content. Should that intentionally racy concurrent deletion attempts be not serialized, one or     more of those may fail because of the list being temporary empty. Related code that ignores the results of     barrier deletion was initially introduced in v5.4 by commit d8af05ff38ae (drm/i915: Allow sharing the     idle-barrier from other kernel requests). However, all users of the barrier deletion routine were     apparently serialized at that time, then the issue didn't exhibit itself. Results of git bisect with help     of a newly developed igt@gem_barrier_race@remote-request IGT test indicate that list corruptions might     start to appear after commit 311770173fac (drm/i915/gt: Schedule request retirement when timeline     idles), introduced in v5.5. Respect results of barrier deletion attempts -- mark the barrier as idle only     if successfully deleted from the list. Then, before proceeding with setting our fence as the one currently     tracked, make sure that the tracker we've got is not a non-idle barrier. If that check fails then don't     use that tracker but go back and try to acquire a new, usable one. v3: use unlikely() to document what     outcome we expect (Andi), - fix bad grammar in commit description. v2: no code changes, - blame commit     311770173fac (drm/i915/gt: Schedule request retirement when timeline idles), v5.5, not commit     d8af05ff38ae (drm/i915: Allow sharing the idle-barrier from other kernel requests), v5.4, - reword     commit description. (cherry picked from commit 506006055769b10d1b2b4e22f636f3b45e0e9fc7) (CVE-2023-53087)

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

The version of kernel installed on the remote host is prior to 5.15.104-63.140. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2023-019 advisory.

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

    ext4: block range must be validated before use in ext4_mb_clear_bb() (CVE-2022-50021)

    A use-after-free vulnerability in the Linux Kernel Performance Events system can be exploited to achieve     local privilege escalation.

    The perf_group_detach function did not check the event's siblings' attach_state before calling     add_event_to_groups(), but remove_on_exec made it possible to call list_del_event() on before detaching     from their group, making it possible to use a dangling pointer causing a use-after-free vulnerability.

    We recommend upgrading past commit fd0815f632c24878e325821943edccc7fde947a2. (CVE-2023-2235)

    An issue was discovered in arch/x86/kvm/vmx/nested.c in the Linux kernel before 6.2.8. nVMX on x86_64     lacks consistency checks for CR0 and CR4. (CVE-2023-30456)

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

    ftrace: Fix invalid address access in lookup_rec() when index is 0 (CVE-2023-53075)

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

    drm/shmem-helper: Remove another errant put in error path (CVE-2023-53084)

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

    drm/i915/active: Fix misuse of non-idle barriers as fence trackers (CVE-2023-53087)

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

    ext4: fix task hung in ext4_xattr_delete_inode (CVE-2023-53089)

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

    ext4: update s_journal_inum if it changes after journal replay (CVE-2023-53091)

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

    interconnect: fix mem leak when freeing nodes (CVE-2023-53096)

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

    ext4: fix WARNING in ext4_update_inline_data (CVE-2023-53100)

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

    ext4: zero i_disksize when initializing the bootloader inode (CVE-2023-53101)

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

    bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails (CVE-2023-53103)

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

    net: tunnels: annotate lockless accesses to dev->needed_headroom (CVE-2023-53109)

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

    loop: Fix use-after-free issues (CVE-2023-53111)

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

    fs: prevent out-of-bounds array speculation when closing a file descriptor (CVE-2023-53117)

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

    tcp: tcp_make_synack() can be called from process context (CVE-2023-53121)

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

    PCI: s390: Fix use-after-free of PCI resources with per-function hotplug (CVE-2023-53123)

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

    SUNRPC: Fix a server shutdown leak (CVE-2023-53131)

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

    bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser() (CVE-2023-53133)

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

    af_unix: fix struct pid leaks in OOB support (CVE-2023-53136)

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

    ext4: Fix possible corruption when moving a directory (CVE-2023-53137)

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

    scsi: core: Remove the /proc/scsi/${proc_name} directory earlier (CVE-2023-53140)

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

    ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping() (CVE-2023-53141)

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

    ext4: fix another off-by-one fsmap error on 1k block filesystems (CVE-2023-53143)

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

    x86/resctrl: Clear staged_config[] before and after it is used (CVE-2023-53169)

    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:

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

    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)

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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-992932 advisory.

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

    drm/i915/active: Fix misuse of non-idle barriers as fence trackers

    Users reported oopses on list corruptions when using i915 perf with a     number of concurrently running graphics applications.  Root cause analysis     pointed at an issue in barrier processing code -- a race among perf open /     close replacing active barriers with perf requests on kernel context and     concurrent barrier preallocate / acquire operations performed during user     context first pin / last unpin.

    When adding a request to a composite tracker, we try to reuse an existing     fence tracker, already allocated and registered with that composite.  The     tracker we obtain may already track another fence, may be an idle barrier,     or an active barrier.

    If the tracker we get occurs a non-idle barrier then we try to delete that     barrier from a list of barrier tasks it belongs to.  However, while doing     that we don't respect return value from a function that performs the     barrier deletion.  Should the deletion ever fail, we would end up reusing     the tracker still registered as a barrier task.  Since the same structure     field is reused with both fence callback lists and barrier tasks list,     list corruptions would likely occur.

    Barriers are now deleted from a barrier tasks list by temporarily removing     the list content, traversing that content with skip over the node to be     deleted, then populating the list back with the modified content.  Should     that intentionally racy concurrent deletion attempts be not serialized,     one or more of those may fail because of the list being temporary empty.

    Related code that ignores the results of barrier deletion was initially     introduced in v5.4 by commit d8af05ff38ae (drm/i915: Allow sharing the     idle-barrier from other kernel requests).  However, all users of the     barrier deletion routine were apparently serialized at that time, then the     issue didn't exhibit itself.  Results of git bisect with help of a newly     developed igt@gem_barrier_race@remote-request IGT test indicate that list     corruptions might start to appear after commit 311770173fac (drm/i915/gt:
    Schedule request retirement when timeline idles), introduced in v5.5.

    Respect results of barrier deletion attempts -- mark the barrier as idle     only if successfully deleted from the list.  Then, before proceeding with     setting our fence as the one currently tracked, make sure that the tracker     we've got is not a non-idle barrier.  If that check fails then don't use     that tracker but go back and try to acquire a new, usable one.

    v3: use unlikely() to document what outcome we expect (Andi),
      - fix bad grammar in commit description.
    v2: no code changes,
      - blame commit 311770173fac (drm/i915/gt: Schedule request retirement         when timeline idles), v5.5, not commit d8af05ff38ae (drm/i915: Allow         sharing the idle-barrier from other kernel requests), v5.4,
      - reword commit description.

    (cherry picked from commit 506006055769b10d1b2b4e22f636f3b45e0e9fc7)

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

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

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

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

    KVM: VMX: Do _all_ initialization before exposing /dev/kvm to userspace (CVE-2022-49932)

    A use-after-free vulnerability in the Linux Kernel Performance Events system can be exploited to achieve     local privilege escalation.

    The perf_group_detach function did not check the event's siblings' attach_state before calling     add_event_to_groups(), but remove_on_exec made it possible to call list_del_event() on before detaching     from their group, making it possible to use a dangling pointer causing a use-after-free vulnerability.

    We recommend upgrading past commit fd0815f632c24878e325821943edccc7fde947a2. (CVE-2023-2235)

    do_tls_getsockopt in net/tls/tls_main.c in the Linux kernel through 6.2.6 lacks a lock_sock call, leading     to a race condition (with a resultant use-after-free or NULL pointer dereference). (CVE-2023-28466)

    An issue was discovered in arch/x86/kvm/vmx/nested.c in the Linux kernel before 6.2.8. nVMX on x86_64     lacks consistency checks for CR0 and CR4. (CVE-2023-30456)

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

    ACPI: PPTT: Fix to avoid sleep in the atomic context when PPTT is absent (CVE-2023-53070)

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

    ftrace: Fix invalid address access in lookup_rec() when index is 0 (CVE-2023-53075)

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

    ocfs2: fix data corruption after failed write (CVE-2023-53081)

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

    drm/shmem-helper: Remove another errant put in error path (CVE-2023-53084)

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

    drm/i915/active: Fix misuse of non-idle barriers as fence trackers (CVE-2023-53087)

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

    ext4: fix task hung in ext4_xattr_delete_inode (CVE-2023-53089)

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

    ext4: update s_journal_inum if it changes after journal replay (CVE-2023-53091)

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

    drm/ttm: Fix a NULL pointer dereference (CVE-2023-53095)

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

    interconnect: fix mem leak when freeing nodes (CVE-2023-53096)

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

    ext4: fix WARNING in ext4_update_inline_data (CVE-2023-53100)

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

    ext4: zero i_disksize when initializing the bootloader inode (CVE-2023-53101)

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

    bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails (CVE-2023-53103)

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

    veth: Fix use after free in XDP_REDIRECT (CVE-2023-53107)

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

    net: tunnels: annotate lockless accesses to dev->needed_headroom (CVE-2023-53109)

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

    loop: Fix use-after-free issues (CVE-2023-53111)

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

    drm/i915/sseu: fix max_subslices array-index-out-of-bounds access (CVE-2023-53112)

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

    fs: prevent out-of-bounds array speculation when closing a file descriptor (CVE-2023-53117)

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

    tcp: tcp_make_synack() can be called from process context (CVE-2023-53121)

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

    PCI: s390: Fix use-after-free of PCI resources with per-function hotplug (CVE-2023-53123)

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

    SUNRPC: Fix a server shutdown leak (CVE-2023-53131)

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

    bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser() (CVE-2023-53133)

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

    af_unix: fix struct pid leaks in OOB support (CVE-2023-53136)

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

    ext4: Fix possible corruption when moving a directory (CVE-2023-53137)

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

    scsi: core: Remove the /proc/scsi/${proc_name} directory earlier (CVE-2023-53140)

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

    ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping() (CVE-2023-53141)

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

    ext4: fix another off-by-one fsmap error on 1k block filesystems (CVE-2023-53143)

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

    x86/resctrl: Clear staged_config[] before and after it is used (CVE-2023-53169)

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 Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:6583 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: net/sched: cls_u32 component reference counter leak if tcf_change_indev() fails (CVE-2023-3609)

    * kernel: net/sched: Use-after-free vulnerabilities in the net/sched classifiers: cls_fw, cls_u32 and     cls_route (CVE-2023-4128, CVE-2023-4206, CVE-2023-4207, CVE-2023-4208)

    * kernel: eBPF: insufficient stack type checks in dynptr (CVE-2023-39191)

    * Kernel: race when faulting a device private page in memory manager (CVE-2022-3523)

    * kernel: use-after-free in l1oip timer handlers (CVE-2022-3565)

    * kernel: Rate limit overflow messages in r8152 in intr_callback (CVE-2022-3594)

    * kernel: vmwgfx: use-after-free in vmw_cmd_res_check (CVE-2022-38457)

    * kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context (CVE-2022-40133)

    * hw: Intel: Gather Data Sampling (GDS) side channel vulnerability (CVE-2022-40982)

    * kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c (CVE-2022-42895)

    * kernel: x86/mm: Randomize per-cpu entry area (CVE-2023-0597)

    * kernel: HID: check empty report_list in hid_validate_values() (CVE-2023-1073)

    * kernel: sctp: fail if no bound addresses can be used for a given scope (CVE-2023-1074)

    * kernel: hid: Use After Free in asus_remove() (CVE-2023-1079)

    * kernel: hash collisions in the IPv6 connection lookup table (CVE-2023-1206)

    * kernel: ovl: fix use after free in struct ovl_aio_req (CVE-2023-1252)

    * Kernel: use-after-free in nfsd4_ssc_setup_dul in fs/nfsd/nfs4proc.c (CVE-2023-1652)

    * kernel: Use after free bug in btsdio_remove due to race condition (CVE-2023-1989)

    * kernel: fbcon: shift-out-of-bounds in fbcon_set_font() (CVE-2023-3161)

    * kernel: out-of-bounds access in relay_file_read (CVE-2023-3268)

    * kernel: xfrm: NULL pointer dereference in xfrm_update_ae_params() (CVE-2023-3772)

    * kernel: xfrm: out-of-bounds read of XFRMA_MTIMER_THRESH nlattr (CVE-2023-3773)

    * kernel: KVM: SEV-ES / SEV-SNP VMGEXIT double fetch vulnerability (CVE-2023-4155)

    * kernel: exFAT: stack overflow in exfat_get_uniname_from_ext_entry (CVE-2023-4273)

    * kernel: mpls: double free on sysctl allocation failure (CVE-2023-26545)

    * kernel: KVM: nVMX: missing consistency checks for CR0 and CR4 (CVE-2023-30456)

    * kernel: net: qcom/emac: race condition leading to use-after-free in emac_remove() (CVE-2023-33203)

    * kernel: vmwgfx: race condition leading to information disclosure vulnerability (CVE-2023-33951)

    * kernel: vmwgfx: double free within the handling of vmw_buffer_object objects (CVE-2023-33952)

    * kernel: r592: race condition leading to use-after-free in r592_remove() (CVE-2023-35825)

    * kernel: net/tls: tls_is_tx_ready() checked list_entry (CVE-2023-1075)

    * kernel: tap: tap_open(): correctly initialize socket uid (CVE-2023-1076)

    * kernel: missing mmap_lock in file_files_note that could possibly lead to a use after free in the     coredump code (CVE-2023-1249)

    * kernel: use-after-free bug in remove function xgene_hwmon_remove (CVE-2023-1855)

    * kernel: Use after free bug in r592_remove (CVE-2023-3141)

    * kernel: gfs2: NULL pointer dereference in gfs2_evict_inode() (CVE-2023-3212)

    * kernel: NULL pointer dereference due to missing kalloc() return value check in     shtp_cl_get_dma_send_buf() (CVE-2023-3358)

    * kernel: tap: tap_open(): correctly initialize socket uid next fix of i_uid to current_fsuid     (CVE-2023-4194)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.3 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:7077 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: tun: avoid double free in tun_free_netdev (CVE-2022-4744)

    * kernel: net/sched: multiple vulnerabilities (CVE-2023-3609, CVE-2023-3611, CVE-2023-4128, CVE-2023-4206,     CVE-2023-4207, CVE-2023-4208)

    * kernel: out-of-bounds write in qfq_change_class function (CVE-2023-31436)

    * kernel: out-of-bounds write in hw_atl_utils_fw_rpc_wait (CVE-2021-43975)

    * kernel: Rate limit overflow messages in r8152 in intr_callback (CVE-2022-3594)

    * kernel: use after free flaw in l2cap_conn_del (CVE-2022-3640)

    * kernel: double free in usb_8dev_start_xmit (CVE-2022-28388)

    * kernel: vmwgfx: multiple vulnerabilities (CVE-2022-38457, CVE-2022-40133, CVE-2023-33951,     CVE-2023-33952)

    * hw: Intel: Gather Data Sampling (GDS) side channel vulnerability (CVE-2022-40982)

    * kernel: Information leak in l2cap_parse_conf_req (CVE-2022-42895)

    * kernel: KVM: multiple vulnerabilities (CVE-2022-45869, CVE-2023-4155, CVE-2023-30456)

    * kernel: memory leak in ttusb_dec_exit_dvb (CVE-2022-45887)

    * kernel: speculative pointer dereference in do_prlimit (CVE-2023-0458)

    * kernel: use-after-free due to race condition in qdisc_graft (CVE-2023-0590)

    * kernel: x86/mm: Randomize per-cpu entry area (CVE-2023-0597)

    * kernel: HID: check empty report_list in hid_validate_values (CVE-2023-1073)

    * kernel: sctp: fail if no bound addresses can be used for a given scope (CVE-2023-1074)

    * kernel: hid: Use After Free in asus_remove (CVE-2023-1079)

    * kernel: use-after-free in drivers/media/rc/ene_ir.c (CVE-2023-1118)

    * kernel: hash collisions in the IPv6 connection lookup table (CVE-2023-1206)

    * kernel: ovl: fix use after free in struct ovl_aio_req (CVE-2023-1252)

    * kernel: denial of service in tipc_conn_close (CVE-2023-1382)

    * kernel: Use after free bug in btsdio_remove due to race condition (CVE-2023-1989)

    * kernel: Spectre v2 SMT mitigations problem (CVE-2023-1998)

    * kernel: ext4: use-after-free in ext4_xattr_set_entry (CVE-2023-2513)

    * kernel: fbcon: shift-out-of-bounds in fbcon_set_font (CVE-2023-3161)

    * kernel: out-of-bounds access in relay_file_read (CVE-2023-3268)

    * kernel: xfrm: NULL pointer dereference in xfrm_update_ae_params (CVE-2023-3772)

    * kernel: smsusb: use-after-free caused by do_submit_urb (CVE-2023-4132)

    * kernel: Race between task migrating pages and another task calling exit_mmap (CVE-2023-4732)

    * Kernel: denial of service in atm_tc_enqueue due to type confusion (CVE-2023-23455)

    * kernel: mpls: double free on sysctl allocation failure (CVE-2023-26545)

    * kernel: Denial of service issue in az6027 driver (CVE-2023-28328)

    * kernel: lib/seq_buf.c has a seq_buf_putmem_hex buffer overflow (CVE-2023-28772)

    * kernel: blocking operation in dvb_frontend_get_event and wait_event_interruptible (CVE-2023-31084)

    * kernel: net: qcom/emac: race condition leading to use-after-free in emac_remove (CVE-2023-33203)

    * kernel: saa7134: race condition leading to use-after-free in saa7134_finidev (CVE-2023-35823)

    * kernel: dm1105: race condition leading to use-after-free in dm1105_remove.c (CVE-2023-35824)

    * kernel: r592: race condition leading to use-after-free in r592_remove (CVE-2023-35825)

    * kernel: net/tls: tls_is_tx_ready() checked list_entry (CVE-2023-1075)

    * kernel: use-after-free bug in remove function xgene_hwmon_remove (CVE-2023-1855)

    * kernel: Use after free bug in r592_remove (CVE-2023-3141)

    * kernel: gfs2: NULL pointer dereference in gfs2_evict_inode (CVE-2023-3212)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 8.9 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:02262-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.

    The following security bugs were fixed:

    - CVE-2022-49110: netfilter: conntrack: revisit gc autotuning (bsc#1237981).
    - CVE-2022-49139: Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt (bsc#1238032).
    - CVE-2022-49767: 9p/trans_fd: always use O_NONBLOCK read/write (bsc#1242493).
    - CVE-2022-49775: tcp: cdg: allow tcp_cdg_release() to be called multiple times (bsc#1242245).
    - CVE-2022-49858: octeontx2-pf: Fix SQE threshold checking (bsc#1242589).
    - CVE-2023-53058: net/mlx5: E-Switch, Fix an Oops in error handling code (bsc#1242237).
    - CVE-2023-53060: igb: revert rtnl_lock() that causes deadlock (bsc#1242241).
    - CVE-2023-53064: iavf: Fix hang on reboot with ice (bsc#1242222).
    - CVE-2023-53066: qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info (bsc#1242227).
    - CVE-2023-53079: net/mlx5: Fix steering rules cleanup (bsc#1242765).
    - CVE-2023-53114: i40e: Fix kernel crash during reboot when adapter is in recovery mode (bsc#1242398).
    - CVE-2023-53134: bnxt_en: Avoid order-5 memory allocation for TPA data (bsc#1242380)
    - CVE-2024-53168: net: make sock_inuse_add() available (bsc#1234887).
    - CVE-2024-56558: nfsd: make sure exp active before svc_export_show (bsc#1235100).
    - CVE-2025-21888: RDMA/mlx5: Fix a WARN during dereg_mr for DM type (bsc#1240177).
    - CVE-2025-21999: proc: fix UAF in proc_get_inode() (bsc#1240802).
    - CVE-2025-22056: netfilter: nft_tunnel: fix geneve_opt type confusion addition (bsc#1241525).
    - CVE-2025-22060: net: mvpp2: Prevent parser TCAM memory corruption (bsc#1241526).
    - CVE-2025-23138: watch_queue: fix pipe accounting mismatch (bsc#1241648).
    - CVE-2025-23145: mptcp: fix NULL pointer in can_accept_new_subflow (bsc#1242596).
    - CVE-2025-37785: ext4: fix OOB read when checking dotdot dir (bsc#1241640).
    - CVE-2025-37789: net: openvswitch: fix nested key length validation in the set() action (bsc#1242762).


Tenable has extracted the preceding description block directly from the SUSE 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 version of kernel installed on the remote host is prior to 5.10.176-157.645. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2024-059 advisory.

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

    ext4: block range must be validated before use in ext4_mb_clear_bb() (CVE-2022-50021)

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

    block, bfq: fix possible uaf for 'bfqq->bic' (CVE-2022-50488)

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

    seccomp: Move copy_seccomp() to no failure path. (CVE-2022-50661)

    An issue was discovered in arch/x86/kvm/vmx/nested.c in the Linux kernel before 6.2.8. nVMX on x86_64     lacks consistency checks for CR0 and CR4. (CVE-2023-30456)

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

    ftrace: Fix invalid address access in lookup_rec() when index is 0 (CVE-2023-53075)

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

    drm/shmem-helper: Remove another errant put in error path (CVE-2023-53084)

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

    drm/i915/active: Fix misuse of non-idle barriers as fence trackers (CVE-2023-53087)

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

    ext4: fix task hung in ext4_xattr_delete_inode (CVE-2023-53089)

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

    interconnect: fix mem leak when freeing nodes (CVE-2023-53096)

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

    ext4: fix WARNING in ext4_update_inline_data (CVE-2023-53100)

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

    ext4: zero i_disksize when initializing the bootloader inode (CVE-2023-53101)

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

    net: tunnels: annotate lockless accesses to dev->needed_headroom (CVE-2023-53109)

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

    i40e: Fix kernel crash during reboot when adapter is in recovery mode (CVE-2023-53114)

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

    nvmet: avoid potential UAF in nvmet_req_complete() (CVE-2023-53116)

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

    fs: prevent out-of-bounds array speculation when closing a file descriptor (CVE-2023-53117)

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

    tcp: tcp_make_synack() can be called from process context (CVE-2023-53121)

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

    scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add() (CVE-2023-53124)

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

    net: usb: smsc75xx: Limit packet length to skb->len (CVE-2023-53125)

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

    SUNRPC: Fix a server shutdown leak (CVE-2023-53131)

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

    bnxt_en: Avoid order-5 memory allocation for TPA data (CVE-2023-53134)

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

    ext4: Fix possible corruption when moving a directory (CVE-2023-53137)

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

    scsi: core: Remove the /proc/scsi/${proc_name} directory earlier (CVE-2023-53140)

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

    ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping() (CVE-2023-53141)

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

    ext4: fix another off-by-one fsmap error on 1k block filesystems (CVE-2023-53143)

    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:

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

    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)

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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-992266 advisory.

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

    drm/i915/active: Fix misuse of non-idle barriers as fence trackers

    Users reported oopses on list corruptions when using i915 perf with a     number of concurrently running graphics applications.  Root cause analysis     pointed at an issue in barrier processing code -- a race among perf open /     close replacing active barriers with perf requests on kernel context and     concurrent barrier preallocate / acquire operations performed during user     context first pin / last unpin.

    When adding a request to a composite tracker, we try to reuse an existing     fence tracker, already allocated and registered with that composite.  The     tracker we obtain may already track another fence, may be an idle barrier,     or an active barrier.

    If the tracker we get occurs a non-idle barrier then we try to delete that     barrier from a list of barrier tasks it belongs to.  However, while doing     that we don't respect return value from a function that performs the     barrier deletion.  Should the deletion ever fail, we would end up reusing     the tracker still registered as a barrier task.  Since the same structure     field is reused with both fence callback lists and barrier tasks list,     list corruptions would likely occur.

    Barriers are now deleted from a barrier tasks list by temporarily removing     the list content, traversing that content with skip over the node to be     deleted, then populating the list back with the modified content.  Should     that intentionally racy concurrent deletion attempts be not serialized,     one or more of those may fail because of the list being temporary empty.

    Related code that ignores the results of barrier deletion was initially     introduced in v5.4 by commit d8af05ff38ae (drm/i915: Allow sharing the     idle-barrier from other kernel requests).  However, all users of the     barrier deletion routine were apparently serialized at that time, then the     issue didn't exhibit itself.  Results of git bisect with help of a newly     developed igt@gem_barrier_race@remote-request IGT test indicate that list     corruptions might start to appear after commit 311770173fac (drm/i915/gt:
    Schedule request retirement when timeline idles), introduced in v5.5.

    Respect results of barrier deletion attempts -- mark the barrier as idle     only if successfully deleted from the list.  Then, before proceeding with     setting our fence as the one currently tracked, make sure that the tracker     we've got is not a non-idle barrier.  If that check fails then don't use     that tracker but go back and try to acquire a new, usable one.

    v3: use unlikely() to document what outcome we expect (Andi),
      - fix bad grammar in commit description.
    v2: no code changes,
      - blame commit 311770173fac (drm/i915/gt: Schedule request retirement         when timeline idles), v5.5, not commit d8af05ff38ae (drm/i915: Allow         sharing the idle-barrier from other kernel requests), v5.4,
      - reword commit description.

    (cherry picked from commit 506006055769b10d1b2b4e22f636f3b45e0e9fc7)

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

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

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:02173-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-49775: tcp: cdg: allow tcp_cdg_release() to be called multiple times (bsc#1242245).
    - CVE-2024-53168: net: make sock_inuse_add() available (bsc#1234887).
    - CVE-2024-56558: nfsd: make sure exp active before svc_export_show (bsc#1235100).
    - CVE-2025-21999: proc: fix UAF in proc_get_inode() (bsc#1240802).
    - CVE-2025-22056: netfilter: nft_tunnel: fix geneve_opt type confusion addition (bsc#1241525).
    - CVE-2025-23145: mptcp: fix NULL pointer in can_accept_new_subflow (bsc#1242596).
    - CVE-2025-37789: net: openvswitch: fix nested key length validation in the set() action (bsc#1242762).
    - CVE-2024-28956: x86/its: Add support for ITS-safe indirect thunk (bsc#1242006).
    - CVE-2025-37785: ext4: fix OOB read when checking dotdot dir (bsc#1241640).


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

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.

ID	Name	Product	Family	Published	Updated	Severity
243839	Linux Distros Unpatched Vulnerability : CVE-2023-53087	Nessus	Misc.	8/5/2025	1/14/2026	medium
176754	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2023-019 (ALASKERNEL-5.15-2023-019)	Nessus	Amazon Linux Local Security Checks	6/6/2023	2/9/2026	high
281303	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-992932)	Nessus	Unity Linux Local Security Checks	12/31/2025	12/31/2025	medium
173854	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2023-148)	Nessus	Amazon Linux Local Security Checks	4/4/2023	2/24/2026	high
194262	RHEL 9 : kernel (RHSA-2023:6583)	Nessus	Red Hat Local Security Checks	4/28/2024	10/28/2025	high
185679	RHEL 8 : kernel (RHSA-2023:7077)	Nessus	Red Hat Local Security Checks	11/14/2023	9/10/2025	high
241966	SUSE SLES15 : Recommended update for initial livepatch (SUSE-SU-2025:02262-1)	Nessus	SuSE Local Security Checks	7/11/2025	12/9/2025	high
200362	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2024-059 (ALASKERNEL-5.10-2024-059)	Nessus	Amazon Linux Local Security Checks	6/11/2024	2/9/2026	high
280206	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992266)	Nessus	Unity Linux Local Security Checks	12/30/2025	12/30/2025	medium
241036	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:02173-1)	Nessus	SuSE Local Security Checks	7/1/2025	12/9/2025	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	3/23/2026	high

Detections

Analytics

Plugins Search

medium

high

medium

high

high

high

high

high

medium

medium

high