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

  - In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: fix shift-out-of-bounds     in check_special_flags UBSAN reported a shift-out-of-bounds warning: left shift of 1 by 31 places cannot     be represented in type 'int' Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline]     dump_stack_lvl+0x8d/0xcf lib/dump_stack.c:106 ubsan_epilogue+0xa/0x44 lib/ubsan.c:151
    __ubsan_handle_shift_out_of_bounds+0x1e7/0x208 lib/ubsan.c:322 check_special_flags fs/binfmt_misc.c:241     [inline] create_entry fs/binfmt_misc.c:456 [inline] bm_register_write+0x9d3/0xa20 fs/binfmt_misc.c:654     vfs_write+0x11e/0x580 fs/read_write.c:582 ksys_write+0xcf/0x120 fs/read_write.c:637 do_syscall_x64     arch/x86/entry/common.c:50 [inline] do_syscall_64+0x34/0x80 arch/x86/entry/common.c:80     entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x4194e1 Since the type of Node's flags is unsigned     long, we should define these macros with same type too. (CVE-2022-50497)

  - In the Linux kernel, the following vulnerability has been resolved: crypto: scomp - fix req->dst buffer     overflow The req->dst buffer size should be checked before copying from the scomp_scratch->dst to avoid     req->dst buffer overflow problem. (CVE-2023-52612)

  - In the Linux kernel, the following vulnerability has been resolved: loop: Fix use-after-free issues     do_req_filebacked() calls blk_mq_complete_request() synchronously or asynchronously when using     asynchronous I/O unless memory allocation fails. Hence, modify loop_handle_cmd() such that it does not     dereference 'cmd' nor 'rq' after do_req_filebacked() finished unless we are sure that the request has not     yet been completed. This patch fixes the following kernel crash: Unable to handle kernel NULL pointer     dereference at virtual address 0000000000000054 Call trace: css_put.42938+0x1c/0x1ac     loop_process_work+0xc8c/0xfd4 loop_rootcg_workfn+0x24/0x34 process_one_work+0x244/0x558     worker_thread+0x400/0x8fc kthread+0x16c/0x1e0 ret_from_fork+0x10/0x20 (CVE-2023-53111)

  - In the Linux kernel, the following vulnerability has been resolved: ubi: ensure that VID header offset +     VID header size <= alloc, size Ensure that the VID header offset + VID header size does not exceed the     allocated area to avoid slab OOB. BUG: KASAN: slab-out-of-bounds in crc32_body lib/crc32.c:111 [inline]     BUG: KASAN: slab-out-of-bounds in crc32_le_generic lib/crc32.c:179 [inline] BUG: KASAN: slab-out-of-bounds     in crc32_le_base+0x58c/0x626 lib/crc32.c:197 Read of size 4 at addr ffff88802bb36f00 by task syz-     executor136/1555 CPU: 2 PID: 1555 Comm: syz-executor136 Tainted: G W 6.0.0-1868 #1 Hardware name: Red Hat     KVM, BIOS 1.13.0-2.module+el8.3.0+7860+a7792d29 04/01/2014 Call Trace: <TASK> __dump_stack     lib/dump_stack.c:88 [inline] dump_stack_lvl+0x85/0xad lib/dump_stack.c:106 print_address_description     mm/kasan/report.c:317 [inline] print_report.cold.13+0xb6/0x6bb mm/kasan/report.c:433     kasan_report+0xa7/0x11b mm/kasan/report.c:495 crc32_body lib/crc32.c:111 [inline] crc32_le_generic     lib/crc32.c:179 [inline] crc32_le_base+0x58c/0x626 lib/crc32.c:197 ubi_io_write_vid_hdr+0x1b7/0x472     drivers/mtd/ubi/io.c:1067 create_vtbl+0x4d5/0x9c4 drivers/mtd/ubi/vtbl.c:317 create_empty_lvol     drivers/mtd/ubi/vtbl.c:500 [inline] ubi_read_volume_table+0x67b/0x288a drivers/mtd/ubi/vtbl.c:812     ubi_attach+0xf34/0x1603 drivers/mtd/ubi/attach.c:1601 ubi_attach_mtd_dev+0x6f3/0x185e     drivers/mtd/ubi/build.c:965 ctrl_cdev_ioctl+0x2db/0x347 drivers/mtd/ubi/cdev.c:1043 vfs_ioctl     fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline]
    __x64_sys_ioctl+0x193/0x213 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline]     do_syscall_64+0x3e/0x86 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0x0 RIP:
    0033:0x7f96d5cf753d Code: RSP: 002b:00007fffd72206f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX:
    ffffffffffffffda RBX: 0000000000000000 RCX: 00007f96d5cf753d RDX: 0000000020000080 RSI: 0000000040186f40     RDI: 0000000000000003 RBP: 0000000000400cd0 R08: 0000000000000000 R09: 0000000000000000 R10:
    0000000000000000 R11: 0000000000000246 R12: 0000000000400be0 R13: 00007fffd72207e0 R14: 0000000000000000     R15: 0000000000000000 </TASK> Allocated by task 1555: kasan_save_stack+0x20/0x3d mm/kasan/common.c:38     kasan_set_track mm/kasan/common.c:45 [inline] set_alloc_info mm/kasan/common.c:437 [inline]
    ____kasan_kmalloc mm/kasan/common.c:516 [inline] __kasan_kmalloc+0x88/0xa3 mm/kasan/common.c:525     kasan_kmalloc include/linux/kasan.h:234 [inline] __kmalloc+0x138/0x257 mm/slub.c:4429 kmalloc     include/linux/slab.h:605 [inline] ubi_alloc_vid_buf drivers/mtd/ubi/ubi.h:1093 [inline]     create_vtbl+0xcc/0x9c4 drivers/mtd/ubi/vtbl.c:295 create_empty_lvol drivers/mtd/ubi/vtbl.c:500 [inline]     ubi_read_volume_table+0x67b/0x288a drivers/mtd/ubi/vtbl.c:812 ubi_attach+0xf34/0x1603     drivers/mtd/ubi/attach.c:1601 ubi_attach_mtd_dev+0x6f3/0x185e drivers/mtd/ubi/build.c:965     ctrl_cdev_ioctl+0x2db/0x347 drivers/mtd/ubi/cdev.c:1043 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl     fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __x64_sys_ioctl+0x193/0x213 fs/ioctl.c:856     do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3e/0x86 arch/x86/entry/common.c:80     entry_SYSCALL_64_after_hwframe+0x63/0x0 The buggy address belongs to the object at ffff88802bb36e00 which     belongs to the cache kmalloc-256 of size 256 The buggy address is located 0 bytes to the right of 256-byte     region [ffff88802bb36e00, ffff88802bb36f00) The buggy address belongs to the physical page:
    page:00000000ea4d1263 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x2bb36     head:00000000ea4d1263 order:1 compound_mapcount:0 compound_pincount:0 flags:
    0xfffffc0010200(slab|head|node=0|zone=1|lastcpupid=0x1fffff) raw: 000fffffc0010200 ffffea000066c300     dead000000000003 ffff888100042b40 raw: 0000000000000000 00000000001 ---truncated--- (CVE-2023-53265)

  - In the Linux kernel, the following vulnerability has been resolved: net: fec: Better handle     pm_runtime_get() failing in .remove() In the (unlikely) event that pm_runtime_get() (disguised as     pm_runtime_resume_and_get()) fails, the remove callback returned an error early. The problem with this is     that the driver core ignores the error value and continues removing the device. This results in a resource     leak. Worse the devm allocated resources are freed and so if a callback of the driver is called later the     register mapping is already gone which probably results in a crash. (CVE-2023-53308)

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

    The SUSE Linux Enterprise 12 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2021-4460: drm/amdkfd: Fix UBSAN shift-out-of-bounds warning (bsc#1250764).
    - CVE-2022-48631: ext4: fix bug in extents parsing when eh_entries == 0 and eh_depth > 0 (bsc#1223475).
    - CVE-2022-50236: iommu/mediatek: Fix crash on isr after kexec() (bsc#1249702).
    - CVE-2022-50249: memory: of: Fix refcount leak bug in of_get_ddr_timings() (bsc#1249747).
    - CVE-2022-50280: pnode: terminate at peers of source (bsc#1249806).
    - CVE-2022-50293: btrfs: do not BUG_ON() on ENOMEM when dropping extent items for a range (bsc#1249752).
    - CVE-2022-50327: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value (bsc#1249859).
    - CVE-2022-50350: scsi: target: iscsi: Fix a race condition between login_work and the login thread     (bsc#1250261).
    - CVE-2022-50356: net: sched: sfb: fix null pointer access issue when sfb_init() fails (bsc#1250040).
    - CVE-2022-50367: fs: fix UAF/GPF bug in nilfs_mdt_destroy (bsc#1250277).
    - CVE-2022-50394: i2c: ismt: Fix an out-of-bounds bug in ismt_access() (bsc#1250107).
    - CVE-2022-50395: integrity: Fix memory leakage in keyring allocation error path (bsc#1250211).
    - CVE-2022-50423: ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage() (bsc#1250784).
    - CVE-2022-50443: drm/rockchip: lvds: fix PM usage counter unbalance in poweron (bsc#1250768).
    - CVE-2022-50459: scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername() (bsc#1250850).
    - CVE-2022-50481: cxl: fix possible null-ptr-deref in cxl_guest_init_afu|adapter() (bsc#1251051).
    - CVE-2022-50485: ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode (bsc#1251197).
    - CVE-2022-50505: iommu/amd: Fix pci device refcount leak in ppr_notifier() (bsc#1251086).
    - CVE-2022-50516: fs: dlm: fix invalid derefence of sb_lvbptr (bsc#1251741).
    - CVE-2022-50542: media: si470x: Fix use-after-free in si470x_int_in_callback() (bsc#1251330).
    - CVE-2022-50571: btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure (bsc#1252487).
    - CVE-2023-53183: btrfs: exit gracefully if reloc roots don't match (bsc#1249863).
    - CVE-2023-53185: wifi: ath9k: don't allow to overwrite ENDPOINT0 attributes (bsc#1249820).
    - CVE-2023-53188: net: openvswitch: fix race on port output (bsc#1249854).
    - CVE-2023-53191: irqchip/alpine-msi: Fix refcount leak in alpine_msix_init_domains (bsc#1249721).
    - CVE-2023-53204: af_unix: Fix data-races around user->unix_inflight (bsc#1249682).
    - CVE-2023-53271: ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume() (bsc#1249916).
    - CVE-2023-53282: scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write     (bsc#1250311).
    - CVE-2023-53289: media: bdisp: Add missing check for create_workqueue (bsc#1249941).
    - CVE-2023-53292: blk-mq: protect q->elevator by ->sysfs_lock in blk_mq_elv_switch_none (bsc#1250163).
    - CVE-2023-53338: lwt: Fix return values of BPF xmit ops (bsc#1250074).
    - CVE-2023-53339: btrfs: fix BUG_ON condition in btrfs_cancel_balance (bsc#1250329).
    - CVE-2023-53373: crypto: seqiv - Handle EBUSY correctly (bsc#1250137).
    - CVE-2023-53433: net: add vlan_get_protocol_and_depth() helper (bsc#1250164).
    - CVE-2023-53476: iw_cxgb4: Fix potential NULL dereference in c4iw_fill_res_cm_id_entry() (bsc#1250839).
    - CVE-2023-53477: ipv6: Add lwtunnel encap size of all siblings in nexthop calculation (bsc#1250840).
    - CVE-2023-53484: lib: cpu_rmap: Avoid use after free on rmap->obj array entries (bsc#1250895).
    - CVE-2023-53517: tipc: do not update mtu if msg_max is too small in mtu negotiation (bsc#1250919).
    - CVE-2023-53519: media: v4l2-mem2mem: add lock to protect parameter num_rdy (bsc#1250964).
    - CVE-2023-53540: wifi: cfg80211: reject auth/assoc to AP with our address (bsc#1251053).
    - CVE-2023-53548: net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb (bsc#1251066).
    - CVE-2023-53556: iavf: Fix use-after-free in free_netdev (bsc#1251059).
    - CVE-2023-53559: ip_vti: fix potential slab-use-after-free in decode_session6 (bsc#1251052).
    - CVE-2023-53582: wifi: brcmfmac: ensure CLM version is null-terminated to prevent stack-out-of-bounds     (bsc#1251061).
    - CVE-2023-53589: wifi: iwlwifi: mvm: don't trust firmware n_channels (bsc#1251129).
    - CVE-2023-53593: cifs: Release folio lock on fscache read hit (bsc#1251132).
    - CVE-2023-53594: driver core: fix resource leak in device_add() (bsc#1251166).
    - CVE-2023-53596: drivers: base: Free devm resources when unregistering a device (bsc#1251161).
    - CVE-2023-53619: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free (bsc#1251743).
    - CVE-2023-53620: md: fix soft lockup in status_resync.
    - CVE-2023-53624: net/sched: sch_fq: fix integer overflow of 'credit' (bsc#1251333).
    - CVE-2023-53635: netfilter: conntrack: fix wrong ct->timeout value (bsc#1251524).
    - CVE-2023-53648: ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer (bsc#1251750).
    - CVE-2023-53687: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating     clk (bsc#1251772).
    - CVE-2023-53695: udf: Detect system inodes linked into directory hierarchy (bsc#1252539).
    - CVE-2023-53705: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (bsc#1252554).
    - CVE-2023-53707: drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1 (bsc#1252632).
    - CVE-2023-53715: wifi: brcmfmac: cfg80211: Pass the PMK in binary instead of hex (bsc#1252545).
    - CVE-2023-53717: wifi: ath9k: Fix potential stack-out-of-bounds write in ath9k_wmi_rsp_callback()     (bsc#1252560).
    - CVE-2023-53733: net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode (bsc#1252685).
    - CVE-2025-38539: trace/fgraph: Fix the warning caused by missing unregister notifier (bsc#1248211).
    - CVE-2025-38680: media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (bsc#1249203).
    - CVE-2025-38691: pNFS: Fix uninited ptr deref in block/scsi layout (bsc#1249215).
    - CVE-2025-38695: scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1249285).
    - CVE-2025-38699: scsi: bfa: Double-free fix (bsc#1249224).
    - CVE-2025-38700: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated     (bsc#1249182).
    - CVE-2025-38714: hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() (bsc#1249260).
    - CVE-2025-38718: sctp: linearize cloned gso packets in sctp_rcv (bsc#1249161).
    - CVE-2025-38724: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (bsc#1249169).
    - CVE-2025-39676: scsi: qla4xxx: Prevent a potential error pointer dereference (bsc#1249302).
    - CVE-2025-39702: ipv6: sr: Fix MAC comparison to be constant-time (bsc#1249317).
    - CVE-2025-39724: serial: 8250: fix panic due to PSLVERR (bsc#1249265).
    - CVE-2025-39756: fs: Prevent file descriptor table allocations exceeding INT_MAX (bsc#1249512).
    - CVE-2025-39772: drm/hisilicon/hibmc: fix the hibmc loaded failed bug (bsc#1249506).
    - CVE-2025-39812: sctp: initialize more fields in sctp_v6_from_sk() (bsc#1250202).
    - CVE-2025-39813: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump (bsc#1250032).
    - CVE-2025-39841: scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250274).
    - CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty() (bsc#1250455).
    - CVE-2025-39876: net: fec: Fix possible NPD in fec_enet_phy_reset_after_clk_enable() (bsc#1250400).
    - CVE-2025-39911: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path (bsc#1250704).
    - CVE-2025-39923: dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (bsc#1250741).
    - CVE-2025-39929: smb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path (bsc#1251036).
    - CVE-2025-39931: crypto: af_alg - Set merge to zero early in af_alg_sendmsg (bsc#1251100).
    - CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).
    - CVE-2025-39949: qed: Don't collect too many protection override GRC elements (bsc#1251177).
    - CVE-2025-39955: tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect() (bsc#1251804).
    - CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).
    - CVE-2025-39970: i40e: Fix filter input checks to prevent config with invalid values (bsc#1252051).
    - CVE-2025-39971: i40e: Add bounds check for ch[] array (bsc#1252052).
    - CVE-2025-39972: i40e: fix idx validation in i40e_validate_queue_map (bsc#1252039).
    - CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).
    - CVE-2025-39997: ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (bsc#1252056).
    - CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).
    - CVE-2025-40044: fs: udf: fix OOB read in lengthAllocDescs handling (bsc#1252785).
    - CVE-2025-40049: Squashfs: fix uninit-value in squashfs_get_parent (bsc#1252822).
    - CVE-2025-40078: bpf: Explicitly check accesses to bpf_sock_addr (bsc#1252789).
    - CVE-2025-40082: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1252775).
    - CVE-2025-40088: hfsplus: fix slab-out-of-bounds read in hfsplus_strcasecmp() (bsc#1252904).

    The following non security issues were fixed:

    - NFSv4.1: fix backchannel max_resp_sz verification check (bsc#1247518).
    - net: hv_netvsc: fix loss of early receive events from host during channel open (bsc#1252265).
    - openvswitch: fix lockup on tx to unregistering netdev with carrier (bsc#1249854)

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.

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

    x86/mce: Work around an erratum on fast string copy instructions(CVE-2022-49124)

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()(CVE-2022-49142)

    scsi: qla2xxx: Fix premature hw access after PCI error(CVE-2022-49157)

    scsi: qla2xxx: Fix warning message due to adisc being flushed(CVE-2022-49158)

    scsi: qla2xxx: Implement ref count for SRB(CVE-2022-49159)

    USB: core: Prevent nested device-reset calls(CVE-2022-49936)

    mmc: vub300: fix return value check of mmc_add_host()(CVE-2022-50251)

    tracing: Fix reading strings from synthetic events(CVE-2022-50255)

    kprobes: Fix check for probe enabled in kill_kprobe()(CVE-2022-50266)

    mmc: rtsx_pci: fix return value check of mmc_add_host()(CVE-2022-50267)

    pnode: terminate at peers of source(CVE-2022-50280)

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline(CVE-2022-50286)

    ext4: fix potential out of bound read in ext4_fc_replay_scan()(CVE-2022-50306)

    drivers: serial: jsm: fix some leaks in probe(CVE-2022-50312)

    erofs: fix order = MAX_ORDER warning due to crafted negative i_size(CVE-2022-50313)

    ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS(CVE-2022-50315)

    perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox()(CVE-2022-50318)

    net: do not sense pfmemalloc status in skb_append_pagefrags()(CVE-2022-50323)

    jbd2: fix potential use-after-free in jbd2_fc_wait_bufs(CVE-2022-50328)

    crypto: cavium - prevent integer overflow loading firmware(CVE-2022-50330)

    ext4: fix null-ptr-deref in ext4_write_info(CVE-2022-50344)

    ext4: init quota for 'old.inode' in 'ext4_rename'(CVE-2022-50346)

    scsi: target: iscsi: Fix a race condition between login_work and the login thread(CVE-2022-50350)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50377)

    padata: Always leave BHs disabled when running -parallel()(CVE-2022-50382)

    nvme: fix multipath crash caused by flush request when blktrace is enabled(CVE-2022-50388)

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak(CVE-2022-50389)

    drm/ttm: fix undefined behavior in bit shift for TTM_TT_FLAG_PRIV_POPULATED(CVE-2022-50390)

    i2c: ismt: Fix an out-of-bounds bug in ismt_access()(CVE-2022-50394)

    ACPICA: Fix error code path in acpi_ds_call_control_method()(CVE-2022-50411)

    x86/fpu: Fix copy_xstate_to_uabi() to copy init states correctly(CVE-2022-50425)

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING(CVE-2022-50430)

    drm/vmwgfx: Validate the box size for the snooped cursor(CVE-2022-50440)

    cpufreq: Init completion before kobject_init_and_add()(CVE-2022-50473)

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode(CVE-2022-50485)

    scsi: qla2xxx: Fix crash when I/O abort times out(CVE-2022-50493)

    binfmt_misc: fix shift-out-of-bounds in check_special_flags(CVE-2022-50497)

    perf/smmuv3: Fix hotplug callback leak in arm_smmu_pmu_init()(CVE-2022-50510)

    tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx'(CVE-2022-50553)

    ext4: avoid deadlock in fs reclaim with page writeback(CVE-2023-53149)

    tracing: Fix null pointer dereference in tracing_err_log_open()(CVE-2023-53167)

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

    serial: 8250: Reinit port-pm on port specific driver unbind(CVE-2023-53176)

    mm: fix zswap writeback race condition(CVE-2023-53178)

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

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

    media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()(CVE-2023-53220)

    bpf: Fix memleak due to fentry attach failure(CVE-2023-53221)

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

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

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

    ext4: fix i_disksize exceeding i_size problem in paritally written case(CVE-2023-53270)

    scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue(CVE-2023-53280)

    ext4: add bounds checking in get_max_inline_xattr_value_size()(CVE-2023-53285)

    drm/client: Fix memory leak in drm_client_modeset_probe(CVE-2023-53288)

    ext4: fix WARNING in mb_find_extent(CVE-2023-53317)

    recordmcount: Fix memory leaks in the uwrite function(CVE-2023-53318)

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

    tracing: Fix race issue between cpu buffer write and swap(CVE-2023-53368)

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

    tracing: Free error logs of tracing instances(CVE-2023-53375)

    ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer(CVE-2023-53395)

    mm: kmem: fix a NULL pointer dereference in obj_stock_flush_required()(CVE-2023-53401)

    blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()(CVE-2023-53421)

    media: uvcvideo: Handle cameras with invalid descriptors(CVE-2023-53437)

    bpf: cpumap: Fix memory leak in cpu_map_update_elem(CVE-2023-53441)

    ext4: remove a BUG_ON in ext4_mb_release_group_pa()(CVE-2023-53450)

    scsi: qla4xxx: Add length check when parsing nlattrs(CVE-2023-53456)

    kobject: Add sanity check for kset-kobj.ktype in kset_register()(CVE-2023-53480)

    ext4: allow ext4_get_group_info() to fail(CVE-2023-53503)

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

    virtio-mmio: don't break lifecycle of vm_dev(CVE-2023-53515)

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

    scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()(CVE-2023-53530)

    tracing/histograms: Add histograms to hist_vars if they have referenced variables(CVE-2023-53560)

    null_blk: Always check queue mode setting from configfs(CVE-2023-53576)

    bpf, cpumap: Make sure kthread is running before map update returns(CVE-2023-53577)

    ring-buffer: Sync IRQ works before buffer destruction(CVE-2023-53587)

    ipmi_si: fix a memleak in try_smi_init()(CVE-2023-53611)

    ext4: fix possible double unlock when moving a directory(CVE-2023-53626)

    bnxt: avoid overflow in bnxt_get_nvram_directory()(CVE-2023-53661)

    ring-buffer: Fix deadloop issue on reading trace_pipe(CVE-2023-53668)

    A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D     cache, potentially resulting in the leakage of sensitive information across privileged     boundaries.(CVE-2024-36357)

    drm/dp_mst: Fix MST sideband message body length check(CVE-2024-56616)

    tls: stop recv() if initial process_rx_list gave us non-DATA(CVE-2024-58239)

    crypto: algif_hash - fix double free in hash_accept(CVE-2025-38079)

    thunderbolt: Do not double dequeue a configuration request(CVE-2025-38174)

    mm: fix uprobe pte be overwritten when expanding vma(CVE-2025-38207)

    scsi: lpfc: Use memcpy() for BIOS version(CVE-2025-38332)

    x86/sgx: Prevent attempts to reclaim poisoned pages(CVE-2025-38334)

    HID: core: do not bypass hid_hw_raw_request(CVE-2025-38494)

    clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns(CVE-2025-38499)

    bpf: Fix oob access in cgroup local storage(CVE-2025-38502)

    drm/sched: Increment job count before swapping tail spsc queue(CVE-2025-38515)

    pinctrl: qcom: msm: mark certain pins as invalid for interrupts(CVE-2025-38516)

    HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras(CVE-2025-38540)

    net/sched: Restrict conditions for adding duplicating netems to qdisc tree(CVE-2025-38553)

    crypto: ccp - Fix crash when rebind ccp device for ccp.ko(CVE-2025-38581)

    padata: Fix pd UAF once and for all(CVE-2025-38584)

    net: drop UFO packets in udp_rcv_segment()(CVE-2025-38622)

    regulator: core: fix NULL dereference on unbind due to stale coupling data(CVE-2025-38668)

    media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format()(CVE-2025-38680)

    fbdev: Fix vmalloc out-of-bounds write in fast_imageblit(CVE-2025-38685)

    media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and     w7090p_tuner_read_serpar(CVE-2025-38693)

    scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure(CVE-2025-38695)

    ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr(CVE-2025-38701)

    x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper(CVE-2025-39681)

    tracing: Limit access to parser-buffer when trace_get_user failed(CVE-2025-39683)

    ftrace: Also allocate and copy hash for reading of filter files(CVE-2025-39689)

    fs/buffer: fix use-after-free when call bh_read() helper(CVE-2025-39691)

    serial: 8250: fix panic due to PSLVERR(CVE-2025-39724)

    rcu: Fix rcu_read_unlock() deadloop due to IRQ work(CVE-2025-39744)

    rcu: Protect -defer_qs_iw_pending from data race(CVE-2025-39749)

    usb: core: config: Prevent OOB read in SS endpoint companion parsing(CVE-2025-39760)

    jbd2: prevent softlockup in jbd2_log_do_checkpoint()(CVE-2025-39782)

    ftrace: Fix potential warning in trace_printk_seq during ftrace_dump(CVE-2025-39813)

    trace/fgraph: Fix the warning caused by missing unregister notifier(CVE-2025-39829)

    vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects(CVE-2025-39850)

    vxlan: Fix NPD when refreshing an FDB entry with a nexthop object(CVE-2025-39851)

    tee: fix NULL pointer dereference in tee_shm_put(CVE-2025-39865)

    fs: writeback: fix use-after-free in __mark_inode_dirty()(CVE-2025-39866)

    cgroup: split cgroup_destroy_wq into 3 workqueues(CVE-2025-39953)

    fbcon: fix integer overflow in fbcon_do_set_font(CVE-2025-39967)

    i40e: add max boundary check for VF filters(CVE-2025-39968)

    i40e: fix idx validation in config queues msg(CVE-2025-39971)

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

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.

The CentOS Linux 8.5 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.5:CLSA-2026:1773047921 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: asix: fix uninit-value in     asix_mdio_read() asix_read_cmd() may read less than sizeof(smsr) bytes and in this case smsr will be     uninitialized. Fail log: BUG: KMSAN: uninit-value in asix_check_host_enable     drivers/net/usb/asix_common.c:82 [inline] BUG: KMSAN: uninit-value in asix_check_host_enable     drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497 BUG: KMSAN: uninit-value in     asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497     asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] asix_check_host_enable     drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497 asix_mdio_read+0x3c1/0xb00     drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497 (CVE-2021-47101)

  - In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Avoid field-overflowing     memcpy() In preparation for FORTIFY_SOURCE performing compile-time and run-time field bounds checking for     memcpy(), memmove(), and memset(), avoid intentionally writing across neighboring fields. Use flexible     arrays instead of zero-element arrays (which look like they are always overflowing) and split the cross-     field memcpy() into two halves that can be appropriately bounds-checked by the compiler. We were doing:
    #define ETH_HLEN 14 #define VLAN_HLEN 4 ... #define MLX5E_XDP_MIN_INLINE (ETH_HLEN + VLAN_HLEN) ... struct     mlx5e_tx_wqe *wqe = mlx5_wq_cyc_get_wqe(wq, pi); ... struct mlx5_wqe_eth_seg *eseg = &wqe->eth; struct     mlx5_wqe_data_seg *dseg = wqe->data; ... memcpy(eseg->inline_hdr.start, xdptxd->data,     MLX5E_XDP_MIN_INLINE); target is wqe->eth.inline_hdr.start (which the compiler sees as being 2 bytes in     size), but copying 18, intending to write across start (really vlan_tci, 2 bytes). The remaining 16 bytes     get written into wqe->data[0], covering byte_count (4 bytes), lkey (4 bytes), and addr (8 bytes). struct     mlx5e_tx_wqe { struct mlx5_wqe_ctrl_seg ctrl; /* 0 16 */ struct mlx5_wqe_eth_seg eth; /* 16 16 */ struct     mlx5_wqe_data_seg data[]; /* 32 0 */ /* size: 32, cachelines: 1, members: 3 */ /* last cacheline: 32 bytes
    */ }; struct mlx5_wqe_eth_seg { u8 swp_outer_l4_offset; /* 0 1 */ u8 swp_outer_l3_offset; /* 1 1 */ u8     swp_inner_l4_offset; /* 2 1 */ u8 swp_inner_l3_offset; /* 3 1 */ u8 cs_flags; /* 4 1 */ u8 swp_flags; /* 5     1 */ __be16 mss; /* 6 2 */ __be32 flow_table_metadata; /* 8 4 */ union { struct { __be16 sz; /* 12 2 */ u8     start[2]; /* 14 2 */ } inline_hdr; /* 12 4 */ struct { __be16 type; /* 12 2 */ __be16 vlan_tci; /* 14 2 */     } insert; /* 12 4 */ __be32 trailer; /* 12 4 */ }; /* 12 4 */ /* size: 16, cachelines: 1, members: 9 */ /*     last cacheline: 16 bytes */ }; struct mlx5_wqe_data_seg { __be32 byte_count; /* 0 4 */ __be32 lkey; /* 4 4
    */ __be64 addr; /* 8 8 */ /* size: 16, cachelines: 1, members: 3 */ /* last cacheline: 16 bytes */ }; So,     split the memcpy() so the compiler can reason about the buffer sizes. pahole shows no size nor member     offset changes to struct mlx5e_tx_wqe nor struct mlx5e_umr_wqe. objdump -d shows no meaningful object     code changes (i.e. only source line number induced differences and optimizations). (CVE-2022-48744)

  - In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix the behavior of READ near     OFFSET_MAX Dan Aloni reports: > Due to commit 8cfb9015280d (NFS: Always provide aligned buffers to > the     RPC read layers) on the client, a read of 0xfff is aligned up > to server rsize of 0x1000. > > As a     result, in a test where the server has a file of size > 0x7fffffffffffffff, and the client tries to read     from the offset > 0x7ffffffffffff000, the read causes loff_t overflow in the server > and it returns an     NFS code of EINVAL to the client. The client as > a result indefinitely retries the request. The Linux NFS     client does not handle NFS?ERR_INVAL, even though all NFS specifications permit servers to return that     status code for a READ. Instead of NFS?ERR_INVAL, have out-of-range READ requests succeed and return a     short result. Set the EOF flag in the result to prevent the client from retrying the READ request. This     behavior appears to be consistent with Solaris NFS servers. Note that NFSv3 and NFSv4 use u64 offset     values on the wire. These must be converted to loff_t internally before use -- an implicit type cast is     not adequate for this purpose. Otherwise VFS checks against sb->s_maxbytes do not work properly.
    (CVE-2022-48827)

  - In the Linux kernel, the following vulnerability has been resolved: virtio_net: fix xdp_rxq_info bug after     suspend/resume The following sequence currently causes a driver bug warning when using virtio_net: # ip     link set eth0 up # echo mem > /sys/power/state (or e.g. # rtcwake -s 10 -m mem) <resume> # ip link set     eth0 down Missing register, driver bug WARNING: CPU: 0 PID: 375 at net/core/xdp.c:138     xdp_rxq_info_unreg+0x58/0x60 Call trace: xdp_rxq_info_unreg+0x58/0x60 virtnet_close+0x58/0xac
    __dev_close_many+0xac/0x140 __dev_change_flags+0xd8/0x210 dev_change_flags+0x24/0x64     do_setlink+0x230/0xdd0 ... This happens because virtnet_freeze() frees the receive_queue completely     (including struct xdp_rxq_info) but does not call xdp_rxq_info_unreg(). Similarly, virtnet_restore() sets     up the receive_queue again but does not call xdp_rxq_info_reg(). Actually, parts of virtnet_freeze_down()     and virtnet_restore_up() are almost identical to virtnet_close() and virtnet_open(): only the calls to     xdp_rxq_info_(un)reg() are missing. This means that we can fix this easily and avoid such problems in the     future by just calling virtnet_close()/open() from the freeze/restore handlers. Aside from adding the     missing xdp_rxq_info calls the only difference is that the refill work is only cancelled if     netif_running(). However, this should not make any functional difference since the refill work should only     be active if the network interface is actually up. (CVE-2022-49687)

  - In the Linux kernel, the following vulnerability has been resolved: ceph: avoid putting the realm twice     when decoding snaps fails When decoding the snaps fails it maybe leaving the 'first_realm' and 'realm'     pointing to the same snaprealm memory. And then it'll put it twice and could cause random use-after-free,     BUG_ON, etc issues. (CVE-2022-49770)

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 :

    x86/mce: Work around an erratum on fast string copy instructions(CVE-2022-49124)

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()(CVE-2022-49142)

    scsi: qla2xxx: Fix premature hw access after PCI error(CVE-2022-49157)

    scsi: qla2xxx: Fix warning message due to adisc being flushed(CVE-2022-49158)

    scsi: qla2xxx: Implement ref count for SRB(CVE-2022-49159)

    USB: core: Prevent nested device-reset calls(CVE-2022-49936)

    mmc: vub300: fix return value check of mmc_add_host()(CVE-2022-50251)

    tracing: Fix reading strings from synthetic events(CVE-2022-50255)

    kprobes: Fix check for probe enabled in kill_kprobe()(CVE-2022-50266)

    mmc: rtsx_pci: fix return value check of mmc_add_host()(CVE-2022-50267)

    pnode: terminate at peers of source(CVE-2022-50280)

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline(CVE-2022-50286)

    ext4: fix potential out of bound read in ext4_fc_replay_scan()(CVE-2022-50306)

    drivers: serial: jsm: fix some leaks in probe(CVE-2022-50312)

    erofs: fix order = MAX_ORDER warning due to crafted negative i_size(CVE-2022-50313)

    ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS(CVE-2022-50315)

    perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox()(CVE-2022-50318)

    net: do not sense pfmemalloc status in skb_append_pagefrags()(CVE-2022-50323)

    jbd2: fix potential use-after-free in jbd2_fc_wait_bufs(CVE-2022-50328)

    crypto: cavium - prevent integer overflow loading firmware(CVE-2022-50330)

    ext4: fix null-ptr-deref in ext4_write_info(CVE-2022-50344)

    ext4: init quota for 'old.inode' in 'ext4_rename'(CVE-2022-50346)

    scsi: target: iscsi: Fix a race condition between login_work and the login thread(CVE-2022-50350)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50377)

    padata: Always leave BHs disabled when running -parallel()(CVE-2022-50382)

    nvme: fix multipath crash caused by flush request when blktrace is enabled(CVE-2022-50388)

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak(CVE-2022-50389)

    drm/ttm: fix undefined behavior in bit shift for TTM_TT_FLAG_PRIV_POPULATED(CVE-2022-50390)

    i2c: ismt: Fix an out-of-bounds bug in ismt_access()(CVE-2022-50394)

    ACPICA: Fix error code path in acpi_ds_call_control_method()(CVE-2022-50411)

    x86/fpu: Fix copy_xstate_to_uabi() to copy init states correctly(CVE-2022-50425)

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING(CVE-2022-50430)

    drm/vmwgfx: Validate the box size for the snooped cursor(CVE-2022-50440)

    cpufreq: Init completion before kobject_init_and_add()(CVE-2022-50473)

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode(CVE-2022-50485)

    scsi: qla2xxx: Fix crash when I/O abort times out(CVE-2022-50493)

    binfmt_misc: fix shift-out-of-bounds in check_special_flags(CVE-2022-50497)

    perf/smmuv3: Fix hotplug callback leak in arm_smmu_pmu_init()(CVE-2022-50510)

    tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx'(CVE-2022-50553)

    ext4: avoid deadlock in fs reclaim with page writeback(CVE-2023-53149)

    tracing: Fix null pointer dereference in tracing_err_log_open()(CVE-2023-53167)

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

    serial: 8250: Reinit port-pm on port specific driver unbind(CVE-2023-53176)

    mm: fix zswap writeback race condition(CVE-2023-53178)

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

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

    media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()(CVE-2023-53220)

    bpf: Fix memleak due to fentry attach failure(CVE-2023-53221)

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

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

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

    ext4: fix i_disksize exceeding i_size problem in paritally written case(CVE-2023-53270)

    scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue(CVE-2023-53280)

    ext4: add bounds checking in get_max_inline_xattr_value_size()(CVE-2023-53285)

    drm/client: Fix memory leak in drm_client_modeset_probe(CVE-2023-53288)

    ext4: fix WARNING in mb_find_extent(CVE-2023-53317)

    recordmcount: Fix memory leaks in the uwrite function(CVE-2023-53318)

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

    tracing: Fix race issue between cpu buffer write and swap(CVE-2023-53368)

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

    tracing: Free error logs of tracing instances(CVE-2023-53375)

    ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer(CVE-2023-53395)

    mm: kmem: fix a NULL pointer dereference in obj_stock_flush_required()(CVE-2023-53401)

    blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()(CVE-2023-53421)

    media: uvcvideo: Handle cameras with invalid descriptors(CVE-2023-53437)

    bpf: cpumap: Fix memory leak in cpu_map_update_elem(CVE-2023-53441)

    ext4: remove a BUG_ON in ext4_mb_release_group_pa()(CVE-2023-53450)

    scsi: qla4xxx: Add length check when parsing nlattrs(CVE-2023-53456)

    kobject: Add sanity check for kset-kobj.ktype in kset_register()(CVE-2023-53480)

    ext4: allow ext4_get_group_info() to fail(CVE-2023-53503)

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

    virtio-mmio: don't break lifecycle of vm_dev(CVE-2023-53515)

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

    scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()(CVE-2023-53530)

    tracing/histograms: Add histograms to hist_vars if they have referenced variables(CVE-2023-53560)

    null_blk: Always check queue mode setting from configfs(CVE-2023-53576)

    bpf, cpumap: Make sure kthread is running before map update returns(CVE-2023-53577)

    ring-buffer: Sync IRQ works before buffer destruction(CVE-2023-53587)

    ipmi_si: fix a memleak in try_smi_init()(CVE-2023-53611)

    ext4: fix possible double unlock when moving a directory(CVE-2023-53626)

    bnxt: avoid overflow in bnxt_get_nvram_directory()(CVE-2023-53661)

    ring-buffer: Fix deadloop issue on reading trace_pipe(CVE-2023-53668)

    A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D     cache, potentially resulting in the leakage of sensitive information across privileged     boundaries.(CVE-2024-36357)

    drm/dp_mst: Fix MST sideband message body length check(CVE-2024-56616)

    tls: stop recv() if initial process_rx_list gave us non-DATA(CVE-2024-58239)

    crypto: algif_hash - fix double free in hash_accept(CVE-2025-38079)

    thunderbolt: Do not double dequeue a configuration request(CVE-2025-38174)

    mm: fix uprobe pte be overwritten when expanding vma(CVE-2025-38207)

    scsi: lpfc: Use memcpy() for BIOS version(CVE-2025-38332)

    x86/sgx: Prevent attempts to reclaim poisoned pages(CVE-2025-38334)

    HID: core: do not bypass hid_hw_raw_request(CVE-2025-38494)

    clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns(CVE-2025-38499)

    bpf: Fix oob access in cgroup local storage(CVE-2025-38502)

    drm/sched: Increment job count before swapping tail spsc queue(CVE-2025-38515)

    pinctrl: qcom: msm: mark certain pins as invalid for interrupts(CVE-2025-38516)

    HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras(CVE-2025-38540)

    net/sched: Restrict conditions for adding duplicating netems to qdisc tree(CVE-2025-38553)

    crypto: ccp - Fix crash when rebind ccp device for ccp.ko(CVE-2025-38581)

    padata: Fix pd UAF once and for all(CVE-2025-38584)

    net: drop UFO packets in udp_rcv_segment()(CVE-2025-38622)

    regulator: core: fix NULL dereference on unbind due to stale coupling data(CVE-2025-38668)

    media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format()(CVE-2025-38680)

    fbdev: Fix vmalloc out-of-bounds write in fast_imageblit(CVE-2025-38685)

    media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and     w7090p_tuner_read_serpar(CVE-2025-38693)

    scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure(CVE-2025-38695)

    ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr(CVE-2025-38701)

    x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper(CVE-2025-39681)

    tracing: Limit access to parser-buffer when trace_get_user failed(CVE-2025-39683)

    ftrace: Also allocate and copy hash for reading of filter files(CVE-2025-39689)

    fs/buffer: fix use-after-free when call bh_read() helper(CVE-2025-39691)

    serial: 8250: fix panic due to PSLVERR(CVE-2025-39724)

    rcu: Fix rcu_read_unlock() deadloop due to IRQ work(CVE-2025-39744)

    rcu: Protect -defer_qs_iw_pending from data race(CVE-2025-39749)

    usb: core: config: Prevent OOB read in SS endpoint companion parsing(CVE-2025-39760)

    jbd2: prevent softlockup in jbd2_log_do_checkpoint()(CVE-2025-39782)

    ftrace: Fix potential warning in trace_printk_seq during ftrace_dump(CVE-2025-39813)

    trace/fgraph: Fix the warning caused by missing unregister notifier(CVE-2025-39829)

    vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects(CVE-2025-39850)

    vxlan: Fix NPD when refreshing an FDB entry with a nexthop object(CVE-2025-39851)

    tee: fix NULL pointer dereference in tee_shm_put(CVE-2025-39865)

    fs: writeback: fix use-after-free in __mark_inode_dirty()(CVE-2025-39866)

    cgroup: split cgroup_destroy_wq into 3 workqueues(CVE-2025-39953)

    fbcon: fix integer overflow in fbcon_do_set_font(CVE-2025-39967)

    i40e: add max boundary check for VF filters(CVE-2025-39968)

    i40e: fix idx validation in config queues msg(CVE-2025-39971)

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

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 CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1778756832 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Fix out-of-bound     read in resp_readcap16() The following warning was observed running syzkaller: [ 3813.830724] sg_write:
    data in/out 65466/242 bytes for SCSI command 0x9e-- guessing data in; [ 3813.830724] program syz-executor     not setting count and/or reply_len properly [ 3813.836956]     ================================================================== [ 3813.839465] BUG: KASAN: stack-out-     of-bounds in sg_copy_buffer+0x157/0x1e0 [ 3813.841773] Read of size 4096 at addr ffff8883cf80f540 by task     syz-executor/1549 [ 3813.846612] Call Trace: [ 3813.846995] dump_stack+0x108/0x15f [ 3813.847524]     print_address_description+0xa5/0x372 [ 3813.848243] kasan_report.cold+0x236/0x2a8 [ 3813.849439]     check_memory_region+0x240/0x270 [ 3813.850094] memcpy+0x30/0x80 [ 3813.850553] sg_copy_buffer+0x157/0x1e0     [ 3813.853032] sg_copy_from_buffer+0x13/0x20 [ 3813.853660] fill_from_dev_buffer+0x135/0x370 [     3813.854329] resp_readcap16+0x1ac/0x280 [ 3813.856917] schedule_resp+0x41f/0x1630 [ 3813.858203]     scsi_debug_queuecommand+0xb32/0x17e0 [ 3813.862699] scsi_dispatch_cmd+0x330/0x950 [ 3813.863329]     scsi_request_fn+0xd8e/0x1710 [ 3813.863946] __blk_run_queue+0x10b/0x230 [ 3813.864544]     blk_execute_rq_nowait+0x1d8/0x400 [ 3813.865220] sg_common_write.isra.0+0xe61/0x2420 [ 3813.871637]     sg_write+0x6c8/0xef0 [ 3813.878853] __vfs_write+0xe4/0x800 [ 3813.883487] vfs_write+0x17b/0x530 [     3813.884008] ksys_write+0x103/0x270 [ 3813.886268] __x64_sys_write+0x77/0xc0 [ 3813.886841]     do_syscall_64+0x106/0x360 [ 3813.887415] entry_SYSCALL_64_after_hwframe+0x44/0xa9 This issue can be     reproduced with the following syzkaller log: r0 = openat(0xffffffffffffff9c,     &(0x7f0000000040)='./file0\x00', 0x26e1, 0x0) r1 = syz_open_procfs(0xffffffffffffffff,     &(0x7f0000000000)='fd/3\x00') open_by_handle_at(r1, &(0x7f00000003c0)=ANY=[@ANYRESHEX], 0x602000) r2 =     syz_open_dev$sg(&(0x7f0000000000), 0x0, 0x40782) write$binfmt_aout(r2, &(0x7f0000000340)=ANY=[@ANYBLOB=00     000000deff000000000000000000000000000000000000000000000000000047f007af9e107a41ec395f1bded7be24277a1501ff61     96a83366f4e6362bc0ff2b247f68a972989b094b2da4fb3607fcf611a22dd04310d28c75039d], 0x126) In resp_readcap16()     we get int alloc_len value -1104926854, and then pass the huge arr_len to fill_from_dev_buffer(), but     arr is only 32 bytes. This leads to OOB in sg_copy_buffer(). To solve this issue, define alloc_len as u32.
    (CVE-2021-47191)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Fix out-of-bound     read in resp_report_tgtpgs() The following issue was observed running syzkaller: BUG: KASAN: slab-out-of-     bounds in memcpy include/linux/string.h:377 [inline] BUG: KASAN: slab-out-of-bounds in     sg_copy_buffer+0x150/0x1c0 lib/scatterlist.c:831 Read of size 2132 at addr ffff8880aea95dc8 by task syz-     executor.0/9815 CPU: 0 PID: 9815 Comm: syz-executor.0 Not tainted 4.19.202-00874-gfc0fe04215a9 #2 Hardware     name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 Call Trace: __dump_stack     lib/dump_stack.c:77 [inline] dump_stack+0xe4/0x14a lib/dump_stack.c:118     print_address_description+0x73/0x280 mm/kasan/report.c:253 kasan_report_error mm/kasan/report.c:352     [inline] kasan_report+0x272/0x370 mm/kasan/report.c:410 memcpy+0x1f/0x50 mm/kasan/kasan.c:302 memcpy     include/linux/string.h:377 [inline] sg_copy_buffer+0x150/0x1c0 lib/scatterlist.c:831     fill_from_dev_buffer+0x14f/0x340 drivers/scsi/scsi_debug.c:1021 resp_report_tgtpgs+0x5aa/0x770     drivers/scsi/scsi_debug.c:1772 schedule_resp+0x464/0x12f0 drivers/scsi/scsi_debug.c:4429     scsi_debug_queuecommand+0x467/0x1390 drivers/scsi/scsi_debug.c:5835 scsi_dispatch_cmd+0x3fc/0x9b0     drivers/scsi/scsi_lib.c:1896 scsi_request_fn+0x1042/0x1810 drivers/scsi/scsi_lib.c:2034
    __blk_run_queue_uncond block/blk-core.c:464 [inline] __blk_run_queue+0x1a4/0x380 block/blk-core.c:484     blk_execute_rq_nowait+0x1c2/0x2d0 block/blk-exec.c:78 sg_common_write.isra.19+0xd74/0x1dc0     drivers/scsi/sg.c:847 sg_write.part.23+0x6e0/0xd00 drivers/scsi/sg.c:716 sg_write+0x64/0xa0     drivers/scsi/sg.c:622 __vfs_write+0xed/0x690 fs/read_write.c:485 kill_bdev:block_device:00000000e138492c     vfs_write+0x184/0x4c0 fs/read_write.c:549 ksys_write+0x107/0x240 fs/read_write.c:599     do_syscall_64+0xc2/0x560 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe We get     'alen' from command its type is int. If userspace passes a large length we will get a negative 'alen'.
    Switch n, alen, and rlen to u32. (CVE-2021-47219)

  - In the Linux kernel, the following vulnerability has been resolved: kvm: avoid speculation-based attacks     from out-of-range memslot accesses KVM's mechanism for accessing guest memory translates a guest physical     address (gpa) to a host virtual address using the right-shifted gpa (also known as gfn) and a struct     kvm_memory_slot. The translation is performed in __gfn_to_hva_memslot using the following formula: hva =     slot->userspace_addr + (gfn - slot->base_gfn) * PAGE_SIZE It is expected that gfn falls within the     boundaries of the guest's physical memory. However, a guest can access invalid physical addresses in such     a way that the gfn is invalid. __gfn_to_hva_memslot is called from kvm_vcpu_gfn_to_hva_prot, which first     retrieves a memslot through __gfn_to_memslot. While __gfn_to_memslot does check that the gfn falls within     the boundaries of the guest's physical memory or not, a CPU can speculate the result of the check and     continue execution speculatively using an illegal gfn. The speculation can result in calculating an out-     of-bounds hva. If the resulting host virtual address is used to load another guest physical address, this     is effectively a Spectre gadget consisting of two consecutive reads, the second of which is data dependent     on the first. Right now it's not clear if there are any cases in which this is exploitable. One     interesting case was reported by the original author of this patch, and involves visiting guest page     tables on x86. Right now these are not vulnerable because the hva read goes through get_user(), which     contains an LFENCE speculation barrier. However, there are patches in progress for x86 uaccess.h to mask     kernel addresses instead of using LFENCE; once these land, a guest could use speculation to read from the     VMM's ring 3 address space. Other architectures such as ARM already use the address masking method, and     would be susceptible to this same kind of data-dependent access gadgets. Therefore, this patch proactively     protects from these attacks by masking out-of-bounds gfns in __gfn_to_hva_memslot, which blocks     speculation of invalid hvas. Sean Christopherson noted that this patch does not cover     kvm_read_guest_offset_cached. This however is limited to a few bytes past the end of the cache, and     therefore it is unlikely to be useful in the context of building a chain of data dependent accesses.
    (CVE-2021-47277)

  - In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: make apf token non-zero     to fix bug In current async pagefault logic, when a page is ready, KVM relies on     kvm_arch_can_dequeue_async_page_present() to determine whether to deliver a READY event to the Guest. This     function test token value of struct kvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when     a READY event is finished by Guest. If value is zero meaning that a READY event is done, so the KVM can     deliver another. But the kvm_arch_setup_async_pf() may produce a valid token with zero value, which is     confused with previous mention and may lead the loss of this READY event. This bug may cause task blocked     forever in Guest: INFO: task stress:7532 blocked for more than 1254 seconds. Not tainted 5.10.0 #16 echo     0 > /proc/sys/kernel/hung_task_timeout_secs disables this message. task:stress state:D stack: 0 pid: 7532     ppid: 1409 flags:0x00000080 Call Trace: __schedule+0x1e7/0x650 schedule+0x46/0xb0     kvm_async_pf_task_wait_schedule+0xad/0xe0 ? exit_to_user_mode_prepare+0x60/0x70
    __kvm_handle_async_pf+0x4f/0xb0 ? asm_exc_page_fault+0x8/0x30 exc_page_fault+0x6f/0x110 ?     asm_exc_page_fault+0x8/0x30 asm_exc_page_fault+0x1e/0x30 RIP: 0033:0x402d00 RSP: 002b:00007ffd31912500     EFLAGS: 00010206 RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0 RDX: 000000000007d011     RSI: 000000000007d000 RDI: 00000000021262b0 RBP: 00000000021262b0 R08: 0000000000000003 R09:
    0000000000000086 R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000 R13: 0000000000000002     R14: 000000000007d000 R15: 0000000000001000 (CVE-2022-48943)

  - In the Linux kernel, the following vulnerability has been resolved: ipv6: addrlabel: fix infoleak when     sending struct ifaddrlblmsg to network When copying a `struct ifaddrlblmsg` to the network,
    __ifal_reserved remained uninitialized, resulting in a 1-byte infoleak: BUG: KMSAN: kernel-network-     infoleak in __netdev_start_xmit ./include/linux/netdevice.h:4841 __netdev_start_xmit     ./include/linux/netdevice.h:4841 netdev_start_xmit ./include/linux/netdevice.h:4857 xmit_one     net/core/dev.c:3590 dev_hard_start_xmit+0x1dc/0x800 net/core/dev.c:3606 __dev_queue_xmit+0x17e8/0x4350     net/core/dev.c:4256 dev_queue_xmit ./include/linux/netdevice.h:3009 __netlink_deliver_tap_skb     net/netlink/af_netlink.c:307 __netlink_deliver_tap+0x728/0xad0 net/netlink/af_netlink.c:325     netlink_deliver_tap net/netlink/af_netlink.c:338 __netlink_sendskb net/netlink/af_netlink.c:1263     netlink_sendskb+0x1d9/0x200 net/netlink/af_netlink.c:1272 netlink_unicast+0x56d/0xf50     net/netlink/af_netlink.c:1360 nlmsg_unicast ./include/net/netlink.h:1061 rtnl_unicast+0x5a/0x80     net/core/rtnetlink.c:758 ip6addrlbl_get+0xfad/0x10f0 net/ipv6/addrlabel.c:628     rtnetlink_rcv_msg+0xb33/0x1570 net/core/rtnetlink.c:6082 ... Uninit was created at:
    slab_post_alloc_hook+0x118/0xb00 mm/slab.h:742 slab_alloc_node mm/slub.c:3398
    __kmem_cache_alloc_node+0x4f2/0x930 mm/slub.c:3437 __do_kmalloc_node mm/slab_common.c:954
    __kmalloc_node_track_caller+0x117/0x3d0 mm/slab_common.c:975 kmalloc_reserve net/core/skbuff.c:437
    __alloc_skb+0x27a/0xab0 net/core/skbuff.c:509 alloc_skb ./include/linux/skbuff.h:1267 nlmsg_new     ./include/net/netlink.h:964 ip6addrlbl_get+0x490/0x10f0 net/ipv6/addrlabel.c:608     rtnetlink_rcv_msg+0xb33/0x1570 net/core/rtnetlink.c:6082 netlink_rcv_skb+0x299/0x550     net/netlink/af_netlink.c:2540 rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:6109 netlink_unicast_kernel     net/netlink/af_netlink.c:1319 netlink_unicast+0x9ab/0xf50 net/netlink/af_netlink.c:1345     netlink_sendmsg+0xebc/0x10f0 net/netlink/af_netlink.c:1921 ... This patch ensures that the reserved field     is always initialized. (CVE-2022-49865)

Note that Nessus has not tested for these issues 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-184 advisory.

    There is a potential deadlock in the eBPF subsystem in the Linux kernel.

    The default sysctl configuration kernel.unprivileged_bpf_disabled on Amazon Linux does not allow     unprivileged users to use eBPF. (CVE-2023-0160)

    A denial of service problem was found, due to a possible recursive locking scenario, resulting in a     deadlock in table_clear in drivers/md/dm-ioctl.c in the Linux Kernel Device Mapper-Multipathing sub-     component. (CVE-2023-2269)

    In the Linux kernel through 6.3.1, a use-after-free in Netfilter nf_tables when processing batch requests     can be abused to perform arbitrary read and write operations on kernel memory. Unprivileged local users     can obtain root privileges. This occurs because anonymous sets are mishandled. (CVE-2023-32233)

    An issue was discovered in the Linux kernel before 6.3.3. There is an out-of-bounds read in crc16 in     lib/crc16.c when called from fs/ext4/super.c because ext4_group_desc_csum does not properly check an     offset. (CVE-2023-34256)

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

    ext4: fix i_disksize exceeding i_size problem in paritally written case (CVE-2023-53270)

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

    ext4: add bounds checking in get_max_inline_xattr_value_size() (CVE-2023-53285)

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

    fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup() (CVE-2023-53294)

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

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

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

    ext4: fix WARNING in mb_find_extent (CVE-2023-53317)

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

    ext4: remove a BUG_ON in ext4_mb_release_group_pa() (CVE-2023-53450)

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

    ext4: improve error handling from ext4_dirhash() (CVE-2023-53473)

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

    x86/MCE/AMD: Use an u64 for bank_map (CVE-2023-53474)

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

    tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp. (CVE-2023-53489)

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

    blk-crypto: make blk_crypto_evict_key() more robust (CVE-2023-53536)

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

    drm/i915: Make intel_get_crtc_new_encoder() less oopsy (CVE-2023-53571)

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

    scsi: target: Fix multiple LUN_RESET handling (CVE-2023-53586)

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

    ring-buffer: Sync IRQ works before buffer destruction (CVE-2023-53587)

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

    dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path (CVE-2023-53604)

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

    net/sched: sch_fq: fix integer overflow of credit (CVE-2023-53624)

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

    netfilter: conntrack: fix wrong ct->timeout value (CVE-2023-53635)

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

    x86: fix clear_user_rep_good() exception handling annotation (CVE-2023-53642)

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

    rcu: Avoid stack overflow due to __rcu_irq_enter_check_tick() being kprobe-ed (CVE-2023-53655)

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

    tcp: fix skb_copy_ubufs() vs BIG TCP (CVE-2023-53669)

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

    ext4: fix use-after-free read in ext4_find_extent for bigalloc + inline (CVE-2023-53692)

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

    x86: fix clear_user_rep_good() exception handling annotation (CVE-2023-53749)

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

    cifs: fix potential use-after-free bugs in TCP_Server_Info::hostname (CVE-2023-53751)

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

    virt/coco/sev-guest: Double-buffer messages (CVE-2023-53769)

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

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

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

    ethtool: Fix uninitialized number of lanes (CVE-2023-53798)

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

    blk-mq: release crypto keyslot before reporting I/O complete (CVE-2023-53810)

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

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

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

    ceph: fix potential use-after-free bug when trimming caps (CVE-2023-53867)

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

    fs/ntfs3: Fix slab-out-of-bounds read in hdr_delete_de() (CVE-2023-53988)

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

    SMB3: Add missing locks to protect deferred close file list (CVE-2023-53990)

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

    btrfs: fix assertion of exclop condition when starting balance (CVE-2023-54002)

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

    vmci_host: fix a race condition in vmci_host_poll() causing GPF (CVE-2023-54007)

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

    spmi: Add a check for remove callback when removing a SPMI driver (CVE-2023-54044)

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

    kheaders: Use array declaration instead of char (CVE-2023-54056)

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

    ext4: fix invalid free tracking in ext4_xattr_move_to_block() (CVE-2023-54062)

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

    fs/ntfs3: Fix OOB read in indx_insert_into_buffer (CVE-2023-54063)

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

    tpm: Add !tpm_amd_is_rng_defective() to the hwrng_unregister() call site (CVE-2023-54073)

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

    fs/ntfs3: Fix memory leak if ntfs_read_mft failed (CVE-2023-54077)

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

    inotify: Avoid reporting event with invalid wd (CVE-2023-54119)

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

    md/raid10: fix memleak for 'conf->bio_split' (CVE-2023-54123)

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

    btrfs: don't free qgroup space unless specified (CVE-2023-54158)

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

    net/sched: cls_api: remove block_cb from driver_list before freeing (CVE-2023-54193)

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

    fs/ntfs3: Add check for kmemdup (CVE-2023-54248)

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

    md/raid10: fix memleak of md thread (CVE-2023-54294)

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

    ext4: fix deadlock when converting an inline directory in nojournal mode (CVE-2023-54311)

    A use-after-free flaw was found in the __ext4_remount in fs/ext4/super.c in ext4 in the Linux kernel. This     flaw allows a local user to cause an information leak problem while freeing the old quota file names     before a potential failure, leading to a use-after-free. (CVE-2024-0775)

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.

The version of kernel installed on the remote host is prior to 5.4.247-161.349. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2023-047 advisory.

    A flaw was found in the x86 KVM subsystem in kvm_steal_time_set_preempted in arch/x86/kvm/x86.c in the     Linux kernel. Unprivileged guest users can compromise the guest kernel because TLB flush operations are     mishandled in certain KVM_VCPU_PREEMPTED situations. (CVE-2022-39189)

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

    btrfs: unset reloc control if transaction commit fails in prepare_to_relocate() (CVE-2022-50067)

    There is a potential deadlock in the eBPF subsystem in the Linux kernel.

    The default sysctl configuration kernel.unprivileged_bpf_disabled on Amazon Linux does not allow     unprivileged users to use eBPF. (CVE-2023-0160)

    A denial of service problem was found, due to a possible recursive locking scenario, resulting in a     deadlock in table_clear in drivers/md/dm-ioctl.c in the Linux Kernel Device Mapper-Multipathing sub-     component. (CVE-2023-2269)

    A heap out-of-bounds write vulnerability in the Linux Kernel ipvlan network driver can be exploited to     achieve local privilege escalation.

    The out-of-bounds write is caused by missing skb->cb  initialization in the ipvlan network driver. The     vulnerability is reachable if CONFIG_IPVLAN is enabled.

    We recommend upgrading past commit 90cbed5247439a966b645b34eb0a2e037836ea8e. (CVE-2023-3090)

    A use after free vulnerability was found in prepare_to_relocate in fs/btrfs/relocation.c in btrfs in the     Linux Kernel. This possible flaw can be triggered by calling btrfs_ioctl_balance() before calling     btrfs_ioctl_defrag(). (CVE-2023-3111)

    A use-after-free flaw was found in r592_remove in drivers/memstick/host/r592.c in media access in the     Linux Kernel. This flaw allows a local attacker to crash the system at device disconnect, possibly leading     to a kernel information leak. (CVE-2023-3141)

    An out of bounds (OOB) memory access flaw was found in the Linux kernel in relay_file_read_start_pos in     kernel/relay.c in the relayfs. This flaw could allow a local attacker to crash the system or leak kernel     internal information. (CVE-2023-3268)

    An issue was discovered in the Linux kernel before 6.3.3. There is an out-of-bounds read in crc16 in     lib/crc16.c when called from fs/ext4/super.c because ext4_group_desc_csum does not properly check an     offset. (CVE-2023-34256)

    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 fl_set_geneve_opt in net/sched/cls_flower.c in the Linux kernel before 6.3.7.
    It allows an out-of-bounds write in the flower classifier code via TCA_FLOWER_KEY_ENC_OPTS_GENEVE packets.
    This may result in denial of service or privilege escalation. (CVE-2023-35788)

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

    serial: 8250: Reinit port->pm on port specific driver unbind (CVE-2023-53176)

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

    ACPICA: Avoid undefined behavior: applying zero offset to null pointer (CVE-2023-53182)

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

    ext4: add bounds checking in get_max_inline_xattr_value_size() (CVE-2023-53285)

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

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

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

    ext4: fix WARNING in mb_find_extent (CVE-2023-53317)

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

    nilfs2: do not write dirty data after degenerating to read-only (CVE-2023-53337)

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

    net: add vlan_get_protocol_and_depth() helper (CVE-2023-53433)

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

    ext4: remove a BUG_ON in ext4_mb_release_group_pa() (CVE-2023-53450)

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

    lib: cpu_rmap: Avoid use after free on rmap->obj array entries (CVE-2023-53484)

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

    tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp. (CVE-2023-53489)

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

    spi: qup: Don't skip cleanup in remove's error path (CVE-2023-53567)

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

    ext2: Check block size validity during mount (CVE-2023-53569)

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

    ring-buffer: Sync IRQ works before buffer destruction (CVE-2023-53587)

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

    dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path (CVE-2023-53604)

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

    net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize (CVE-2023-53667)

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

    fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode() (CVE-2023-53683)

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

    ext4: fix use-after-free read in ext4_find_extent for bigalloc + inline (CVE-2023-53692)

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

    ipv6: Fix out-of-bounds access in ipv6_find_tlv() (CVE-2023-53705)

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

    serial: arc_uart: fix of_iomap leak in `arc_serial_probe` (CVE-2023-53719)

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

    vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF (CVE-2023-53747)

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

    scsi: lpfc: Fix ioremap issues in lpfc_sli4_pci_mem_setup() (CVE-2023-53754)

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

    USB: usbtmc: Fix direction for 0-length ioctl control messages (CVE-2023-53761)

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

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

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

    nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode() (CVE-2023-53804)

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

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

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

    nilfs2: fix infinite loop in nilfs_mdt_get_block() (CVE-2023-53845)

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

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

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

    udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated(). (CVE-2023-54004)

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

    vmci_host: fix a race condition in vmci_host_poll() causing GPF (CVE-2023-54007)

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

    net: fix stack overflow when LRO is disabled for virtual interfaces (CVE-2023-54012)

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

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

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

    ext4: set goal start correctly in ext4_mb_normalize_request (CVE-2023-54021)

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

    spmi: Add a check for remove callback when removing a SPMI driver (CVE-2023-54044)

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

    kheaders: Use array declaration instead of char (CVE-2023-54056)

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

    ext4: fix invalid free tracking in ext4_xattr_move_to_block() (CVE-2023-54062)

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

    scsi: lpfc: Prevent lpfc_debugfs_lockstat_write() buffer overflow (CVE-2023-54102)

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

    net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (CVE-2023-54114)

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

    inotify: Avoid reporting event with invalid wd (CVE-2023-54119)

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

    md/raid10: fix memleak for 'conf->bio_split' (CVE-2023-54123)

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

    btrfs: don't free qgroup space unless specified (CVE-2023-54158)

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

    firmware: arm_sdei: Fix sleep from invalid context BUG (CVE-2023-54160)

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

    RDMA/mlx4: Prevent shift wrapping in set_user_sq_size() (CVE-2023-54168)

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

    scsi: target: iscsit: Free cmds before session free (CVE-2023-54184)

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

    net/sched: cls_api: remove block_cb from driver_list before freeing (CVE-2023-54193)

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

    USB: sisusbvga: Add endpoint checks (CVE-2023-54213)

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

    net: Fix load-tearing on sk->sk_stamp in sock_recv_cmsgs(). (CVE-2023-54218)

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

    af_unix: Fix data races around sk->sk_shutdown. (CVE-2023-54226)

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

    ACPI: EC: Fix oops when removing custom query handlers (CVE-2023-54244)

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

    debugobjects: Don't wake up kswapd from fill_pool() (CVE-2023-54268)

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

    md/raid10: fix memleak of md thread (CVE-2023-54294)

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

    ext4: fix deadlock when converting an inline directory in nojournal mode (CVE-2023-54311)

    A use-after-free flaw was found in the __ext4_remount in fs/ext4/super.c in ext4 in the Linux kernel. This     flaw allows a local user to cause an information leak problem while freeing the old quota file names     before a potential failure, leading to a use-after-free. (CVE-2024-0775)

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 CentOS Linux 8.4 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.4:CLSA-2026:1773048865 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Avoid field-overflowing     memcpy() In preparation for FORTIFY_SOURCE performing compile-time and run-time field bounds checking for     memcpy(), memmove(), and memset(), avoid intentionally writing across neighboring fields. Use flexible     arrays instead of zero-element arrays (which look like they are always overflowing) and split the cross-     field memcpy() into two halves that can be appropriately bounds-checked by the compiler. We were doing:
    #define ETH_HLEN 14 #define VLAN_HLEN 4 ... #define MLX5E_XDP_MIN_INLINE (ETH_HLEN + VLAN_HLEN) ... struct     mlx5e_tx_wqe *wqe = mlx5_wq_cyc_get_wqe(wq, pi); ... struct mlx5_wqe_eth_seg *eseg = &wqe->eth; struct     mlx5_wqe_data_seg *dseg = wqe->data; ... memcpy(eseg->inline_hdr.start, xdptxd->data,     MLX5E_XDP_MIN_INLINE); target is wqe->eth.inline_hdr.start (which the compiler sees as being 2 bytes in     size), but copying 18, intending to write across start (really vlan_tci, 2 bytes). The remaining 16 bytes     get written into wqe->data[0], covering byte_count (4 bytes), lkey (4 bytes), and addr (8 bytes). struct     mlx5e_tx_wqe { struct mlx5_wqe_ctrl_seg ctrl; /* 0 16 */ struct mlx5_wqe_eth_seg eth; /* 16 16 */ struct     mlx5_wqe_data_seg data[]; /* 32 0 */ /* size: 32, cachelines: 1, members: 3 */ /* last cacheline: 32 bytes
    */ }; struct mlx5_wqe_eth_seg { u8 swp_outer_l4_offset; /* 0 1 */ u8 swp_outer_l3_offset; /* 1 1 */ u8     swp_inner_l4_offset; /* 2 1 */ u8 swp_inner_l3_offset; /* 3 1 */ u8 cs_flags; /* 4 1 */ u8 swp_flags; /* 5     1 */ __be16 mss; /* 6 2 */ __be32 flow_table_metadata; /* 8 4 */ union { struct { __be16 sz; /* 12 2 */ u8     start[2]; /* 14 2 */ } inline_hdr; /* 12 4 */ struct { __be16 type; /* 12 2 */ __be16 vlan_tci; /* 14 2 */     } insert; /* 12 4 */ __be32 trailer; /* 12 4 */ }; /* 12 4 */ /* size: 16, cachelines: 1, members: 9 */ /*     last cacheline: 16 bytes */ }; struct mlx5_wqe_data_seg { __be32 byte_count; /* 0 4 */ __be32 lkey; /* 4 4
    */ __be64 addr; /* 8 8 */ /* size: 16, cachelines: 1, members: 3 */ /* last cacheline: 16 bytes */ }; So,     split the memcpy() so the compiler can reason about the buffer sizes. pahole shows no size nor member     offset changes to struct mlx5e_tx_wqe nor struct mlx5e_umr_wqe. objdump -d shows no meaningful object     code changes (i.e. only source line number induced differences and optimizations). (CVE-2022-48744)

  - In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix the behavior of READ near     OFFSET_MAX Dan Aloni reports: > Due to commit 8cfb9015280d (NFS: Always provide aligned buffers to > the     RPC read layers) on the client, a read of 0xfff is aligned up > to server rsize of 0x1000. > > As a     result, in a test where the server has a file of size > 0x7fffffffffffffff, and the client tries to read     from the offset > 0x7ffffffffffff000, the read causes loff_t overflow in the server > and it returns an     NFS code of EINVAL to the client. The client as > a result indefinitely retries the request. The Linux NFS     client does not handle NFS?ERR_INVAL, even though all NFS specifications permit servers to return that     status code for a READ. Instead of NFS?ERR_INVAL, have out-of-range READ requests succeed and return a     short result. Set the EOF flag in the result to prevent the client from retrying the READ request. This     behavior appears to be consistent with Solaris NFS servers. Note that NFSv3 and NFSv4 use u64 offset     values on the wire. These must be converted to loff_t internally before use -- an implicit type cast is     not adequate for this purpose. Otherwise VFS checks against sb->s_maxbytes do not work properly.
    (CVE-2022-48827)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix user-after-free     This uses l2cap_chan_hold_unless_zero() after calling __l2cap_get_chan_blah() to prevent the following     trace: Bluetooth: l2cap_core.c:static void l2cap_chan_destroy(struct kref *kref) Bluetooth: chan     0000000023c4974d Bluetooth: parent 00000000ae861c08     ================================================================== BUG: KASAN: use-after-free in
    __mutex_waiter_is_first kernel/locking/mutex.c:191 [inline] BUG: KASAN: use-after-free in
    __mutex_lock_common kernel/locking/mutex.c:671 [inline] BUG: KASAN: use-after-free in
    __mutex_lock+0x278/0x400 kernel/locking/mutex.c:729 Read of size 8 at addr ffff888006a49b08 by task     kworker/u3:2/389 (CVE-2022-50386)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: libsas: Fix use-after-free bug     in smp_execute_task_sg() When executing SMP task failed, the smp_execute_task_sg() calls del_timer() to     delete slow_task->timer. However, if the timer handler sas_task_internal_timedout() is running, the     del_timer() in smp_execute_task_sg() will not stop it and a UAF will happen. The process is shown below:
    (thread 1) | (thread 2) smp_execute_task_sg() | sas_task_internal_timedout() ... | del_timer() | ... | ...
    sas_free_task(task) | kfree(task->slow_task) //FREE| | task->slow_task->... //USE Fix by calling     del_timer_sync() in smp_execute_task_sg(), which makes sure the timer handler have finished before the     task->slow_task is deallocated. (CVE-2022-50422)

  - In the Linux kernel, the following vulnerability has been resolved: kernfs: fix use-after-free in
    __kernfs_remove Syzkaller managed to trigger concurrent calls to kernfs_remove_by_name_ns() for the same     file resulting in a KASAN detected use-after-free. The race occurs when the root node is freed during     kernfs_drain(). To prevent this acquire an additional reference for the root of the tree that is removed     before calling __kernfs_remove(). Found by syzkaller with the following reproducer (slab_nomerge is     required): syz_mount_image$ext4(0x0, &(0x7f0000000100)='./file0\x00', 0x100000, 0x0, 0x0, 0x0, 0x0) r0 =     openat(0xffffffffffffff9c, &(0x7f0000000080)='/proc/self/exe\x00', 0x0, 0x0) close(r0)     pipe2(&(0x7f0000000140)={0xffffffffffffffff, <r1=>0xffffffffffffffff}, 0x800) mount$9p_fd(0x0,     &(0x7f0000000040)='./file0\x00', &(0x7f00000000c0), 0x408, &(0x7f0000000280)={'trans=fd,', {'rfdno', 0x3d,     r0}, 0x2c, {'wfdno', 0x3d, r1}, 0x2c, {[{@cache_loose}, {@mmap}, {@loose}, {@loose}, {@mmap}],     [{@mask={'mask', 0x3d, '^MAY_EXEC'}}, {@fsmagic={'fsmagic', 0x3d, 0x10001}}, {@dont_hash}]}}) Sample     report: ================================================================== BUG: KASAN: use-after-free in     kernfs_type include/linux/kernfs.h:335 [inline] BUG: KASAN: use-after-free in kernfs_leftmost_descendant     fs/kernfs/dir.c:1261 [inline] BUG: KASAN: use-after-free in __kernfs_remove.part.0+0x843/0x960     fs/kernfs/dir.c:1369 Read of size 2 at addr ffff8880088807f0 by task syz-executor.2/857 CPU: 0 PID: 857     Comm: syz-executor.2 Not tainted 6.0.0-rc3-00363-g7726d4c3e60b #5 Hardware name: QEMU Standard PC (i440FX     + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline]     dump_stack_lvl+0x6e/0x91 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:317 [inline]     print_report.cold+0x5e/0x5e5 mm/kasan/report.c:433 kasan_report+0xa3/0x130 mm/kasan/report.c:495     kernfs_type include/linux/kernfs.h:335 [inline] kernfs_leftmost_descendant fs/kernfs/dir.c:1261 [inline]
    __kernfs_remove.part.0+0x843/0x960 fs/kernfs/dir.c:1369 __kernfs_remove fs/kernfs/dir.c:1356 [inline]     kernfs_remove_by_name_ns+0x108/0x190 fs/kernfs/dir.c:1589 sysfs_slab_add+0x133/0x1e0 mm/slub.c:5943
    __kmem_cache_create+0x3e0/0x550 mm/slub.c:4899 create_cache mm/slab_common.c:229 [inline]     kmem_cache_create_usercopy+0x167/0x2a0 mm/slab_common.c:335 p9_client_create+0xd4d/0x1190     net/9p/client.c:993 v9fs_session_init+0x1e6/0x13c0 fs/9p/v9fs.c:408 v9fs_mount+0xb9/0xbd0     fs/9p/vfs_super.c:126 legacy_get_tree+0xf1/0x200 fs/fs_context.c:610 vfs_get_tree+0x85/0x2e0     fs/super.c:1530 do_new_mount fs/namespace.c:3040 [inline] path_mount+0x675/0x1d00 fs/namespace.c:3370     do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount     fs/namespace.c:3568 [inline] __x64_sys_mount+0x282/0x300 fs/namespace.c:3568 do_syscall_x64     arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0x90 arch/x86/entry/common.c:80     entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f725f983aed Code: 02 b8 ff ff ff ff c3 66 0f 1f 44     00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0     ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f725f0f7028 EFLAGS: 00000246     ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007f725faa3f80 RCX: 00007f725f983aed RDX:
    00000000200000c0 RSI: 0000000020000040 RDI: 0000000000000000 RBP: 00007f725f9f419c R08: 0000000020000280     R09: 0000000000000000 R10: 0000000000000408 R11: 0000000000000246 R12: 0000000000000000 R13:
    0000000000000006 R14: 00007f725faa3f80 R15: 00007f725f0d7000 </TASK> Allocated by task 855:
    kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38 kasan_set_track mm/kasan/common.c:45 [inline]     set_alloc_info mm/kasan/common.c:437 [inline] __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:470     kasan_slab_alloc include/linux/kasan.h:224 [inline] slab_post_alloc_hook mm/slab.h:7 ---truncated---     (CVE-2022-50432)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
352841	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1778276927)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/22	high
276910	SUSE SLES12: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:4189-1)	Nessus	SuSE Local Security Checks	2025/11/26	2026/6/25	high
281563	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2025-2623)	Nessus	Huawei Local Security Checks	2025/12/31	2026/3/6	high
352370	CentOS Linux 8.5 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.5:CLSA-2026:1773047921)	Nessus	CentOS Local Security Checks	2026/9/30	2026/9/30	high
278473	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2522)	Nessus	Huawei Local Security Checks	2025/12/11	2026/3/6	high
281579	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2025-2609)	Nessus	Huawei Local Security Checks	2025/12/31	2026/3/6	high
362062	CentOS Linux 7 [TuxCare] Security Update: bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1778756832)	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
176925	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2023-184)	Nessus	Amazon Linux Local Security Checks	2023/6/8	2026/2/12	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	2021/7/22	2026/11/2	high
177776	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2023-047 (ALASKERNEL-5.4-2023-047)	Nessus	Amazon Linux Local Security Checks	2023/6/29	2026/2/11	high
361020	CentOS Linux 8.4 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.4:CLSA-2026:1773048865)	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high