In the Linux kernel, the following vulnerability has been resolved: scsi: ses: Handle enclosure with just a primary component gracefully This reverts commit 3fe97ff3d949 ("scsi: ses: Don't attach if enclosure has no components") and introduces proper handling of case where there are no detected secondary components, but primary component (enumerated in num_enclosures) does exist. That fix was originally proposed by Ding Hui <dinghui@sangfor.com.cn>. Completely ignoring devices that have one primary enclosure and no secondary one results in ses_intf_add() bailing completely scsi 2:0:0:254: enclosure has no enumerated components scsi 2:0:0:254: Failed to bind enclosure -12ven in valid configurations such even on valid configurations with 1 primary and 0 secondary enclosures as below: # sg_ses /dev/sg0 3PARdata SES 3321 Supported diagnostic pages: Supported Diagnostic Pages [sdp] [0x0] Configuration (SES) [cf] [0x1] Short Enclosure Status (SES) [ses] [0x8] # sg_ses -p cf /dev/sg0 3PARdata SES 3321 Configuration diagnostic page: number of secondary subenclosures: 0 generation code: 0x0 enclosure descriptor list Subenclosure identifier: 0 [primary] relative ES process id: 0, number of ES processes: 1 number of type descriptor headers: 1 enclosure logical identifier (hex): 20000002ac02068d enclosure vendor: 3PARdata product: VV rev: 3321 type descriptor header and text list Element type: Unspecified, subenclosure id: 0 number of possible elements: 1 The changelog for the original fix follows ===== We can get a crash when disconnecting the iSCSI session, the call trace like this: [ffff00002a00fb70] kfree at ffff00000830e224 [ffff00002a00fba0] ses_intf_remove at ffff000001f200e4 [ffff00002a00fbd0] device_del at ffff0000086b6a98 [ffff00002a00fc50] device_unregister at ffff0000086b6d58 [ffff00002a00fc70] __scsi_remove_device at ffff00000870608c [ffff00002a00fca0] scsi_remove_device at ffff000008706134 [ffff00002a00fcc0] __scsi_remove_target at ffff0000087062e4 [ffff00002a00fd10] scsi_remove_target at ffff0000087064c0 [ffff00002a00fd70] __iscsi_unbind_session at ffff000001c872c4 [ffff00002a00fdb0] process_one_work at ffff00000810f35c [ffff00002a00fe00] worker_thread at ffff00000810f648 [ffff00002a00fe70] kthread at ffff000008116e98 In ses_intf_add, components count could be 0, and kcalloc 0 size scomp, but not saved in edev->component[i].scratch In this situation, edev->component[0].scratch is an invalid pointer, when kfree it in ses_intf_remove_enclosure, a crash like above would happen The call trace also could be other random cases when kfree cannot catch the invalid pointer We should not use edev->component[] array when the components count is 0 We also need check index when use edev->component[] array in ses_enclosure_data_process =====

According to the versions of the kernel packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

    media: v4l2-mem2mem: add lock to protect parameter num_rdy(CVE-2023-53519)

    md: Replace snprintf with scnprintf(CVE-2022-50299)

    mm/vmscan: don't try to reclaim hwpoison folio(CVE-2025-37834)

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume()(CVE-2023-53271)

    md/raid10: fix wrong setting of max_corr_read_errors(CVE-2023-53313)

    scsi: target: target_core_configfs: Add length check to avoid buffer overflow(CVE-2025-39998)

    loop: Avoid updating block size under exclusive owner(CVE-2025-38709)

    mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory(CVE-2025-39883)

    scsi: qla4xxx: Prevent a potential error pointer dereference(CVE-2025-39676)

    NFS: Fix a race when updating an existing write(CVE-2025-39697)

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses(CVE-2023-7324)

    efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare(CVE-2025-39817)

    dm raid: fix address sanitizer warning in raid_resume(CVE-2022-50085)

    usb-storage: alauda: Fix uninit-value in alauda_check_media()(CVE-2023-53847)

    mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list(CVE-2025-39725)

    md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request(CVE-2023-53380)

    md/raid10: check slab-out-of-bounds in md_bitmap_get_counter(CVE-2023-53357)

    net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode(CVE-2023-53733)

    fs: quota: create dedicated workqueue for quota_release_work(CVE-2025-40196)

    partitions: mac: fix handling of bogus partition table(CVE-2025-21772)

    HID: hidraw: fix memory leak in hidraw_release()(CVE-2022-49981)

    pid: Add a judgment for ns null in pid_nr_ns(CVE-2025-40178)

    libceph: fix potential use-after-free in have_mon_and_osd_map()(CVE-2025-68285)

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

    drivers/md/md-bitmap: check the return value of md_bitmap_get_counter()(CVE-2022-50402)

    PNP: fix name memory leak in pnp_alloc_dev()(CVE-2022-50278)

    ipvs: Defer ip_vs_ftp unregister during netns cleanup(CVE-2025-40018)

    nbd: Fix hung when signal interrupts nbd_start_device_ioctl()(CVE-2022-50314)

    igb: Do not free q_vector unless new one was allocated(CVE-2022-50252)

    ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed(CVE-2023-53481)

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

    scsi: mpt3sas: Fix crash in transport port remove by using ioc_info()(CVE-2025-40115)

    scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()(CVE-2023-53676)

    NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid(CVE-2025-68349)

    net: hns: fix possible memory leak in hnae_ae_register()(CVE-2022-50352)

    md: call __md_stop_writes in md_stop(CVE-2022-49987)

    net/packet: fix a race in packet_set_ring() and packet_notifier()(CVE-2025-38617)

    regulator: of: Fix refcount leak bug in of_get_regulation_constraints()(CVE-2022-50191)

    ubi: Fix use-after-free when volume resizing failed(CVE-2023-53800)

    HID: multitouch: Correct devm device reference for hidinput input_dev name(CVE-2023-53454)

    ipv6: reject malicious packets in ipv6_gso_segment()(CVE-2025-38572)

    md/raid10: fix leak of 'r10bio-remaining' for recovery(CVE-2023-53299)

    scsi: qla2xxx: Wait for io return on terminate rport(CVE-2023-53322)

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

    igb: Fix igb_down hung on surprise removal(CVE-2023-53148)

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

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()(CVE-2023-53803)

    ubi: ensure that VID header offset + VID header size = alloc, size(CVE-2023-53265)

    fs/proc: fix uaf in proc_readdir_de()(CVE-2025-40271)

    firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails(CVE-2022-50087)

    md-raid10: fix KASAN warning(CVE-2022-50211)

    scsi: ses: Fix possible desc_ptr out-of-bounds accesses(CVE-2023-53675)

    mmc: core: Fix kernel panic when remove non-standard SDIO card(CVE-2022-50640)

    nfs: handle failure of nfs_get_lock_context in unlock path(CVE-2025-38023)

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

    RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug(CVE-2025-38024)

    sctp: check send stream number after wait_for_sndbuf(CVE-2023-53296)

    net/sched: sch_qfq: Fix race condition on qfq_aggregate(CVE-2025-38477)

    RDMA/rxe: Fix 'kernel NULL pointer dereference' error(CVE-2022-50671)

    i40e: add validation for ring_len param(CVE-2025-39973)

    md/raid1: Fix stack memory use after return in raid1_reshape(CVE-2025-38445)

    Squashfs: check return result of sb_min_blocksize(CVE-2025-38415)

    net/tunnel: wait until all sk_user_data reader finish before releasing the sock(CVE-2022-50405)

    ip6_vti: fix slab-use-after-free in decode_session6(CVE-2023-53821)

    af_unix: Fix data-races around user-unix_inflight.(CVE-2023-53204)

    RDMA/rxe: Fix error unwind in rxe_create_qp()(CVE-2022-50127)

    __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock(CVE-2025-38058)

    NFSD: Protect against send buffer overflow in NFSv2 READ(CVE-2022-50410)

    scsi: hpsa: Fix possible memory leak in hpsa_init_one()(CVE-2022-50646)

    sctp: handle the error returned from sctp_auth_asoc_init_active_key(CVE-2022-50243)

    vsock: Do not allow binding to VMADDR_PORT_ANY(CVE-2025-38618)

    smb: client: Fix use-after-free in cifs_fill_dirent(CVE-2025-38051)

    scsi: libiscsi: Initialize iscsi_conn-dd_data only if memory is allocated(CVE-2025-38700)

    sctp: fix a potential overflow in sctp_ifwdtsn_skip(CVE-2023-53372)

    pstore/ram: Check start of empty przs during init(CVE-2023-53331)

    clk: samsung: Fix memory leak in _samsung_clk_register_pll()(CVE-2022-50449)

    md/raid10: prevent soft lockup while flush writes(CVE-2023-53151)

    nfsd: call op_release, even when op_func returns an error(CVE-2023-53241)

    cifs: Release folio lock on fscache read hit.(CVE-2023-53593)

    net: bridge: fix soft lockup in br_multicast_query_expired()(CVE-2025-39773)

    cifs: fix small mempool leak in SMB2_negotiate()(CVE-2022-49938)

    dm raid: fix address sanitizer warning in raid_status(CVE-2022-50084)

    nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()(CVE-2025-38724)

    scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport()(CVE-2023-54014)

    block: fix resource leak in blk_register_queue() error path(CVE-2025-37980)

    drm/client: Fix memory leak in drm_client_target_cloned(CVE-2023-54091)

    dm flakey: fix a crash with invalid table line(CVE-2023-53786)

    crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui()(CVE-2023-53817)

    hwrng: virtio - Fix race on data_avail and actual data(CVE-2023-53998)

    sched/fair: Don't balance task to its current running CPU(CVE-2023-53215)

    ppp: associate skb with a device at tx(CVE-2022-50655)

    fbdev: bitblit: bound-check glyph index in bit_putcs*(CVE-2025-40322)

    acct: fix potential integer overflow in encode_comp_t()(CVE-2022-50749)

    udf: Avoid double brelse() in udf_rename()(CVE-2022-50755)

    tee: add overflow check in register_shm_helper()(CVE-2022-50080)

    drm: Prevent drm_copy_field() to attempt copying a NULL pointer(CVE-2022-50884)

    crypto: api - Use work queue in crypto_destroy_instance(CVE-2023-53799)

    mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()(CVE-2023-53623)

Tenable has extracted the preceding description block directly from the EulerOS Virtualization kernel security advisory.

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

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    scsi: mpt3sas: Fix crash in transport port remove by using ioc_info()(CVE-2025-40115)

    scsi: target: Fix WRITE_SAME No Data Buffer crash(CVE-2022-21546)

    NFSD: Fix crash in nfsd4_read_release()(CVE-2025-40324)

    scsi: qla4xxx: Prevent a potential error pointer dereference(CVE-2025-39676)

    loop: Avoid updating block size under exclusive owner(CVE-2025-38709)

     media: v4l2-mem2mem: add lock to protect parameter num_rdy(CVE-2023-53519)

    mmc: rtsx_usb_sdmmc: fix return value check of mmc_add_host()(CVE-2022-50347)

    net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb(CVE-2023-53548)

    platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]()(CVE-2022-50521)

    tipc: fix an information leak in tipc_topsrv_kern_subscr(CVE-2022-50531)

    scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport()(CVE-2023-54014)

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume()(CVE-2023-53271)

    dma-buf: insert memory barrier before updating num_fences(CVE-2025-38095)

    md/raid10: fix wrong setting of max_corr_read_errors(CVE-2023-53313)

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses(CVE-2023-7324)

    scsi: storvsc: Fix handling of virtual Fibre Channel timeouts(CVE-2023-53245)

    md/raid10: prevent soft lockup while flush writes(CVE-2023-53151)

    clk: samsung: Fix memory leak in _samsung_clk_register_pll()(CVE-2022-50449)

    sctp: fix a potential overflow in sctp_ifwdtsn_skip(CVE-2023-53372)

    crypto: api - Use work queue in crypto_destroy_instance(CVE-2023-53799)

    drm: Prevent drm_copy_field() to attempt copying a NULL pointer(CVE-2022-50884)

    dm raid: fix address sanitizer warning in raid_status(CVE-2022-50084)

    cifs: fix small mempool leak in SMB2_negotiate()(CVE-2022-49938)

    net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device(CVE-2023-54015)

    ipv6: reject malicious packets in ipv6_gso_segment()(CVE-2025-38572)

    fs/proc: fix uaf in proc_readdir_de()(CVE-2025-40271)

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()(CVE-2023-53803)

    macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse(CVE-2025-68367)

    ubi: Fix use-after-free when volume resizing failed(CVE-2023-53800)

    crypto: qat - fix DMA transfer direction(CVE-2022-50774)

    scsi: hpsa: Fix possible memory leak in hpsa_init_one()(CVE-2022-50646)

    mmc: core: Fix kernel panic when remove non-standard SDIO card(CVE-2022-50640)

    usb: host: ohci-ppc-of: Fix refcount leak bug(CVE-2022-50033)

    PNP: fix name memory leak in pnp_alloc_dev()(CVE-2022-50278)

    media: dvb-frontends: fix leak of memory fw(CVE-2022-50664)

    fs: quota: create dedicated workqueue for quota_release_work(CVE-2025-40196)

    acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl(CVE-2024-56662)

    scsi: ses: Handle enclosure with just a primary component gracefully(CVE-2023-53431)

    pid: Add a judgment for ns null in pid_nr_ns(CVE-2025-40178)

    NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid(CVE-2025-68349)

    hwrng: virtio - Fix race on data_avail and actual data(CVE-2023-53998)

    usb-storage: alauda: Fix uninit-value in alauda_check_media()(CVE-2023-53847)

    netlink: do not hard code device address lenth in fdb dumps(CVE-2023-53863)

    drm/client: Fix memory leak in drm_client_target_cloned(CVE-2023-54091)

    ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe(CVE-2025-68241)

    md/raid10: fix null-ptr-deref in raid10_sync_request(CVE-2023-53832)

    iommu/amd: Fix pci device refcount leak in ppr_notifier()(CVE-2022-50505)

    net: read sk-sk_family once in sk_mc_loop()(CVE-2023-53831)

    fbdev: bitblit: bound-check glyph index in bit_putcs*(CVE-2025-40322)

    bpf: make sure skb-len != 0 when redirecting to a tunneling device(CVE-2022-50253)

    ppp: associate skb with a device at tx(CVE-2022-50655)

    ip6_vti: fix slab-use-after-free in decode_session6(CVE-2023-53821)

    hwrng: amd - Fix PCI device refcount leak(CVE-2022-50868)

    netlink: annotate accesses to nlk-cb_running(CVE-2023-53853)

    acct: fix potential integer overflow in encode_comp_t()(CVE-2022-50749)

    RDMA/rxe: Fix 'kernel NULL pointer dereference' error(CVE-2022-50671)

    udf: Avoid double brelse() in udf_rename()(CVE-2022-50755)

    dm flakey: fix a crash with invalid table line(CVE-2023-53786)

    libceph: fix potential use-after-free in have_mon_and_osd_map()(CVE-2025-68285)

    crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui()(CVE-2023-53817)

Tenable has extracted the preceding description block directly from the EulerOS kernel 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-2026-005743 advisory.

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

    scsi: ses: Handle enclosure with just a primary component gracefully

    This reverts commit 3fe97ff3d949 (scsi: ses: Don't attach if enclosure     has no components) and introduces proper handling of case where there are     no detected secondary components, but primary component (enumerated in     num_enclosures) does exist. That fix was originally proposed by Ding Hui     <dinghui@sangfor.com.cn>.

    Completely ignoring devices that have one primary enclosure and no     secondary one results in ses_intf_add() bailing completely

            scsi 2:0:0:254: enclosure has no enumerated components             scsi 2:0:0:254: Failed to bind enclosure -12ven in valid configurations such

    even on valid configurations with 1 primary and 0 secondary enclosures as     below:

            # sg_ses /dev/sg0               3PARdata  SES               3321             Supported diagnostic pages:
              Supported Diagnostic Pages [sdp] [0x0]               Configuration (SES) [cf] [0x1]               Short Enclosure Status (SES) [ses] [0x8]             # sg_ses -p cf /dev/sg0               3PARdata  SES               3321             Configuration diagnostic page:
              number of secondary subenclosures: 0               generation code: 0x0               enclosure descriptor list                 Subenclosure identifier: 0 [primary]                   relative ES process id: 0, number of ES processes: 1                   number of type descriptor headers: 1                   enclosure logical identifier (hex): 20000002ac02068d                   enclosure vendor: 3PARdata  product: VV                rev: 3321               type descriptor header and text list                 Element type: Unspecified, subenclosure id: 0                   number of possible elements: 1

    The changelog for the original fix follows

    =====     We can get a crash when disconnecting the iSCSI session,     the call trace like this:

      [ffff00002a00fb70] kfree at ffff00000830e224       [ffff00002a00fba0] ses_intf_remove at ffff000001f200e4       [ffff00002a00fbd0] device_del at ffff0000086b6a98       [ffff00002a00fc50] device_unregister at ffff0000086b6d58       [ffff00002a00fc70] __scsi_remove_device at ffff00000870608c       [ffff00002a00fca0] scsi_remove_device at ffff000008706134       [ffff00002a00fcc0] __scsi_remove_target at ffff0000087062e4       [ffff00002a00fd10] scsi_remove_target at ffff0000087064c0       [ffff00002a00fd70] __iscsi_unbind_session at ffff000001c872c4       [ffff00002a00fdb0] process_one_work at ffff00000810f35c       [ffff00002a00fe00] worker_thread at ffff00000810f648       [ffff00002a00fe70] kthread at ffff000008116e98

    In ses_intf_add, components count could be 0, and kcalloc 0 size scomp,     but not saved in edev->component[i].scratch

    In this situation, edev->component[0].scratch is an invalid pointer,     when kfree it in ses_intf_remove_enclosure, a crash like above would happen     The call trace also could be other random cases when kfree cannot catch     the invalid pointer

    We should not use edev->component[] array when the components count is 0     We also need check index when use edev->component[] array in     ses_enclosure_data_process     =====

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

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

    scsi: ses: Handle enclosure with just a primary component gracefully

    This reverts commit 3fe97ff3d949 (scsi: ses: Don't attach if enclosure     has no components) and introduces proper handling of case where there are     no detected secondary components, but primary component (enumerated in     num_enclosures) does exist. That fix was originally proposed by Ding Hui     <dinghui@sangfor.com.cn>.

    Completely ignoring devices that have one primary enclosure and no     secondary one results in ses_intf_add() bailing completely

            scsi 2:0:0:254: enclosure has no enumerated components             scsi 2:0:0:254: Failed to bind enclosure -12ven in valid configurations such

    even on valid configurations with 1 primary and 0 secondary enclosures as     below:

            # sg_ses /dev/sg0               3PARdata  SES               3321             Supported diagnostic pages:
              Supported Diagnostic Pages [sdp] [0x0]               Configuration (SES) [cf] [0x1]               Short Enclosure Status (SES) [ses] [0x8]             # sg_ses -p cf /dev/sg0               3PARdata  SES               3321             Configuration diagnostic page:
              number of secondary subenclosures: 0               generation code: 0x0               enclosure descriptor list                 Subenclosure identifier: 0 [primary]                   relative ES process id: 0, number of ES processes: 1                   number of type descriptor headers: 1                   enclosure logical identifier (hex): 20000002ac02068d                   enclosure vendor: 3PARdata  product: VV                rev: 3321               type descriptor header and text list                 Element type: Unspecified, subenclosure id: 0                   number of possible elements: 1

    The changelog for the original fix follows

    =====     We can get a crash when disconnecting the iSCSI session,     the call trace like this:

      [ffff00002a00fb70] kfree at ffff00000830e224       [ffff00002a00fba0] ses_intf_remove at ffff000001f200e4       [ffff00002a00fbd0] device_del at ffff0000086b6a98       [ffff00002a00fc50] device_unregister at ffff0000086b6d58       [ffff00002a00fc70] __scsi_remove_device at ffff00000870608c       [ffff00002a00fca0] scsi_remove_device at ffff000008706134       [ffff00002a00fcc0] __scsi_remove_target at ffff0000087062e4       [ffff00002a00fd10] scsi_remove_target at ffff0000087064c0       [ffff00002a00fd70] __iscsi_unbind_session at ffff000001c872c4       [ffff00002a00fdb0] process_one_work at ffff00000810f35c       [ffff00002a00fe00] worker_thread at ffff00000810f648       [ffff00002a00fe70] kthread at ffff000008116e98

    In ses_intf_add, components count could be 0, and kcalloc 0 size scomp,     but not saved in edev->component[i].scratch

    In this situation, edev->component[0].scratch is an invalid pointer,     when kfree it in ses_intf_remove_enclosure, a crash like above would happen     The call trace also could be other random cases when kfree cannot catch     the invalid pointer

    We should not use edev->component[] array when the components count is 0     We also need check index when use edev->component[] array in     ses_enclosure_data_process     =====

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

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

    scsi: ses: Handle enclosure with just a primary component gracefully

    This reverts commit 3fe97ff3d949 (scsi: ses: Don't attach if enclosure     has no components) and introduces proper handling of case where there are     no detected secondary components, but primary component (enumerated in     num_enclosures) does exist. That fix was originally proposed by Ding Hui     <dinghui@sangfor.com.cn>.

    Completely ignoring devices that have one primary enclosure and no     secondary one results in ses_intf_add() bailing completely

            scsi 2:0:0:254: enclosure has no enumerated components             scsi 2:0:0:254: Failed to bind enclosure -12ven in valid configurations such

    even on valid configurations with 1 primary and 0 secondary enclosures as     below:

            # sg_ses /dev/sg0               3PARdata  SES               3321             Supported diagnostic pages:
              Supported Diagnostic Pages [sdp] [0x0]               Configuration (SES) [cf] [0x1]               Short Enclosure Status (SES) [ses] [0x8]             # sg_ses -p cf /dev/sg0               3PARdata  SES               3321             Configuration diagnostic page:
              number of secondary subenclosures: 0               generation code: 0x0               enclosure descriptor list                 Subenclosure identifier: 0 [primary]                   relative ES process id: 0, number of ES processes: 1                   number of type descriptor headers: 1                   enclosure logical identifier (hex): 20000002ac02068d                   enclosure vendor: 3PARdata  product: VV                rev: 3321               type descriptor header and text list                 Element type: Unspecified, subenclosure id: 0                   number of possible elements: 1

    The changelog for the original fix follows

    =====     We can get a crash when disconnecting the iSCSI session,     the call trace like this:

      [ffff00002a00fb70] kfree at ffff00000830e224       [ffff00002a00fba0] ses_intf_remove at ffff000001f200e4       [ffff00002a00fbd0] device_del at ffff0000086b6a98       [ffff00002a00fc50] device_unregister at ffff0000086b6d58       [ffff00002a00fc70] __scsi_remove_device at ffff00000870608c       [ffff00002a00fca0] scsi_remove_device at ffff000008706134       [ffff00002a00fcc0] __scsi_remove_target at ffff0000087062e4       [ffff00002a00fd10] scsi_remove_target at ffff0000087064c0       [ffff00002a00fd70] __iscsi_unbind_session at ffff000001c872c4       [ffff00002a00fdb0] process_one_work at ffff00000810f35c       [ffff00002a00fe00] worker_thread at ffff00000810f648       [ffff00002a00fe70] kthread at ffff000008116e98

    In ses_intf_add, components count could be 0, and kcalloc 0 size scomp,     but not saved in edev->component[i].scratch

    In this situation, edev->component[0].scratch is an invalid pointer,     when kfree it in ses_intf_remove_enclosure, a crash like above would happen     The call trace also could be other random cases when kfree cannot catch     the invalid pointer

    We should not use edev->component[] array when the components count is 0     We also need check index when use edev->component[] array in     ses_enclosure_data_process     =====

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

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

    scsi: ses: Handle enclosure with just a primary component gracefully

    This reverts commit 3fe97ff3d949 (scsi: ses: Don't attach if enclosure     has no components) and introduces proper handling of case where there are     no detected secondary components, but primary component (enumerated in     num_enclosures) does exist. That fix was originally proposed by Ding Hui     <dinghui@sangfor.com.cn>.

    Completely ignoring devices that have one primary enclosure and no     secondary one results in ses_intf_add() bailing completely

            scsi 2:0:0:254: enclosure has no enumerated components             scsi 2:0:0:254: Failed to bind enclosure -12ven in valid configurations such

    even on valid configurations with 1 primary and 0 secondary enclosures as     below:

            # sg_ses /dev/sg0               3PARdata  SES               3321             Supported diagnostic pages:
              Supported Diagnostic Pages [sdp] [0x0]               Configuration (SES) [cf] [0x1]               Short Enclosure Status (SES) [ses] [0x8]             # sg_ses -p cf /dev/sg0               3PARdata  SES               3321             Configuration diagnostic page:
              number of secondary subenclosures: 0               generation code: 0x0               enclosure descriptor list                 Subenclosure identifier: 0 [primary]                   relative ES process id: 0, number of ES processes: 1                   number of type descriptor headers: 1                   enclosure logical identifier (hex): 20000002ac02068d                   enclosure vendor: 3PARdata  product: VV                rev: 3321               type descriptor header and text list                 Element type: Unspecified, subenclosure id: 0                   number of possible elements: 1

    The changelog for the original fix follows

    =====     We can get a crash when disconnecting the iSCSI session,     the call trace like this:

      [ffff00002a00fb70] kfree at ffff00000830e224       [ffff00002a00fba0] ses_intf_remove at ffff000001f200e4       [ffff00002a00fbd0] device_del at ffff0000086b6a98       [ffff00002a00fc50] device_unregister at ffff0000086b6d58       [ffff00002a00fc70] __scsi_remove_device at ffff00000870608c       [ffff00002a00fca0] scsi_remove_device at ffff000008706134       [ffff00002a00fcc0] __scsi_remove_target at ffff0000087062e4       [ffff00002a00fd10] scsi_remove_target at ffff0000087064c0       [ffff00002a00fd70] __iscsi_unbind_session at ffff000001c872c4       [ffff00002a00fdb0] process_one_work at ffff00000810f35c       [ffff00002a00fe00] worker_thread at ffff00000810f648       [ffff00002a00fe70] kthread at ffff000008116e98

    In ses_intf_add, components count could be 0, and kcalloc 0 size scomp,     but not saved in edev->component[i].scratch

    In this situation, edev->component[0].scratch is an invalid pointer,     when kfree it in ses_intf_remove_enclosure, a crash like above would happen     The call trace also could be other random cases when kfree cannot catch     the invalid pointer

    We should not use edev->component[] array when the components count is 0     We also need check index when use edev->component[] array in     ses_enclosure_data_process     =====

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 SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4515-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2022-50364: i2c: mux: reg: check return value after calling platform_get_resource() (bsc#1250083).
    - CVE-2022-50368: drm/msm/dsi: fix memory corruption with too many bridges (bsc#1250009).
    - CVE-2022-50494: thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash     (bsc#1251173).
    - CVE-2022-50545: r6040: Fix kmemleak in probe and remove (bsc#1251285).
    - CVE-2022-50551: wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request()     (bsc#1251322).
    - CVE-2022-50569: xfrm: Update ipcomp_scratches with NULL when freed (bsc#1252640).
    - CVE-2022-50578: class: fix possible memory leak in __class_register() (bsc#1252519).
    - CVE-2023-53229: wifi: mac80211: fix invalid drv_sta_pre_rcu_remove calls for non-uploaded sta     (bsc#1249650).
    - CVE-2023-53369: net: dcb: choose correct policy to parse DCB_ATTR_BCN (bsc#1250206).
    - CVE-2023-53431: scsi: ses: Don't attach if enclosure has no components (bsc#1250374).
    - CVE-2023-53542: ARM: dts: exynos: Use Exynos5420 compatible for the MIPI video phy (bsc#1251154).
    - CVE-2023-53597: cifs: fix mid leak during reconnection after timeout threshold (bsc#1251159).
    - CVE-2023-53641: wifi: ath9k: hif_usb: fix memory leak of remain_skbs (bsc#1251728).
    - CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).
    - CVE-2025-38436: drm/scheduler: signal scheduled fence when kill job (bsc#1247227).
    - CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).
    - CVE-2025-39967: fbcon: fix integer overflow in fbcon_do_set_font (bsc#1252033).
    - CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).
    - CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).
    - CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).
    - CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).
    - CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).
    - CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).
    - CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).
    - CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).
    - CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).
    - CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).
    - CVE-2025-40205: btrfs: avoid potential out-of-bounds in btrfs_encode_fh() (bsc#1253456).


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 remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:03628-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2022-49138: Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt (bsc#1238160).
    - CVE-2022-49980: USB: gadget: fix use-after-free read in usb_udc_uevent() (bsc#1245110).
    - CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev->{dev_name,short_name} (bsc#1246968).
    - CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).
    - CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).
    - CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).
    - CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).
    - CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).
    - CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint (bsc#1242573).
    - CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).
    - CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).
    - CVE-2025-37958: mm/huge_memory: fix dereferencing invalid pmd migration entry (bsc#1243539).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38084: mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245498).
    - CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245499).
    - CVE-2025-38111: net/mdiobus: Fix potential out-of-bounds read/write access (bsc#1245666).
    - CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).
    - CVE-2025-38380: i2c/designware: Fix an initialization issue (bsc#1247028).
    - CVE-2025-38470: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime     (bsc#1247288).
    - CVE-2025-38476: rpl: Fix use-after-free in rpl_do_srh_inline() (bsc#1247317).
    - CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).
    - CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree     (bsc#1248255).
    - CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).
    - CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).
    - CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).
    - CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).
    - CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).
    - CVE-2025-38706: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (bsc#1249195).
    - CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).
    - CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).
    - CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).
    - CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).
    - CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).
    - CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).
    - CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).
    - CVE-2025-39790: bus: mhi: host: Detect events pointing to unexpected TREs (bsc#1249548).
    - CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).
    - CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).
    - CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).
    - CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).
    - CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).


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 remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:03615-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2022-49138: Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt (bsc#1238160).
    - CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev->{dev_name,short_name} (bsc#1246968).
    - CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).
    - CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).
    - CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).
    - CVE-2023-53257: wifi: mac80211: check S1G action frame size (bsc#1249869).
    - CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).
    - CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).
    - CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).
    - CVE-2025-37958: mm/huge_memory: fix dereferencing invalid pmd migration entry (bsc#1243539).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38111: net/mdiobus: Fix potential out-of-bounds read/write access (bsc#1245666).
    - CVE-2025-38380: i2c/designware: Fix an initialization issue (bsc#1247028).
    - CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).
    - CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree     (bsc#1248255).
    - CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).
    - CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).
    - CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).
    - CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).
    - CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).
    - CVE-2025-38706: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (bsc#1249195).
    - CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).
    - CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).
    - CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).
    - CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).
    - CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).
    - CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).
    - CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).
    - CVE-2025-39790: bus: mhi: host: Detect events pointing to unexpected TREs (bsc#1249548).
    - CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).
    - CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).
    - CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).
    - CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).


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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - scsi: ses: Handle enclosure with just a primary component gracefully This reverts commit 3fe97ff3d949     (scsi: ses: Don't attach if enclosure has no components) and introduces proper handling of case where     there are no detected secondary components, but primary component (enumerated in num_enclosures) does     exist. That fix was originally proposed by Ding Hui <dinghui@sangfor.com.cn>. Completely ignoring devices     that have one primary enclosure and no secondary one results in ses_intf_add() bailing completely scsi     2:0:0:254: enclosure has no enumerated components scsi 2:0:0:254: Failed to bind enclosure -12ven in valid     configurations such even on valid configurations with 1 primary and 0 secondary enclosures as below: #     sg_ses /dev/sg0 3PARdata SES 3321 Supported diagnostic pages: Supported Diagnostic Pages [sdp] [0x0]     Configuration (SES) [cf] [0x1] Short Enclosure Status (SES) [ses] [0x8] # sg_ses -p cf /dev/sg0 3PARdata     SES 3321 Configuration diagnostic page: number of secondary subenclosures: 0 generation code: 0x0     enclosure descriptor list Subenclosure identifier: 0 [primary] relative ES process id: 0, number of ES     processes: 1 number of type descriptor headers: 1 enclosure logical identifier (hex): 20000002ac02068d     enclosure vendor: 3PARdata product: VV rev: 3321 type descriptor header and text list Element type:
    Unspecified, subenclosure id: 0 number of possible elements: 1 The changelog for the original fix follows     ===== We can get a crash when disconnecting the iSCSI session, the call trace like this:
    [ffff00002a00fb70] kfree at ffff00000830e224 [ffff00002a00fba0] ses_intf_remove at ffff000001f200e4     [ffff00002a00fbd0] device_del at ffff0000086b6a98 [ffff00002a00fc50] device_unregister at ffff0000086b6d58     [ffff00002a00fc70] __scsi_remove_device at ffff00000870608c [ffff00002a00fca0] scsi_remove_device at     ffff000008706134 [ffff00002a00fcc0] __scsi_remove_target at ffff0000087062e4 [ffff00002a00fd10]     scsi_remove_target at ffff0000087064c0 [ffff00002a00fd70] __iscsi_unbind_session at ffff000001c872c4     [ffff00002a00fdb0] process_one_work at ffff00000810f35c [ffff00002a00fe00] worker_thread at     ffff00000810f648 [ffff00002a00fe70] kthread at ffff000008116e98 In ses_intf_add, components count could be     0, and kcalloc 0 size scomp, but not saved in edev->component[i].scratch In this situation,     edev->component[0].scratch is an invalid pointer, when kfree it in ses_intf_remove_enclosure, a crash like     above would happen The call trace also could be other random cases when kfree cannot catch the invalid     pointer We should not use edev->component[] array when the components count is 0 We also need check index     when use edev->component[] array in ses_enclosure_data_process ===== (CVE-2023-53431)

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 4.14.309-231.529. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2023-1987 advisory.

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

    net: sched: fix memory leak in tcindex_set_parms (CVE-2022-50396)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0458)

    Use After Free vulnerability in Linux kernel traffic control index filter (tcindex) allows Privilege     Escalation. The imperfect hash area can be updated while packets are traversing, which will cause a use-     after-free when 'tcf_exts_exec()' is called with the destroyed tcf_ext. A local attacker user can use this     vulnerability to elevate its privileges to root.This issue affects Linux Kernel: from 4.14 before git     commit ee059170b1f7e94e55fa6cadee544e176a6e59c2. (CVE-2023-1281)

    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 iscsi_sw_tcp_session_create in drivers/scsi/iscsi_tcp.c in the SCSI     sub-component in the Linux Kernel. This issue could allow an attacker to leak kernel internal information.
    (CVE-2023-2162)

    In the Linux kernel before 6.1.13, there is a double free in net/mpls/af_mpls.c upon an allocation failure     (for registering the sysctl table under a new location) during the renaming of a device. (CVE-2023-26545)

    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)

    A flaw was found in the Framebuffer Console (fbcon) in the Linux Kernel. When providing a font->width and     font->height greater than 32 to the fbcon_set_font, since there are no checks in place, a shift-out-of-     bounds occurs, leading to undefined behavior and possible denial of service. (CVE-2023-3161)

    An issue was discovered in drivers/usb/storage/ene_ub6250.c for the ENE UB6250 reader driver in the Linux     kernel before 6.2.5. An object could potentially extend beyond the end of an allocation. (CVE-2023-45862)

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

    aio: fix mremap after fork null-deref (CVE-2023-52646)

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

    net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path (CVE-2023-52703)

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

    nilfs2: fix underflow in second superblock position calculations (CVE-2023-52705)

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

    mmc: sdio: fix possible resource leaks in some error paths (CVE-2023-52730)

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

    net: USB: Fix wrong-direction WARNING in plusb.c (CVE-2023-52742)

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

    mm/swapfile: add cond_resched() in get_swap_pages() (CVE-2023-52932)

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

    Squashfs: fix handling and sanity checking of xattr_ids count (CVE-2023-52933)

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

    scsi: iscsi_tcp: Fix UAF during login when accessing the shost ipaddress (CVE-2023-52974)

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

    net: openvswitch: fix flow memory leak in ovs_flow_cmd_new (CVE-2023-52977)

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

    squashfs: harden sanity check in squashfs_read_xattr_id_table (CVE-2023-52979)

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

    irqchip/alpine-msi: Fix refcount leak in alpine_msix_init_domains (CVE-2023-53191)

    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:

    ubi: ensure that VID header offset + VID header size <= alloc, size (CVE-2023-53265)

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

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume() (CVE-2023-53271)

    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:

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

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

    scsi: ses: Don't attach if enclosure has no components (CVE-2023-53431)

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

    drm/radeon: free iio for atombios when driver shutdown (CVE-2023-53453)

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

    ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed (CVE-2023-53481)

    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:

    scsi: ses: Fix slab-out-of-bounds in ses_intf_remove() (CVE-2023-53521)

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

    scsi: ses: Fix possible desc_ptr out-of-bounds accesses (CVE-2023-53675)

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

    ubi: Fix use-after-free when volume resizing failed (CVE-2023-53800)

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

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process() (CVE-2023-53803)

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

    ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show() (CVE-2023-53826)

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

    hfs: fix missing hfs_bnode_get() in __hfs_bnode_create (CVE-2023-53862)

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

    ubi: Fix possible null-ptr-deref in ubi_free_volume() (CVE-2023-54087)

    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:

    Bluetooth: L2CAP: Fix potential user-after-free (CVE-2023-54214)

    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:

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

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

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

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses (CVE-2023-7324)

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 version of kernel installed on the remote host is prior to 5.4.235-144.344. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2023-043 advisory.

    A regression exists in the Linux Kernel within KVM: nVMX that allowed for speculative execution attacks.
    L2 can carry out Spectre v2 attacks on L1 due to L1 thinking it doesn't need retpolines or IBPB after     running L2 due to KVM (L0) advertising eIBRS support to L1. An attacker at L2 with code execution can     execute code on an indirect branch on the host machine. We recommend upgrading to Kernel 6.2 or past     commit 2e7eab81425a (CVE-2022-2196)

    It has been discovered that on some AMD CPUs, the RAS (Return Address Stack, also called RAP - Return     Address Predictor - in some AMD documentation, and RSB - Return Stack Buffer - in Intel terminology) is     dynamically partitioned between non-idle threads.  This allows an attacker to control speculative     execution on the adjacent thread. (CVE-2022-27672)

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

    netfilter: nft_tproxy: restrict to prerouting hook (CVE-2022-50001)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0458)

    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)

    The upstream bug report describes this issue as follows:

    A flaw found in the Linux Kernel in RDS (Reliable Datagram Sockets) protocol. The     rds_rm_zerocopy_callback() uses list_entry() on the head of a list causing a type confusion. Local user     can trigger this with rds_message_put(). Type confusion leads to `struct rds_msg_zcopy_info *info`     actually points to something else that is potentially controlled by local user. It is known how to trigger     this, which causes an OOB access, and a lock corruption. (CVE-2023-1078)

    Use After Free vulnerability in Linux kernel traffic control index filter (tcindex) allows Privilege     Escalation. The imperfect hash area can be updated while packets are traversing, which will cause a use-     after-free when 'tcf_exts_exec()' is called with the destroyed tcf_ext. A local attacker user can use this     vulnerability to elevate its privileges to root.This issue affects Linux Kernel: from 4.14 before git     commit ee059170b1f7e94e55fa6cadee544e176a6e59c2. (CVE-2023-1281)

    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 iscsi_sw_tcp_session_create in drivers/scsi/iscsi_tcp.c in the SCSI     sub-component in the Linux Kernel. This issue could allow an attacker to leak kernel internal information.
    (CVE-2023-2162)

    In the Linux kernel before 6.1.13, there is a double free in net/mpls/af_mpls.c upon an allocation failure     (for registering the sysctl table under a new location) during the renaming of a device. (CVE-2023-26545)

    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)

    A flaw was found in the Framebuffer Console (fbcon) in the Linux Kernel. When providing a font->width and     font->height greater than 32 to the fbcon_set_font, since there are no checks in place, a shift-out-of-     bounds occurs, leading to undefined behavior and possible denial of service. (CVE-2023-3161)

    A use-after-free flaw was found in vcs_read in drivers/tty/vt/vc_screen.c in vc_screen in the Linux     Kernel. In this flaw an attacker with local user access may lead to a system crash or a leak of internal     kernel information. (CVE-2023-3567)

    An issue was discovered in drivers/usb/storage/ene_ub6250.c for the ENE UB6250 reader driver in the Linux     kernel before 6.2.5. An object could potentially extend beyond the end of an allocation. (CVE-2023-45862)

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

    aio: fix mremap after fork null-deref (CVE-2023-52646)

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

    net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path (CVE-2023-52703)

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

    nilfs2: fix underflow in second superblock position calculations (CVE-2023-52705)

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

    sched/psi: Fix use-after-free in ep_remove_wait_queue() (CVE-2023-52707)

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

    mmc: mmc_spi: fix error handling in mmc_spi_probe() (CVE-2023-52708)

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

    mmc: sdio: fix possible resource leaks in some error paths (CVE-2023-52730)

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

    net: USB: Fix wrong-direction WARNING in plusb.c (CVE-2023-52742)

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

    IB/IPoIB: Fix legacy IPoIB due to wrong number of queues (CVE-2023-52745)

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

    mm/swapfile: add cond_resched() in get_swap_pages() (CVE-2023-52932)

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

    Squashfs: fix handling and sanity checking of xattr_ids count (CVE-2023-52933)

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

    vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF (CVE-2023-52973)

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

    scsi: iscsi_tcp: Fix UAF during login when accessing the shost ipaddress (CVE-2023-52974)

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

    efi: fix potential NULL deref in efi_mem_reserve_persistent (CVE-2023-52976)

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

    net: openvswitch: fix flow memory leak in ovs_flow_cmd_new (CVE-2023-52977)

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

    squashfs: harden sanity check in squashfs_read_xattr_id_table (CVE-2023-52979)

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

    ext4: Fix function prototype mismatch for ext4_feat_ktype (CVE-2023-53224)

    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:

    thermal/drivers/hisi: Drop second sensor hi3660 (CVE-2023-53242)

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

    ubi: ensure that VID header offset + VID header size <= alloc, size (CVE-2023-53265)

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

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume() (CVE-2023-53271)

    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:

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

    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:

    scsi: ses: Don't attach if enclosure has no components (CVE-2023-53431)

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

    drm/radeon: free iio for atombios when driver shutdown (CVE-2023-53453)

    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:

    ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed (CVE-2023-53481)

    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:

    scsi: ses: Fix slab-out-of-bounds in ses_intf_remove() (CVE-2023-53521)

    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:

    scsi: ses: Fix possible desc_ptr out-of-bounds accesses (CVE-2023-53675)

    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:

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

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

    ubi: Fix use-after-free when volume resizing failed (CVE-2023-53800)

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

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process() (CVE-2023-53803)

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

    ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show() (CVE-2023-53826)

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

    hfs: fix missing hfs_bnode_get() in __hfs_bnode_create (CVE-2023-53862)

    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:

    ubi: Fix possible null-ptr-deref in ubi_free_volume() (CVE-2023-54087)

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

    scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests (CVE-2023-54108)

    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:

    Bluetooth: L2CAP: Fix potential user-after-free (CVE-2023-54214)

    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)

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

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

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses (CVE-2023-7324)

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 version of kernel installed on the remote host is prior to 5.10.173-154.642. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2023-028 advisory.

    A regression exists in the Linux Kernel within KVM: nVMX that allowed for speculative execution attacks.
    L2 can carry out Spectre v2 attacks on L1 due to L1 thinking it doesn't need retpolines or IBPB after     running L2 due to KVM (L0) advertising eIBRS support to L1. An attacker at L2 with code execution can     execute code on an indirect branch on the host machine. We recommend upgrading to Kernel 6.2 or past     commit 2e7eab81425a (CVE-2022-2196)

    It has been discovered that on some AMD CPUs, the RAS (Return Address Stack, also called RAP - Return     Address Predictor - in some AMD documentation, and RSB - Return Stack Buffer - in Intel terminology) is     dynamically partitioned between non-idle threads.  This allows an attacker to control speculative     execution on the adjacent thread. (CVE-2022-27672)

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

    netfilter: nft_tproxy: restrict to prerouting hook (CVE-2022-50001)

    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)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0458)

    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)

    The upstream bug report describes this issue as follows:

    A flaw found in the Linux Kernel in RDS (Reliable Datagram Sockets) protocol. The     rds_rm_zerocopy_callback() uses list_entry() on the head of a list causing a type confusion. Local user     can trigger this with rds_message_put(). Type confusion leads to `struct rds_msg_zcopy_info *info`     actually points to something else that is potentially controlled by local user. It is known how to trigger     this, which causes an OOB access, and a lock corruption. (CVE-2023-1078)

    Use After Free vulnerability in Linux kernel traffic control index filter (tcindex) allows Privilege     Escalation. The imperfect hash area can be updated while packets are traversing, which will cause a use-     after-free when 'tcf_exts_exec()' is called with the destroyed tcf_ext. A local attacker user can use this     vulnerability to elevate its privileges to root.This issue affects Linux Kernel: from 4.14 before git     commit ee059170b1f7e94e55fa6cadee544e176a6e59c2. (CVE-2023-1281)

    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)

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

    The io_file_get_fixed function lacks the presence of ctx->uring_lock which can lead to a Use-After-Free     vulnerability due a race condition with fixed files getting unregistered.

    We recommend upgrading past commit da24142b1ef9fd5d36b76e36bab328a5b27523e8. (CVE-2023-1872)

    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 iscsi_sw_tcp_session_create in drivers/scsi/iscsi_tcp.c in the SCSI     sub-component in the Linux Kernel. This issue could allow an attacker to leak kernel internal information.
    (CVE-2023-2162)

    In the Linux kernel before 6.0.3, drivers/gpu/drm/virtio/virtgpu_object.c misinterprets the     drm_gem_shmem_get_sg_table return value (expects it to be NULL in the error case, whereas it is actually     an error pointer). (CVE-2023-22998)

    In the Linux kernel before 6.1.13, there is a double free in net/mpls/af_mpls.c upon an allocation failure     (for registering the sysctl table under a new location) during the renaming of a device. (CVE-2023-26545)

    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)

    A flaw was found in the Framebuffer Console (fbcon) in the Linux Kernel. When providing a font->width and     font->height greater than 32 to the fbcon_set_font, since there are no checks in place, a shift-out-of-     bounds occurs, leading to undefined behavior and possible denial of service. (CVE-2023-3161)

    A use-after-free flaw was found in vcs_read in drivers/tty/vt/vc_screen.c in vc_screen in the Linux     Kernel. In this flaw an attacker with local user access may lead to a system crash or a leak of internal     kernel information. (CVE-2023-3567)

    An issue was discovered in drivers/usb/storage/ene_ub6250.c for the ENE UB6250 reader driver in the Linux     kernel before 6.2.5. An object could potentially extend beyond the end of an allocation. (CVE-2023-45862)

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

    aio: fix mremap after fork null-deref (CVE-2023-52646)

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

    net: openvswitch: fix possible memory leak in ovs_meter_cmd_set() (CVE-2023-52702)

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

    net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path (CVE-2023-52703)

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

    nilfs2: fix underflow in second superblock position calculations (CVE-2023-52705)

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

    mmc: mmc_spi: fix error handling in mmc_spi_probe() (CVE-2023-52708)

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

    mmc: sdio: fix possible resource leaks in some error paths (CVE-2023-52730)

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

    Fix page corruption caused by racy check in __free_pages (CVE-2023-52739)

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

    cifs: Fix use-after-free in rdata->read_into_pages() (CVE-2023-52741)

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

    net: USB: Fix wrong-direction WARNING in plusb.c (CVE-2023-52742)

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

    IB/IPoIB: Fix legacy IPoIB due to wrong number of queues (CVE-2023-52745)

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

    xfrm/compat: prevent potential spectre v1 gadget in xfrm_xlate32_attr() (CVE-2023-52746)

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

    drm/i915: Fix potential bit_17 double-free (CVE-2023-52930)

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

    mm/swapfile: add cond_resched() in get_swap_pages() (CVE-2023-52932)

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

    Squashfs: fix handling and sanity checking of xattr_ids count (CVE-2023-52933)

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

    vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF (CVE-2023-52973)

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

    scsi: iscsi_tcp: Fix UAF during login when accessing the shost ipaddress (CVE-2023-52974)

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

    efi: fix potential NULL deref in efi_mem_reserve_persistent (CVE-2023-52976)

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

    net: openvswitch: fix flow memory leak in ovs_flow_cmd_new (CVE-2023-52977)

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

    squashfs: harden sanity check in squashfs_read_xattr_id_table (CVE-2023-52979)

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

    bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener (CVE-2023-52986)

    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:

    ext4: Fix function prototype mismatch for ext4_feat_ktype (CVE-2023-53224)

    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:

    thermal/drivers/hisi: Drop second sensor hi3660 (CVE-2023-53242)

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

    ubi: ensure that VID header offset + VID header size <= alloc, size (CVE-2023-53265)

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

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume() (CVE-2023-53271)

    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:

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

    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:

    scsi: ses: Don't attach if enclosure has no components (CVE-2023-53431)

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

    drm/radeon: free iio for atombios when driver shutdown (CVE-2023-53453)

    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:

    ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed (CVE-2023-53481)

    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:

    scsi: mpt3sas: Fix a memory leak (CVE-2023-53512)

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

    scsi: ses: Fix slab-out-of-bounds in ses_intf_remove() (CVE-2023-53521)

    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:

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

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

    scsi: ses: Fix possible desc_ptr out-of-bounds accesses (CVE-2023-53675)

    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:

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

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

    ubi: Fix use-after-free when volume resizing failed (CVE-2023-53800)

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

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process() (CVE-2023-53803)

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

    l2tp: Avoid possible recursive deadlock in l2tp_tunnel_register() (CVE-2023-53809)

    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:

    ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show() (CVE-2023-53826)

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

    hfs: fix missing hfs_bnode_get() in __hfs_bnode_create (CVE-2023-53862)

    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:

    ubi: Fix possible null-ptr-deref in ubi_free_volume() (CVE-2023-54087)

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

    scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests (CVE-2023-54108)

    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)

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

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

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses (CVE-2023-7324)

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.

An update of the linux package has been released.

ID	Name	Product	Family	Severity
302543	EulerOS Virtualization 2.10.0 : kernel (EulerOS-SA-2026-1557)	Nessus	Huawei Local Security Checks	high
302405	EulerOS 2.0 SP10 : kernel (EulerOS-SA-2026-1313)	Nessus	Huawei Local Security Checks	high
301628	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1280)	Nessus	Huawei Local Security Checks	high
301595	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1244)	Nessus	Huawei Local Security Checks	high
301004	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-005743)	Nessus	Unity Linux Local Security Checks	medium
300533	Unity Linux 20.1070e Security Update: kernel (UTSA-2026-005402)	Nessus	Unity Linux Local Security Checks	medium
281419	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-992814)	Nessus	Unity Linux Local Security Checks	medium
280232	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-992531)	Nessus	Unity Linux Local Security Checks	medium
279908	SUSE SLES12 Security Update : kernel (SUSE-SU-2025:4515-1)	Nessus	SuSE Local Security Checks	high
270857	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:03628-1)	Nessus	SuSE Local Security Checks	high
270837	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:03615-1)	Nessus	SuSE Local Security Checks	high
265518	Linux Distros Unpatched Vulnerability : CVE-2023-53431	Nessus	Misc.	medium
173233	Amazon Linux 2 : kernel, --advisory ALAS2-2023-1987 (ALAS-2023-1987)	Nessus	Amazon Linux Local Security Checks	high
173230	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2023-043 (ALASKERNEL-5.4-2023-043)	Nessus	Amazon Linux Local Security Checks	high
173228	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2023-028 (ALASKERNEL-5.10-2023-028)	Nessus	Amazon Linux Local Security Checks	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	high

Detections

Analytics

CVE-2023-53431

medium

Tenable Plugins

high

high

high

high

medium

medium

medium

medium

high

high

high

medium

high

high

high

high