远程 Redhat Enterprise Linux 9 主机上安装的多个程序包受到 RHSA-2023:6583 公告中提及的多个漏洞影响。

  - 内核：内存管理器中设备私有页面发生故障时，出现争用 (CVE-2022-3523)

  - kernel：l1oip 计时器处理程序中的释放后使用 (CVE-2022-3565)

  - 内核：intr_callback 的 r8152 中存在速率限制溢出消息 (CVE-2022-3594)

  - 内核：vmwgfx：vmw_cmd_res_check 中存在释放后使用漏洞 (CVE-2022-38457)

  - 内核：vmwgfx：vmw_execbuf_tie_context 中存在释放后使用漏洞 (CVE-2022-40133)

  - hw: Intel：收集数据采样 (GDS) 边信道漏洞 (CVE-2022-40982)

  - 内核：net/bluetooth/l2cap_core.c 的 l2cap_parse_conf_req 中存在信息泄漏漏洞 (CVE-2022-42895)

  - kernel: x86/mm：随机化 per-cpu 条目区域 (CVE-2023-0597)

  - kernel: HID：检查 hid_validate_values() 中空的 report_list (CVE-2023-1073)

  - kernel: sctp：如果给定范围内没有可以使用的绑定地址，则失败 (CVE-2023-1074)

  - kernel: net/tls：tls_is_tx_ready() 检查了 list_entry (CVE-2023-1075)

  - kernel: tap: tap_open()：正确初始化套接字 uid (CVE-2023-1076)

  - kernel: hid：asus_remove() 中的释放后使用 (CVE-2023-1079)

  - kernel：IPv6 连接查找表中的哈希冲突 (CVE-2023-1206)

  - kernel：file_files_note 中缺少 mmap_lock，可能导致 coredump 代码中出现释放后使用 (CVE-2023-1249)

  - kernel: ovl：修复 ovl_aio_req 结构中的释放后使用 (CVE-2023-1252)

  - Kernel：fs/nfsd/nfs4proc.c 中 nfsd4_ssc_setup_dul 中的释放后使用 (CVE-2023-1652)

  - kernel：删除函数 xgene_hwmon_remove 中的释放后使用缺陷 (CVE-2023-1855)

  - Kernel：由于争用条件，xen_9pfs_front_remove 中存在释放后使用 (CVE-2023-1989)

  - Kernel：dm- ioctl.c 的 dm_get_inactive_table 中可能存在死锁问题，进而导致 DOS (CVE-2023-2269)

  - kernel：r592_remove 中的释放后使用缺陷 (CVE-2023-3141)

  - kernel: fbcon：fbcon_set_font() 中的 shift 越界 (CVE-2023-3161)

  - kernel: gfs2：修复 gfs2_rgrp_dump 中的空指针取消引用漏洞 (CVE-2023-3212)

  - kernel：relay_file_read 中的越界访问 (CVE-2023-3268)

  - kernel：由于 shtp_cl_get_dma_send_buf() 中缺少 kalloc() 返回值检查，导致空指针取消引用 (CVE-2023-3358)

  - kernel：net/sched：如果 tcf_change_indev() 失败，cls_u32 组件引用计数器将会泄漏 (CVE-2023-3609)

  - kernel: xfrm：xfrm_update_ae_params() 中的空指针取消引用 (CVE-2023-3772)

  - kernel: xfrm：XFRMA_MTIMER_THRESH nlattr 发生越界读取 (CVE-2023-3773)

  - kernel：SEV-ES/SEV-SNP VMGEXIT 双重提取漏洞 (CVE-2023-4155)

   kernel: tap: tap_open()：正确初始化套接字 uid，再将 i_uid 修复为 current_fsuid (CVE-2023-4194)

  - kernel：net/sched：net/sched 分类器中存在释放后使用漏洞：cls_fw、cls_u32 和 cls_route（CVE-2023-4206、CVE-2023-4207、CVE-2023-4208）

  - kernel: exFAT：exfat_get_uniname_from_ext_entry 中的堆栈溢出（CVE-2023-4273）

  - kernel: mpls：sysctl 分配时的双重释放失败 (CVE-2023-26545)

  - 内核：KVM：nVMX：缺少对 CR0 和 CR4 的一致性检查 (CVE-2023-30456)

  - kernel：net: qcom/emac: 争用条件导致 emac_remove() 中发生释放后使用 (CVE-2023-33203)

  - 内核：vmwgfx：争用条件导致信息泄露漏洞 (CVE-2023-33951)

  - 内核：vmwgfx：处理 vmw_buffer_object 对象时发生双重释放 (CVE-2023-33952)

  - kernel: r592: 争用条件导致 r592_remove() 中发生释放后使用 (CVE-2023-35825)

  - 内核：eBPF：dynptr 中的堆栈类型检查不充分 (CVE-2023-39191)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

AlmaLinux 9.2 主机上存在安装的程序包，该程序包受到 TuxCare ALMALINUX9.2：CLSA-2026：1779987841 24 公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：net: hns3: do not allow call hns3_nic_net_open repeatedly hns3_nic_net_open() is not allowed to called repeatly, but there is no checking for this. When doing device reset and setup tc concurrently, there is a small oppotunity to call hns3_nic_net_open repeatedly, and cause kernel bug by calling napi_enable twice. The calltrace information is like below: [ 3078.222780] ------------[ cut here ]------------ [ 3078.230255] kernel BUG at net/core/dev.c:6991! [ 3078.236224] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP [ 3078.243431] Modules linked in: hns3 hclgevf hclge hnae3 vfio_iommu_type1 vfio_pci vfio_virqfd vfio pv680_mii(O) [ 3078.258880] CPU: 0 PID: 295 Comm: kworker/u8:5 Tainted: G O 5.14.0-rc4+ #1 [ 3078.269102] Hardware name: , BIOS KpxxxFPGA 1P B600 V181 08/12/2021 [ 3078.276801] Workqueue: hclge hclge_service_task [hclge] [3078.288774] pstate: 60400009 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 3078.296168] pc :
    napi_enable+0x80/0x84 tc qdisc sho[w 3d0e7v8 .e3t0h218 79] lr : hns3_nic_net_open+0x138/0x510 [hns3] [3078.314771] sp : ffff8000108abb20 [ 3078.319099] x29: ffff8000108abb20 x28: 0000000000000000 x27:
    ffff0820a8490300 [ 3078.329121] x26: 0000000000000001 x25: ffff08209cfc6200 x24: 0000000000000000 [3078.339044] x23: ffff0820a8490300 x22: ffff08209cd76000 x21: ffff0820abfe3880 [ 3078.349018] x20:
    0000000000000000 x19: ffff08209cd76900 x18: 0000000000000000 [ 3078.358620] x17: 0000000000000000 x16:
    ffffc816e1727a50 x15: 0000ffff8f4ff930 [ 3078.368895] x14: 0000000000000000 x13: 0000000000000000 x12:
    0000259e9dbeb6b4 [ 3078.377987] x11: 0096a8f7e764eb40 x10: 634615ad28d3eab5 x9 : ffffc816ad8885b8 [3078.387091] x8 : ffff08209cfc6fb8 x7 : ffff0820ac0da058 x6 : ffff0820a8490344 [ 3078.396356] x5 :
    0000000000000140 x4 : 0000000000000003 x3 : ffff08209cd76938 [ 3078.405365] x2 : 0000000000000000 x1 :
    0000000000000010 x0 : ffff0820abfe38a0 [ 3078.414657] Call trace: [ 3078.418517] napi_enable+0x80/0x84 [3078.424626] hns3_reset_notify_up_enet+0x78/0xd0 [hns3] [ 3078.433469] hns3_reset_notify+0x64/0x80 [hns3] [ 3078.441430] hclge_notify_client+0x68/0xb0 [hclge] [ 3078.450511] hclge_reset_rebuild+0x524/0x884 [hclge] [ 3078.458879] hclge_reset_service_task+0x3c4/0x680 [hclge] [ 3078.467470] hclge_service_task+0xb0/0xb54 [hclge] [ 3078.475675] process_one_work+0x1dc/0x48c [ 3078.481888] worker_thread+0x15c/0x464 [ 3078.487104] kthread+0x160/0x170 [ 3078.492479] ret_from_fork+0x10/0x18 [3078.498785] Code: c8027c81 35ffffa2 d50323bf d65f03c0 (d4210000) [ 3078.506889] ---[ end trace 8ebe0340a1b0fb44 ]--- Once hns3_nic_net_open() is excute success, the flag HNS3_NIC_STATE_DOWN will be cleared. So add checking for this flag, directly return when HNS3_NIC_STATE_DOWN is no set.
    (CVE-2021-47400)

  - 已修复 Linux 内核中的下列漏洞：can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() Using wait_event_interruptible() to wait for complete transmission, but do not check the result of wait_event_interruptible() which can be interrupted. It will result in TX buffer has multiple accessors and the later process interferes with the previous process.
    Following is one of the problems reported by syzbot.
    ============================================================= WARNING: CPU: 0 PID: 0 at net/can/isotp.c:840 isotp_tx_timer_handler+0x2e0/0x4c0 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.13.0-rc7+ #68 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014 RIP: 0010:isotp_tx_timer_handler+0x2e0/0x4c0 Call Trace: <IRQ> ? isotp_setsockopt+0x390/0x390
    __hrtimer_run_queues+0xb8/0x610 hrtimer_run_softirq+0x91/0xd0 ? rcu_read_lock_sched_held+0x4d/0x80
    __do_softirq+0xe8/0x553 irq_exit_rcu+0xf8/0x100 sysvec_apic_timer_interrupt+0x9e/0xc0 </IRQ> asm_sysvec_apic_timer_interrupt+0x12/0x20 Add result check for wait_event_interruptible() in isotp_sendmsg() to avoid multiple accessers for tx buffer. (CVE-2021-47457)

  - 已修复 Linux 内核中的下列漏洞：serial: core: fix transmit-buffer reset and memleak Commit 761ed4a94582 (tty: serial_core: convert uart_close to use tty_port_close) converted serial core to use tty_port_close() but failed to notice that the transmit buffer still needs to be freed on final close. Not freeing the transmit buffer means that the buffer is no longer cleared on next open so that any ioctl() waiting for the buffer to drain might wait indefinitely (e.g. on termios changes) or that stale data can end up being transmitted in case tx is restarted. Furthermore, the buffer of any port that has been opened would leak on driver unbind. Note that the port lock is held when clearing the buffer pointer due to the ldisc race worked around by commit a5ba1d95e46e (uart: fix race between uart_put_char() and uart_shutdown()). Also note that the tty-port shutdown() callback is not called for console ports so it is not strictly necessary to free the buffer page after releasing the lock (cf. d72402145ace (tty/serial: do not free trasnmit buffer page under port lock)). (CVE-2021-47527)

  - 已修复 Linux 内核中的下列漏洞：mm/gup: fix gup_pud_range() for dax For dax pud, pud_huge() returns true on x86. So the function works as long as hugetlb is configured.
    However, dax doesn't depend on hugetlb. Commit 414fd080d125 (mm/gup: fix gup_pmd_range() for dax) fixed devmap-backed huge PMDs, but missed devmap-backed huge PUDs. Fix this as well. This fixes the below kernel panic: general protection fault, probably for non-canonical address 0x69e7c000cc478: 0000 [#1] SMP < snip > Call Trace: <TASK> get_user_pages_fast+0x1f/0x40 iov_iter_get_pages+0xc6/0x3b0 ? mempool_alloc+0x5d/0x170 bio_iov_iter_get_pages+0x82/0x4e0 ? bvec_alloc+0x91/0xc0 ? bio_alloc_bioset+0x19a/0x2a0 blkdev_direct_IO+0x282/0x480 ? __io_complete_rw_common+0xc0/0xc0 ? filemap_range_has_page+0x82/0xc0 generic_file_direct_write+0x9d/0x1a0 ? inode_update_time+0x24/0x30
    __generic_file_write_iter+0xbd/0x1e0 blkdev_write_iter+0xb4/0x150 ? io_import_iovec+0x8d/0x340 io_write+0xf9/0x300 io_issue_sqe+0x3c3/0x1d30 ? sysvec_reschedule_ipi+0x6c/0x80 __io_queue_sqe+0x33/0x240 ? fget+0x76/0xa0 io_submit_sqes+0xe6a/0x18d0 ? __fget_light+0xd1/0x100
    __x64_sys_io_uring_enter+0x199/0x880 ? __context_tracking_enter+0x1f/0x70 ? irqentry_exit_to_user_mode+0x24/0x30 ? irqentry_exit+0x1d/0x30 ? __context_tracking_exit+0xe/0x70 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7fc97c11a7be < snip > </TASK>
    ---[ end trace 48b2e0e67debcaeb ]--- RIP: 0010:internal_get_user_pages_fast+0x340/0x990 < snip > Kernel panic - not syncing: Fatal exception Kernel Offset: disabled (CVE-2022-48986)

  - 已修复 Linux 内核中的下列漏洞：lz4: fix LZ4_decompress_safe_partial read out of bound When partialDecoding, it is EOF if we've either filled the output buffer or can't proceed with reading an offset for following match. In some extreme corner cases when compressed data is suitably corrupted, UAF will occur. As reported by KASAN [1], LZ4_decompress_safe_partial may lead to read out of bound problem during decoding. lz4 upstream has fixed it [2] and this issue has been disscussed here [3] before. current decompression routine was ported from lz4 v1.8.3, bumping lib/lz4 to v1.9.+ is certainly a huge work to be done later, so, we'd better fix it first. [1] https://lore.kernel.org/all/000000000000830d1205cf7f0477@google.com/ [2] https://github.com/lz4/lz4/commit/c5d6f8a8be3927c0bec91bcc58667a6cfad244ad# [3] https://lore.kernel.org/all/CC666AE8-4CA4-4951-B6FB-A2EFDE3AC03B@fb.com/ (CVE-2022-49078)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - 已修复 Linux 内核中的下列漏洞：scsi: lpfc: Check kzalloc() in lpfc_sli4_cgn_params_read() If kzalloc() fails in lpfc_sli4_cgn_params_read(), then we rely on lpfc_read_object()'s routine to NULL check pdata. Currently, an early return error is thrown from lpfc_read_object() to protect us from NULL ptr dereference, but the errno code is -ENODEV. Change the errno code to a more appropriate -ENOMEM. (CVE-2023-53038)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
194262	RHEL 9：kernel (RHSA-2023:6583)	Nessus	Red Hat Local Security Checks	2024/4/28	2025/10/28	high
360748	AlmaLinux 9.2 [TuxCare] 安全更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / 等多个漏洞（ALMALINUX9.2：CLSA-2026：1779987841）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/21	high
248602	Linux Distros 未修补的漏洞：CVE-2023-53038	Nessus	Misc.	2025/8/12	2026/10/31	medium

检测

插件搜索

high

high

medium