如 TuxCare CENTOS8.4：CLSA-2025：1763731262公告所述，CentOS Linux 8.4 主机上安装的程序包受到多个漏洞的影响。

  - 在 Samsung Galaxy S3 i9305 4.4.4 设备中发现一个问题。只要前 8 个字节与 EAPOL 的有效 RFC1042（即 LLC/SNAP）标头一致，WEP、WPA、WPA2 和 WPA3 实现就可以接受明文 A-MSDU 帧。攻击者可能会滥用此漏洞，以注入与网络配置无关的任意网络数据包。(CVE-2020-26144)

  - 在 5.11.8 值之前的 Linux 内核中发现一个问题。kernel/bpf/verifier.c 在指针算法上执行不良的越界推测，进而导致边信道攻击，这可破坏 Spectre 缓解措施，并从内核内存获取敏感信息，即 CID-f232326f6966。这会影响未定义 ptr_limit 的指针类型。(CVE-2020-27170)

  - 在 5.11.8 值之前的 Linux 内核中发现一个问题。kernel/bpf/verifier.c 中存在差一错误（导致整数下溢），会影响指针算法上的越界推测，进而导致边信道攻击，这可破坏 Spectre 缓解措施，并从内核内存获取敏感信息，即 CID-10d2bb2e6b1d。(CVE-2020-27171)

  - 已修复 Linux 内核中的下列漏洞：scsi: mpt3sas: Fix use-after-free warning Fix the following use-after-free warning which is observed during controller reset: refcount_t:
    underflow; use-after-free. WARNING: CPU: 23 PID: 5399 at lib/refcount.c:28 refcount_warn_saturate+0xa6/0xf0 (CVE-2022-48695)

  - 已修复 Linux 内核中的下列漏洞：ASoC: ops: Reject out of bounds values in snd_soc_put_volsw() We don't currently validate that the values being set are within the range we advertised to userspace as being valid, do so and reject any values that are out of range.
    (CVE-2022-48738)

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

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

  - ALSAoss修复 PCM OSS 缓冲区分配溢出 我们收到 syzbot 报告在从 snd_pcm_plug_alloc() 调用的 vmalloc() 分配中命中 INT_MAX 溢出。尽管我们对输入参数应用了限制，但这仅基于底层 PCM 设备的 hw_params。由于 PCM OSS 层为数据转换分配临时缓冲区当提供更多通道或更高速率时缓冲区大小可能会意外变大在报告的情况中它超过了 INT_MAX因此命中了 WARN_ON()。
    此修补程序旨在避免此类溢出和过大的缓冲区分配。首先，它添加 1MB 的限制作为周期字节的上限。此大小必须足以满足所有用例，并且我们确实不想处理大于此大小的临时缓冲区。在两个位置执行大小检查一个是计算原始周期字节另一个是计算插件缓冲区大小。此外驱动程序使用 array_size() 和 array3_size() 进行乘法捕获转换后的周期大小和缓冲区字节的溢出。 (CVE-2022-49292)

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

如 TuxCare CENTOS7：CLSA-2025：1759431860公告所述，CentOS Linux 7 主机上安装的程序包受到多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：watchdog: Fix possible use-after-free by calling del_timer_sync() This driver's remove path calls del_timer(). However, that function does not wait until the timer handler finishes. This means that the timer handler may still be running after the driver's remove function has finished, which would result in a use-after-free. Fix by calling del_timer_sync(), which makes sure the timer handler has finished, and unable to re-schedule itself.
    (CVE-2021-47321)

  - 已修复 Linux 内核中的下列漏洞：virtio-net: Add validation for used length This adds validation for used length (might come from an untrusted device) to avoid data corruption or loss. (CVE-2021-47352)

  - 已修复 Linux 内核中的下列漏洞：nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells If a cell has 'nbits' equal to a multiple of BITS_PER_BYTE the logic *p &= GENMASK((cell->nbits%BITS_PER_BYTE) - 1, 0); will become undefined behavior because nbits modulo BITS_PER_BYTE is 0, and we subtract one from that making a large number that is then shifted more than the number of bits that fit into an unsigned long. UBSAN reports this problem: UBSAN: shift-out-of-bounds in drivers/nvmem/core.c:1386:8 shift exponent 64 is too large for 64-bit type 'unsigned long' CPU: 6 PID: 7 Comm: kworker/u16:0 Not tainted 5.15.0-rc3+ #9 Hardware name: Google Lazor (rev3+) with KB Backlight (DT) Workqueue: events_unbound deferred_probe_work_func Call trace: dump_backtrace+0x0/0x170 show_stack+0x24/0x30 dump_stack_lvl+0x64/0x7c dump_stack+0x18/0x38 ubsan_epilogue+0x10/0x54
    __ubsan_handle_shift_out_of_bounds+0x180/0x194 __nvmem_cell_read+0x1ec/0x21c nvmem_cell_read+0x58/0x94 nvmem_cell_read_variable_common+0x4c/0xb0 nvmem_cell_read_variable_le_u32+0x40/0x100 a6xx_gpu_init+0x170/0x2f4 adreno_bind+0x174/0x284 component_bind_all+0xf0/0x264 msm_drm_bind+0x1d8/0x7a0 try_to_bring_up_master+0x164/0x1ac __component_add+0xbc/0x13c component_add+0x20/0x2c dp_display_probe+0x340/0x384 platform_probe+0xc0/0x100 really_probe+0x110/0x304
    __driver_probe_device+0xb8/0x120 driver_probe_device+0x4c/0xfc __device_attach_driver+0xb0/0x128 bus_for_each_drv+0x90/0xdc __device_attach+0xc8/0x174 device_initial_probe+0x20/0x2c bus_probe_device+0x40/0xa4 deferred_probe_work_func+0x7c/0xb8 process_one_work+0x128/0x21c process_scheduled_works+0x40/0x54 worker_thread+0x1ec/0x2a8 kthread+0x138/0x158 ret_from_fork+0x10/0x20 Fix it by making sure there are any bits to mask out. (CVE-2021-47497)

  - Linux PV 设备前端容易受到后端攻击 [此 CNA 信息记录与多个 CVE 相关；文本说明了哪些方面/漏洞对应于哪些 CVE]。多个 Linux PV 设备前端正在以受争用条件约束的方式使用授予的桌面接口删除后端的访问权限，从而导致潜在的数据泄漏、恶意后端造成的数据损坏以及恶意后端触发的拒绝服务攻击：blkfront、netfront、scsifront 和 gntalloc 驱动程序正在测试授权引用是否仍在使用中。如果未正在使用，它们假设后续的授权访问删除将始终成功，但如果后端已在这两个操作之间映射授权页面，则情况并非如此。因此，无论前端 I/O 完成后如何使用页面，后端都可以始终访问客户机内存页面。
    xenbus 驱动程序存在类似的问题，因为它不检查是否成功删除了对共享环形缓冲区的访问权限。blkfront：CVE-2022-23036 netfront：CVE-2022-23037 scsifront：CVE-2022-23038 gntalloc：CVE-2022-23039 xenbus：CVE-2022-23040  blkfront、netfront、scsifront、usbfront、dmabuf、xenbus、9p、kbdfront 和 pvcalls 正在使用一种功能将释放授权引用延迟到不再使用，但相关数据页的释放未与放置授予访问权限同步。因此，即使在内存页面被释放并重新用于其他目的之后，后端仍可继续访问该页面。  如果 CVE-2022-23041 netfront 撤消 rx 路径中的访问权限失败，则 BUG_ON() 断言会失败。这将导致客户机拒绝服务 （DoS） 情况，可由后端触发。 CVE-2022-23042 （CVE-2022-23037， CVE-2022-23038， CVE-2022-23039）

  - 在 6.0.9 及之前版本的 Linux 内核中发现一个问题。drivers/media/dvb-core/dvbdev.c 存在一个与 dvb_register_device 动态分配 fops 相关的释放后使用。(CVE-2022-45884)

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

如 TuxCare CENTOS8.5：CLSA-2025：1763734783公告所述，CentOS Linux 8.5 主机上安装的程序包受到多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：scsi: mpt3sas: Fix use-after-free warning Fix the following use-after-free warning which is observed during controller reset: refcount_t:
    underflow; use-after-free. WARNING: CPU: 23 PID: 5399 at lib/refcount.c:28 refcount_warn_saturate+0xa6/0xf0 (CVE-2022-48695)

  - 已修复 Linux 内核中的下列漏洞：ASoC: ops: Reject out of bounds values in snd_soc_put_volsw() We don't currently validate that the values being set are within the range we advertised to userspace as being valid, do so and reject any values that are out of range.
    (CVE-2022-48738)

  - 已修复 Linux 内核中的下列漏洞：rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev struct rpmsg_ctrldev contains a struct cdev. The current code frees the rpmsg_ctrldev struct in rpmsg_ctrldev_release_device(), but the cdev is a managed object, therefore its release is not predictable and the rpmsg_ctrldev could be freed before the cdev is entirely released, as in the backtrace below. [ 93.625603] ODEBUG: free active (active state 0) object type: timer_list hint:
    delayed_work_timer_fn+0x0/0x7c [ 93.636115] WARNING: CPU: 0 PID: 12 at lib/debugobjects.c:488 debug_print_object+0x13c/0x1b0 [ 93.644799] Modules linked in: veth xt_cgroup xt_MASQUERADE rfcomm algif_hash algif_skcipher af_alg uinput ip6table_nat fuse uvcvideo videobuf2_vmalloc venus_enc venus_dec videobuf2_dma_contig hci_uart btandroid btqca snd_soc_rt5682_i2c bluetooth qcom_spmi_temp_alarm snd_soc_rt5682v [ 93.715175] CPU: 0 PID: 12 Comm: kworker/0:1 Tainted: G B 5.4.163-lockdep #26 [93.723855] Hardware name: Google Lazor (rev3 - 8) with LTE (DT) [ 93.730055] Workqueue: events kobject_delayed_cleanup [ 93.735271] pstate: 60c00009 (nZCv daif +PAN +UAO) [ 93.740216] pc :
    debug_print_object+0x13c/0x1b0 [ 93.744890] lr : debug_print_object+0x13c/0x1b0 [ 93.749555] sp :
    ffffffacf5bc7940 [ 93.752978] x29: ffffffacf5bc7940 x28: dfffffd000000000 [ 93.758448] x27:
    ffffffacdb11a800 x26: dfffffd000000000 [ 93.763916] x25: ffffffd0734f856c x24: dfffffd000000000 [93.769389] x23: 0000000000000000 x22: ffffffd0733c35b0 [ 93.774860] x21: ffffffd0751994a0 x20:
    ffffffd075ec27c0 [ 93.780338] x19: ffffffd075199100 x18: 00000000000276e0 [ 93.785814] x17:
    0000000000000000 x16: dfffffd000000000 [ 93.791291] x15: ffffffffffffffff x14: 6e6968207473696c [93.796768] x13: 0000000000000000 x12: ffffffd075e2b000 [ 93.802244] x11: 0000000000000001 x10:
    0000000000000000 [ 93.807723] x9 : d13400dff1921900 x8 : d13400dff1921900 [ 93.813200] x7 :
    0000000000000000 x6 : 0000000000000000 [ 93.818676] x5 : 0000000000000080 x4 : 0000000000000000 [93.824152] x3 : ffffffd0732a0fa4 x2 : 0000000000000001 [ 93.829628] x1 : ffffffacf5bc7580 x0 :
    0000000000000061 [ 93.835104] Call trace: [ 93.837644] debug_print_object+0x13c/0x1b0 [ 93.841963]
    __debug_check_no_obj_freed+0x25c/0x3c0 [ 93.846987] debug_check_no_obj_freed+0x18/0x20 [ 93.851669] slab_free_freelist_hook+0xbc/0x1e4 [ 93.856346] kfree+0xfc/0x2f4 [ 93.859416] rpmsg_ctrldev_release_device+0x78/0xb8 [ 93.864445] device_release+0x84/0x168 [ 93.868310] kobject_cleanup+0x12c/0x298 [ 93.872356] kobject_delayed_cleanup+0x10/0x18 [ 93.876948] process_one_work+0x578/0x92c [ 93.881086] worker_thread+0x804/0xcf8 [ 93.884963] kthread+0x2a8/0x314 [93.888303] ret_from_fork+0x10/0x18 The cdev_device_add/del() API was created to address this issue (see commit '233ed09d7fda (chardev: add helper function to register char devs with a struct device)'), use it instead of cdev add/del(). (CVE-2022-48759)

  - 已修复 Linux 内核中的下列漏洞：dm integrity: fix memory corruption when tag_size is less than digest size It is possible to set up dm-integrity in such a way that the tag_size parameter is less than the actual digest size. In this situation, a part of the digest beyond tag_size is ignored. In this case, dm-integrity would write beyond the end of the ic->recalc_tags array and corrupt memory. The corruption happened in integrity_recalc->integrity_sector_checksum->crypto_shash_final. Fix this corruption by increasing the tags array so that it has enough padding at the end to accomodate the loop in integrity_recalc() being able to write a full digest size for the last member of the tags array. (CVE-2022-49044)

  - 已修复 Linux 内核中的下列漏洞：ata: sata_dwc_460ex: Fix crash due to OOB write the driver uses libata's tag values from in various arrays. Since the mentioned patch bumped the ATA_TAG_INTERNAL to 32, the value of the SATA_DWC_QCMD_MAX needs to account for that. Otherwise ATA_TAG_INTERNAL usage cause similar crashes like this as reported by Tice Rex on the OpenWrt Forum and reproduced (with symbols) here: | BUG: Kernel NULL pointer dereference at 0x00000000 | Faulting instruction address: 0xc03ed4b8 | Oops: Kernel access of bad area, sig: 11 [#1] | BE PAGE_SIZE=4K PowerPC 44x Platform | CPU: 0 PID: 362 Comm: scsi_eh_1 Not tainted 5.4.163 #0 | NIP: c03ed4b8 LR: c03d27e8 CTR:
    c03ed36c | REGS: cfa59950 TRAP: 0300 Not tainted (5.4.163) | MSR: 00021000 <CE,ME> CR: 42000222 XER:
    00000000 | DEAR: 00000000 ESR: 00000000 | GPR00: c03d27e8 cfa59a08 cfa55fe0 00000000 0fa46bc0 [...] | [..] | NIP [c03ed4b8] sata_dwc_qc_issue+0x14c/0x254 | LR [c03d27e8] ata_qc_issue+0x1c8/0x2dc | Call Trace: | [cfa59a08] [c003f4e0] __cancel_work_timer+0x124/0x194 (unreliable) | [cfa59a78] [c03d27e8] ata_qc_issue+0x1c8/0x2dc | [cfa59a98] [c03d2b3c] ata_exec_internal_sg+0x240/0x524 | [cfa59b08] [c03d2e98] ata_exec_internal+0x78/0xe0 | [cfa59b58] [c03d30fc] ata_read_log_page.part.38+0x1dc/0x204 | [cfa59bc8] [c03d324c] ata_identify_page_supported+0x68/0x130 | [...] This is because sata_dwc_dma_xfer_complete() NULLs the dma_pending's next neighbour chan (a *dma_chan struct) in this '32' case right here (line ~735): > hsdevp->dma_pending[tag] = SATA_DWC_DMA_PENDING_NONE; Then the next time, a dma gets issued;
    dma_dwc_xfer_setup() passes the NULL'd hsdevp->chan to the dmaengine_slave_config() which then causes the crash. With this patch, SATA_DWC_QCMD_MAX is now set to ATA_MAX_QUEUE + 1. This avoids the OOB. But please note, there was a worthwhile discussion on what ATA_TAG_INTERNAL and ATA_MAX_QUEUE is. And why there should not be a fake 33 command-long queue size. Ideally, the dw driver should account for the ATA_TAG_INTERNAL. In Damien Le Moal's words: ... having looked at the driver, it is a bigger change than just faking a 33rd tag that is in fact not a command tag at all. BugLink:
    https://github.com/openwrt/openwrt/issues/9505 (CVE-2022-49073)

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

CentOS Linux 6 主机上存在安装的程序包，该程序包受到 TuxCare CENTOS6：CLSA-2025：1762454401公告中提及的多个漏洞的影响。

  - Linux PV 设备前端容易受到后端攻击 [此 CNA 信息记录与多个 CVE 相关；文本说明了哪些方面/漏洞对应于哪些 CVE]。多个 Linux PV 设备前端正在以受争用条件约束的方式使用授予的桌面接口删除后端的访问权限，从而导致潜在的数据泄漏、恶意后端造成的数据损坏以及恶意后端触发的拒绝服务攻击：blkfront、netfront、scsifront 和 gntalloc 驱动程序正在测试授权引用是否仍在使用中。如果未正在使用，它们假设后续的授权访问删除将始终成功，但如果后端已在这两个操作之间映射授权页面，则情况并非如此。因此，无论前端 I/O 完成后如何使用页面，后端都可以始终访问客户机内存页面。
    xenbus 驱动程序存在类似的问题，因为它不检查是否成功删除了对共享环形缓冲区的访问权限。blkfront：CVE-2022-23036 netfront：CVE-2022-23037 scsifront：CVE-2022-23038 gntalloc：CVE-2022-23039 xenbus：CVE-2022-23040  blkfront、netfront、scsifront、usbfront、dmabuf、xenbus、9p、kbdfront 和 pvcalls 正在使用一种功能将释放授权引用延迟到不再使用，但相关数据页的释放未与放置授予访问权限同步。因此，即使在内存页面被释放并重新用于其他目的之后，后端仍可继续访问该页面。  如果 CVE-2022-23041 netfront 撤消 rx 路径中的访问权限失败，则 BUG_ON() 断言会失败。这将导致客户机发生可由后端触发的拒绝服务 (DoS) 情况。CVE-2022-23042 (CVE-2022-23037)

  - 已修复 Linux 内核中的下列漏洞：ALSA: oss: Fix PCM OSS buffer allocation overflow We've got syzbot reports hitting INT_MAX overflow at vmalloc() allocation that is called from snd_pcm_plug_alloc(). Although we apply the restrictions to input parameters, it's based only on the hw_params of the underlying PCM device. Since the PCM OSS layer allocates a temporary buffer for the data conversion, the size may become unexpectedly large when more channels or higher rates is given;
    in the reported case, it went over INT_MAX, hence it hits WARN_ON(). This patch is an attempt to avoid such an overflow and an allocation for too large buffers. First off, it adds the limit of 1MB as the upper bound for period bytes. This must be large enough for all use cases, and we really don't want to handle a larger temporary buffer than this size. The size check is performed at two places, where the original period bytes is calculated and where the plugin buffer size is calculated. In addition, the driver uses array_size() and array3_size() for multiplications to catch overflows for the converted period size and buffer bytes. (CVE-2022-49292)

  - 已修复 Linux 内核中的下列漏洞：net: atm: fix use after free in lec_send() The ->send() operation frees skb so save the length before calling ->send() to avoid a use after free. (CVE-2025-22004)

  - 已修复 Linux 内核中的下列漏洞：net/sched: sch_qfq: Fix race condition on qfq_aggregate A race condition can occur when 'agg' is modified in qfq_change_agg (called during qfq_enqueue) while other threads access it concurrently. For example, qfq_dump_class may trigger a NULL dereference, and qfq_delete_class may cause a use-after-free. This patch addresses the issue by: 1. Moved qfq_destroy_class into the critical section. 2. Added sch_tree_lock protection to qfq_dump_class and qfq_dump_class_stats. (CVE-2025-38477)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
361530	CentOS Linux 8.4 [TuxCare] 安全更新：bpftool / kernel / kernel-core / kernel-cross-headers / 等多个漏洞（CENTOS8.4：CLSA-2025：1763731262）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
225306	Linux Distros 未修补的漏洞：CVE-2022-49292	Nessus	Misc.	2025/3/5	2026/7/17	high
352574	CentOS Linux 7 [TuxCare] 安全更新：bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / 等多个漏洞（CENTOS7：CLSA-2025：1759431860）	Nessus	CentOS Local Security Checks	2026/9/30	2026/10/21	high
283090	iracleLinux 7kernel-3.10.0-1160.119.1.0.15.el7.AXS7 (AXSA:2025-10986:81)	Nessus	Miracle Linux Local Security Checks	2026/1/13	2026/1/20	high
352076	CentOS Linux 8.5 [TuxCare] 安全更新：bpftool / kernel / kernel-core / kernel-cross-headers / 等多个漏洞（CENTOS8.5：CLSA-2025：1763734783）	Nessus	CentOS Local Security Checks	2026/9/30	2026/9/30	high
361913	CentOS Linux 6 [TuxCare] 安全更新：kernel / kernel-abi-whitelists / kernel-debug / kernel-debug-devel / etc 多个漏洞（CENTOS6：CLSA-2025：1762454401）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high

检测

插件搜索

high

high

high

high

high

high