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

  - 已修复 Linux 内核中的下列漏洞：ASoC: codecs: wcd937x: fix a potential memory leak in wcd937x_soc_codec_probe() When snd_soc_dapm_new_controls() or snd_soc_dapm_add_routes() fails, wcd937x_soc_codec_probe() returns without releasing 'wcd937x->clsh_info', which is allocated by wcd_clsh_ctrl_alloc. Add wcd_clsh_ctrl_free() to prevent potential memory leak. (CVE-2025-37941)

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

远程 Oracle Linux 9 主机上安装的程序包受到 ELSA-2025-20480 公告中提及的多个漏洞影响。

    - sunrpc在 svc auth 处理期间将 SVC_GARBAGE 处理为认证错误 (Jeff Layton) [Orabug: 38178286] {CVE-2025-38089}
    - 添加 Zen34 客户端 (Borislav Petkov (AMD)) [Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - x86/process在 MONITOR 之前移动缓冲区清除 (Kim Phillips) [Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - 添加正常计数器 (Borislav Petkov (AMD)) [Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - KVMSVM向客户机公告 TSA CPUID 位 (Borislav Petkov (AMD)) [Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - x86/缺陷添加临时计划程序攻击缓解 (Borislav Petkov (AMD)) [Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - x86/缺陷将 MDS 机械重命名为更通用的名称 (Borislav Petkov (AMD)) [Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - block修复将 folio 添加到 bio (Ming Lei) [Orabug: 37844657] {CVE-2025-22122}
    - f2fs修复以避免访问未初始化的curseg (Chao Yu) [Orabug: 37844644] {CVE-2025-22123}
    - gpio: virtuser修复潜在的越界写入 (Markus Burri) [Orabug: 38095181] {CVE-2025-38082}
    - net_schedhfsc地址可重入队列两次向 eltree 添加类 (Pedro Tammela) [Orabug
    38049363] {CVE-2025-38001}
    - smb客户端修复 cifs_fill_dirent 中的释放后使用 (Zhaolong Wang) [Orabug: 38094970] {CVE-2025-38051}
    - platform/x86dell-wmi-sysman避免 current_password_store() 中的缓冲区溢出 (Vladimir Moskovkin) [Orabug: 38095141] {CVE-2025-38077}
    - ALSApcm修复 PCM OSS 层的缓冲区访问争用 (Takashi Iwai) [Orabug: 38095145] {CVE-2025-38078}
    - canbcm添加 procfs 内容缺少的 rcu 读取保护 (Oliver Hartkopp) [Orabug: 38049369] {CVE-2025-38003}
    - canbcm为 bcm_op 运行时更新添加锁定 (Oliver Hartkopp) [Orabug: 38049374] {CVE-2025-38004}
    - padata请勿泄漏 reorder_work 中的引用计数 (Dominik Grzegorzek) [Orabug38094842] {CVE-2025-38031}
    - cryptoalgif_hash - 修复 hash_accept 中的双重释放 (Ivan Pravdin) [Orabug: 38095153] {CVE-2025-38079}
    - net/tipc修复 tipc_aead_encrypt_done 中的 slab-use-after-free 读取 (Wang Liu) [Orabug: 38094978] {CVE-2025-38052}
    - sch_hfsc修复在 hfsc_enqueue() 中使用 peek 时的 qlen 核算缺陷 (Cong Wang) [Orabug: 38049357] {CVE-2025-38000}
    - idpf修复 idpf_features_check 中的 null-ptr-deref (Pavan Kumar Linga) [Orabug: 38094982] {CVE-2025-38053}
    - ptpocp限制汇总输出函数中的信号/频率计数 (Sagi Maimon) [Orabug: 38094984] {CVE-2025-38054}
    - perf/x86/intel修复包含 sample_freq 的 PEBS-via-PT 的段错误 (Adrian Hunter) [Orabug: 38094988] {CVE-2025-38055}
    - ASoCSOF: Intelhda重新加载模块时修复 UAF (Tabian Barnes) [Orabug: 38094991] {CVE-2025-38056}
    - espintcp修复 skb 泄露 (Sabrina Dubroca) [Orabug: 38094993] {CVE-2025-38057}
    - __legitimize_mnt()应在 mount_lock 下进行 MNT_SYNC_UMOUNT 检查 (Al Viro) [Orabug: 38095000] {CVE-2025-38058}
    - x86/Kconfig使 CFI_AUTO_DEFAULT 依赖于 !RUST 或 Rust >= 1.88 (Pawel Anikiel) [Orabug: 38094847] {CVE-2025-38033}
    - btrfs如果无有效 csum 树则避免空指针取消引用 (Qu Wenruo) [Orabug38095010] {CVE-2025-38059}
    - btrfs修正 btrfs__prelim_ref 中 prelim_ref 参数的顺序 (Goldwyn Rodrigues) [Orabug:
    38094856] {CVE-2025-38034}
    - nvmet-tcp不恢复空 sk_state_change (Alistair Francisco) [Orabug: 38094863] {CVE-2025-38035}
    - vxlan注释 FDB 数据争用 (Ido Schimmel) [Orabug: 38094879] {CVE-2025-38037}
    - cpufreqamd-pstate删除 set_boost 中不必要的 driver_lock (Dhananjay Ugwekar) [Orabug: 38094888] {CVE-2025-38038}
    - drm/amd/display增加 block_sequence 数组大小 (Joshua Aberback) [Orabug38095164] {CVE-2025-38080}
    - bpfcopy_verifier_state() 应复制“loop_entry”字段 (Eduard Zingerman) [Orabug38095018] {CVE-2025-38060}
    - serialmctrl_gpio将 disable_ms 拆分为 sync 和 no_sync API (Alexis Lothore) [Orabug: 38094901] {CVE-2025-38040}
    - netpktgen修复 pktgen_thread_write() 中用户指定缓冲区之外的访问 (Peter Seiderer) [Orabug
    38095024] {CVE-2025-38061}
    - genirq/msi将 IOMMU IOVA 直接存储在 msi_desc 而不是 iommu_cookie 中 (Jason Gunthorpe) [Orabug:
    38095031] {CVE-2025-38062}
    - dm修复 REQ_PREFLUSH 造成的无条件 IO 节流 (Jinliang Zheng) [Orabug38095038] {CVE-2025-38063}
    - firmwarearm_ffa设置 ffa 设备的 dma_mask (Viresh Kumar) [Orabug38094925] {CVE-2025-38043}
    - mediacx231xx设置 417 的 device_caps (Hans Verkuil) [Orabug38094934] {CVE-2025-38044}
    - Orangefs不截断文件大小 (Matthew Wilcox) [Orabug: 38095056] {CVE-2025-38065}
    - dm 缓存通过阻止设备恢复失败的重试来防止 BUG_ON (Ming-Hung Tsai) [Orabug:
    38095063] {CVE-2025-38066}
    - cryptolzo - 修复压缩缓冲区溢出 (Herbert Xu) [Orabug38095079] {CVE-2025-38068}
    - PCI 端点pci-epf-test修复导致内核 oops 的双重释放 (Christian Bruel) [Orabug
    38095087] {CVE-2025-38069}
    - wifiiwlwifi修复调试操作顺序 (Johannes Berg) [Orabug38094942] {CVE-2025-38045}
    - x86/mm检查 memblock_phys_alloc_range() 的返回值 (Philip Redkin) [Orabug: 38095101] {CVE-2025-38071}
    - libnvdimm/labels修复 nd_label_data_init() 中的除法错误 (Robert Richter) [Orabug: 38095109] {CVE-2025-38072}
    - spi-rockchip修复寄存器越界访问 (Luis de Arquer) [Orabug38095173] {CVE-2025-38081}
    - x86/fred修复启用 FRED 的 S4 恢复期间的系统挂起 (Xin Li) [Orabug: 38094951] {CVE-2025-38047}
    - block修复 set_blocksize 和读取路径之间的争用 (Darrick J. Wong) [Orabug38095117] {CVE-2025-38073}
    - virtio_ring通过将 event_triggered 标记为 KCSAN 的 racy修复数据争用 (Zhongqiu Han) [Orabug:
    38094958] {CVE-2025-38048}
    - scsitargetiscsi修复已删除连接的超时 (Dmitry Bogdanov) [Orabug38095134] {CVE-2025-38075}
    - usbtypecucsidisplayport修复死锁 (Andrei Kuchynski) [Orabug: 37977018] {CVE-2025-37967}
    - 蓝牙btnxpuart修复 FW 发布期间的内核错误 (Neeraj Sanjay Kale) [Orabug: 37844459] {CVE-2025-22102}
    - iiolight opt3001修复因并发标记访问导致的死锁 (Luca Ceresoli) [Orabug: 37977026] {CVE-2025-37968}
    - mm/page_alloc修复未接受内存处理中的争用条件 (Kirill A. Shutemov) [Orabug: 38094767] {CVE-2025-38008}
    - dmaengineidxd使用 idxd_cleanup() 帮助程序重构删除调用 (Shuai Xue) [Orabug38094790] {CVE-2025-38014}
    - dmaengineidxd修复 idxd_alloc 的错误处理路径中的内存泄漏 (Shuai Xue) [Orabug: 38094793] {CVE-2025-38015}
    - dmaenginetik3-udma添加缺失的锁定 (Ronald Wahl) [Orabug38094756] {CVE-2025-38005}
    - wifimt76在删除驱动程序时禁用 napi (Fedor Pchelkin) [Orabug38094770] {CVE-2025-38009}
    - phytegraxusb将位掩码用于 UTMI pad 电源状态跟踪 (Wane Chang) [Orabug: 38094777] {CVE-2025-38010}
    - drm/amdgpucsa unmap 使用不间断锁定 (Philip Yang) [Orabug: 38094779] {CVE-2025-38011}
    - HIDbpf中止调度如果设备遭到破坏 (Rongrong) [Orabug38094796] {CVE-2025-38016}
    - sched_extbpf_iter_scx_dsq_new() 应始终初始化迭代器 (Tejun Heo) [Orabug: 38094786] {CVE-2025-38012}
    - net/tls修复 alloc_page 失败时的内核错误 (Pengtao He) [Orabug: 38094802] {CVE-2025-38018}
    - mlxswspectrum_router修复删除 GRE 网络设备时的释放后使用 (Ido Schimmel) [Orabug
    38094804] {CVE-2025-38019}
    - wifimac80211分配 struct cfg80211_scan_request 后设置 n_channels (Kees Cook) [Orabug
    38094788] {CVE-2025-38013}
    - regulatormax20086修复无效的内存访问 (Cosmin Tanislav) [Orabug: 38094833] {CVE-2025-38027}
    - net/mlx5e禁用上行链路representor配置文件的 MACsec 卸载 (Carolina Jubran) [Orabug: 38094808] {CVE-2025-38020}
    - net_sched ->change() 期间也刷新 gso_skb 列表 (Cong Wang) [Orabug37998128] {CVE-2025-37992}
    - RDMA/core修复“KASAN: slab-use-after-free Read in ib_register_device”问题 (Zhu Yanjun) [Orabug:
    38094813] {CVE-2025-38022}
    - nfs处理解锁路径中的 nfs_get_lock_context 失败 (Li Lingfeng) [Orabug38094818] {CVE-2025-38023}
    - HIDuclogic在 uclogic_input_configured() 中添加空检查 (Henry Martin) [Orabug: 38094764] {CVE-2025-38007}
    - RDMA/rxe修复 rxe_queue_cleanup 缺陷中的 slab-use-after-free 读取 (Zhu Yanjun) [Orabug: 38094827] {CVE-2025-38024}
    - arm64bpf仅缓解非特权用户加载的 cBPF 程序 (James Morse) [Orabug: 37977004] {CVE-2025-37963}
    - arm64bpf将 BHB 缓解添加到 cBPF 程序的尾声 (James Morse) [Orabug37976926] {CVE-2025-37948}
    - usbtypecucsidisplayport修复空指针访问 (Andrei Kuchynski) [Orabug: 38015126] {CVE-2025-37994}
    - 模块确保 kobject_put() 对于模块类型 kobjects 是安全的 (Dmitry Antipov) [Orabug: 38015131] {CVE-2025-37995}
    - memblock接受分配的内存然后在 memblock_double_array() 中使用 (Tom Lendacky) [Orabug:
    37976994] {CVE-2025-37960}
    - xenbus使用 kref 跟踪 req 生命周期 (Jason Andryuk) [Orabug: 37976934] {CVE-2025-37949}
    - smb 客户端通过租用中断避免 open_cached_dir 中发生争用 (Paul Aurich) [Orabug37976959] {CVE-2025-37954}
    - drm/amd/display修复 dml 帮助程序中的无效上下文错误 (Roman Li) [Orabug: 37977185] {CVE-2025-37965}
    - drm/v3d如果跳过重置则将作业添加至待定列表 (Maira Canal) [Orabug: 37976942] {CVE-2025-37951}
    - iioimu st_lsm6dsx修复 st_lsm6dsx_read_taged_fifo 中可能的锁定 (Silvano Seva) [Orabug:
    37977031] {CVE-2025-37969}
    - iioimust_lsm6dsx修复 st_lsm6dsx_read_fifo 中可能的锁定 (Silvano Seva) [Orabug: 37977037] {CVE-2025-37970}
    - KVMSVMSHUTDOWN 拦截时强制离开 SMM 模式 (Mikhail Lobanov) [Orabug37976977] {CVE-2025-37957}
    - mm/huge_memory修复取消引用无效的 pmd 迁移条目 (Gavin Guo) [Orabug37976982] {CVE-2025-37958}
    - x86/mm消除可能会无意间跳过 TLB 刷新的窗口 (Dave Hansen) [Orabug: 37977013] {CVE-2025-37964}
    - stagingbcm2835-camera初始化 v4l2_dev 中的 dev (Dave Stevenson) [Orabug: 37977042] {CVE-2025-37971}
    - Inputmtk-pmic-keys - 修复可能存在的空指针取消引用 (Gary Bisson) [Orabug37977044] {CVE-2025-37972}
    - bpfbpf_redirect_peer 上的清理数据包(Paul Chaignon) [Orabug37976990] {CVE-2025-37959}
    - netfilteripset修复哈希类型中的区域锁定 (Jozsef Kadlecsik) [Orabug38015141] {CVE-2025-37997}
    - ipvs修复 do_output_route4 中 saddr 的 uninit-value (Julian Anastasov) [Orabug: 37976996] {CVE-2025-37961}
    - canm_canm_can_class_allocate_dev()初始化设备探测上的旋转锁定 (Antonios Salios) [Orabug
    38015123] {CVE-2025-37993}
    - virtio-net在 virtnet_xsk_pool_enable() 中发生错误时释放 xsk_buffs (Jakub Kicinski) [Orabug: 37976969] {CVE-2025-37955}
    - sch_htb使 htb_deactivate() 幂等 (Cong Wang) [Orabug: 37977176] {CVE-2025-37953}
    - ksmbd修复 parse_lease_state() 中的内存泄漏 (Zhaolong Wang) [Orabug: 37977180] {CVE-2025-37962}
    - openvswitch修复 output_userspace() 中不安全的属性解析 (Eelco Chaudron) [Orabug38015148] {CVE-2025-37998}
    - ksmbd修复 __close_file_table_ids 中的 UAF (Sean Heelan) [Orabug: 37976951] {CVE-2025-37952}
    - ksmbd通过验证 *pos 防止越界流写入 (Norbert Szetei) [Orabug: 37976923] {CVE-2025-37947}
    - ksmbd防止使用空字符串重命名 (Namjae Jeon) [Orabug37976972] {CVE-2025-37956}
    - s390/pci当 PF 具有子 VF 时修复 disable_slot() 中的重复 pci_dev_put() (Niklas Schnelle) [Orabug
    37976920] {CVE-2025-37946}
    - wificfg80211修复多链接元素碎片整理期间的越界访问 (Veerendranath Jakkam) [Orabug: 37977046] {CVE-2025-37973}
    - s390/pci修复缺少检查的 zpci_create_device() 错误返回 (Niklas Schnelle) [Orabug: 37977050] {CVE-2025-37974}
    - fs/erofs/fileio调用 bio_add_folio() 之后调用 erofs_onlinefolio_split() (Max Kellermann) [Orabug
    38015155] {CVE-2025-37999}
    - mlxbf-bootctl在 secure_boot_fuse_state_show() 中使用 sysfs_emit_at() (David Thomson) [Orabug
    37964051,38037120] {CVE-2025-37866}

Tenable 已直接从 Oracle Linux 安全公告中提取上述描述块。

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

远程 Oracle Linux 10 / 9 主机上存在安装的程序包该程序包受到 ELSA-2025-20530 公告中提及的多个漏洞的影响。

    - sunrpc在 svc auth 处理期间将 SVC_GARBAGE 处理为认证错误 (Jeff Layton) [Orabug: 38137447] {CVE-2025-38089}
    - 添加 Zen34 客户端 (Borislav Petkov (AMD)) [Orabug38172252] {CVE-2024-36350} {CVE-2024-36357}
    - x86/process在 MONITOR 之前移动缓冲区清除 (Kim Phillips) [Orabug: 38172252] {CVE-2024-36350} {CVE-2024-36357}
    - 添加正常计数器 (Borislav Petkov (AMD)) [Orabug: 38172252] {CVE-2024-36350} {CVE-2024-36357}
    - KVMSVM向客户机公告 TSA CPUID 位 (Borislav Petkov (AMD)) [Orabug: 38172252] {CVE-2024-36350} {CVE-2024-36357}
    - x86/缺陷添加临时计划程序攻击缓解 (Borislav Petkov (AMD)) [Orabug: 38172252] {CVE-2024-36350} {CVE-2024-36357}

Tenable 已直接从 Oracle Linux 安全公告中提取上述描述块。

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

远程 CentOS Linux 9 主机上安装的多个程序包受到 kernel-5.14.0-598.el9 版本变更日志中提及的多个漏洞影响。

  - 已修复 Linux 内核中的下列漏洞：udf: Fix a slab-out-of-bounds write bug in udf_find_entry() Syzbot reported a slab-out-of-bounds Write bug: loop0: detected capacity change from 0 to 2048 ================================================================== BUG: KASAN: slab-out-of-bounds in udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 Write of size 105 at addr ffff8880123ff896 by task syz-executor323/3610 CPU: 0 PID: 3610 Comm: syz-executor323 Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 kasan_check_range+0x2a7/0x2e0 mm/kasan/generic.c:189 memcpy+0x3c/0x60 mm/kasan/shadow.c:66 udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP:
    0033:0x7ffab0d164d9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe1a7e6bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055 RAX: ffffffffffffffda RBX:
    0000000000000000 RCX: 00007ffab0d164d9 RDX: 00007ffab0d164d9 RSI: 0000000000000000 RDI: 0000000020000180 RBP: 00007ffab0cd5a10 R08: 0000000000000000 R09: 0000000000000000 R10: 00005555573552c0 R11:
    0000000000000246 R12: 00007ffab0cd5aa0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Allocated by task 3610: kasan_save_stack mm/kasan/common.c:45 [inline] kasan_set_track+0x3d/0x60 mm/kasan/common.c:52 ____kasan_kmalloc mm/kasan/common.c:371 [inline] __kasan_kmalloc+0x97/0xb0 mm/kasan/common.c:380 kmalloc include/linux/slab.h:576 [inline] udf_find_entry+0x7b6/0x14f0 fs/udf/namei.c:243 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline]
    __x64_sys_creat+0x11f/0x160 fs/open.c:1396 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd The buggy address belongs to the object at ffff8880123ff800 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 150 bytes inside of 256-byte region [ffff8880123ff800, ffff8880123ff900) The buggy address belongs to the physical page: page:ffffea000048ff80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x123fe head:ffffea000048ff80 order:1 compound_mapcount:0 compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw:
    00fff00000010200 ffffea00004b8500 dead000000000003 ffff888012041b40 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x0(), pid 1, tgid 1 (swapper/0), ts 1841222404, free_ts 0 create_dummy_stack mm/page_owner.c: ---truncated--- (CVE-2022-49846)

  - 已修复 Linux 内核中的下列漏洞：bpf: Fix deadlock when freeing cgroup storage The following commit bc235cdb423a (bpf: Prevent deadlock from recursive bpf_task_storage_[get|delete]) first introduced deadlock prevention for fentry/fexit programs attaching on bpf_task_storage helpers. That commit also employed the logic in map free path in its v6 version. Later bpf_cgrp_storage was first introduced in c4bcfb38a95e (bpf: Implement cgroup storage available to non-cgroup-attached bpf progs) which faces the same issue as bpf_task_storage, instead of its busy counter, NULL was passed to bpf_local_storage_map_free() which opened a window to cause deadlock: <TASK> (acquiring local_storage->lock) _raw_spin_lock_irqsave+0x3d/0x50 bpf_local_storage_update+0xd1/0x460 bpf_cgrp_storage_get+0x109/0x130 bpf_prog_a4d4a370ba857314_cgrp_ptr+0x139/0x170 ?
    __bpf_prog_enter_recur+0x16/0x80 bpf_trampoline_6442485186+0x43/0xa4 cgroup_storage_ptr+0x9/0x20 (holding local_storage->lock) bpf_selem_unlink_storage_nolock.constprop.0+0x135/0x160 bpf_selem_unlink_storage+0x6f/0x110 bpf_local_storage_map_free+0xa2/0x110 bpf_map_free_deferred+0x5b/0x90 process_one_work+0x17c/0x390 worker_thread+0x251/0x360 kthread+0xd2/0x100 ret_from_fork+0x34/0x50 ret_from_fork_asm+0x1a/0x30 </TASK> Progs: - A: SEC(fentry/cgroup_storage_ptr) - cgid (BPF_MAP_TYPE_HASH) Record the id of the cgroup the current task belonging to in this hash map, using the address of the cgroup as the map key. - cgrpa (BPF_MAP_TYPE_CGRP_STORAGE) If current task is a kworker, lookup the above hash map using function parameter @owner as the key to get its corresponding cgroup id which is then used to get a trusted pointer to the cgroup through bpf_cgroup_from_id(). This trusted pointer can then be passed to bpf_cgrp_storage_get() to finally trigger the deadlock issue. - B:
    SEC(tp_btf/sys_enter) - cgrpb (BPF_MAP_TYPE_CGRP_STORAGE) The only purpose of this prog is to fill Prog A's hash map by calling bpf_cgrp_storage_get() for as many userspace tasks as possible. Steps to reproduce: - Run A; - while (true) { Run B; Destroy B; } Fix this issue by passing its busy counter to the free procedure so it can be properly incremented before storage/smap locking. (CVE-2024-58088)

  - 已修复 Linux 内核中的下列漏洞：mm: zswap: properly synchronize freeing resources during CPU hotunplug In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU. If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e.
    acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp). The problem was introduced in commit 1ec3b5fe6eec (mm/zswap: move to use crypto_acomp API for hardware acceleration) when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed. Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
    The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression. Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2]. Alternative fixes that were considered/attempted and could have worked: - Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined. - Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
    [1]https://lkml.kernel.org/20241219212437.2714151-1-yosryahmed@google.com/[2]https://lkml.kernel.org/20250107074724.1756696-2-yosryahmed@google.com/[3]https://lkml.kernel.org/20250107222236.2715883-2-yosryahmed@google.com/ [yosryahmed@google.com: remove comment] (CVE-2025-21693)

  - 已修复 Linux 内核中的下列漏洞：bpf: Send signals asynchronously if !preemptible BPF programs can execute in all kinds of contexts and when a program running in a non-preemptible context uses the bpf_send_signal() kfunc, it will cause issues because this kfunc can sleep.
    Change `irqs_disabled()` to `!preemptible()`. (CVE-2025-21728)

  - 已修复 Linux 内核中的下列漏洞：ipv6: mcast: extend RCU protection in igmp6_send() igmp6_send() can be called without RTNL or RCU being held. Extend RCU protection so that we can safely fetch the net pointer and avoid a potential UAF. Note that we no longer can use sock_alloc_send_skb() because ipv6.igmp_sk uses GFP_KERNEL allocations which can sleep. Instead use alloc_skb() and charge the net->ipv6.igmp_sk socket under RCU protection. (CVE-2025-21759)

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

远程 Ubuntu 25.04 主机上安装的程序包受到 USN-7594-1 公告中提及的多个漏洞的影响。

    在 Linux 内核中发现多个安全问题。攻击者可能利用这些问题入侵系统。此更新修正了以下子系统中的缺陷：

    - ARM32 架构；

    - ARM64 架构；

    - PowerPC 架构；

    - RISC-V 架构；

    - User-Mode Linux (UML)；

    - x86 架构；

    - 区块层子系统；

    - 加密 API；

    - 计算加速框架；

    - ACPI 驱动程序；

    - 串行 ATA 和并行 ATA 驱动程序；

    - 驱动程序核心；

    - ublk userspace block 驱动程序；

    - 蓝牙驱动程序；

    - 总线设备；

    - TPM 设备驱动程序；

    - 时钟框架和驱动程序；

    - CPU 频率缩放框架；

    - 缓冲区共享和同步框架；

    - DMA 引擎子系统；

    - GPU 驱动程序；

    - HID 子系统；

    - HSI 子系统

    - I2C 子系统；

    - I3C 子系统；

    - IIO 子系统；

    - InfiniBand 驱动程序；

    - IOMMU 子系统；

    - IRQ 芯片驱动程序；

    - MCB 驱动程序

    - 多设备驱动程序；

    - 媒体驱动程序；

    - MemoryStick 子系统；

    - 多功能设备驱动程序；

    - Microchip PCI 驱动程序；

    - Intel 管理引擎接口驱动程序

    - PCI 端点测试驱动程序

    - MTD 块设备驱动程序；

    - 网络驱动程序；

    - 以太网绑定驱动程序；

    - Mellanox 网络驱动程序；

    - STMicroelectronics 网络驱动程序；

    - NTB 驱动程序；

    - NVME 驱动程序；

    - PCI 子系统；

    - Synopsys DesignWare PCIe PMU

    - Mellanox 平台驱动程序

    - PWM 驱动程序

    - 远程处理器子系统；

    - S/390 驱动程序；

    - SCSI 子系统；

    - Samsung SoC 驱动程序

    - SPI 子系统；

    - GPIB 驱动程序

    - VideoCore 服务驱动程序

    - 热驱动程序；

    - TTY 驱动程序；

    - UFS 子系统；

    - Cadence USB3 驱动程序

    - ChipIdea USB 驱动程序

    - USB 设备类驱动程序；

    - DesignWare USB3 驱动程序；

    - USB Gadget 驱动程序；

    - USB 主机控制器驱动程序；

    - USB Type-C 支持驱动程序；

    - Virtio Host (VHOST) 子系统；

    - Backlight 驱动程序；

    - Framebuffer 层；

    - W1dallas 的 1-wire 总线驱动程序

    - 9P 分布式文件系统；

    - 文件系统基础设施；

    - BTRFS 文件系统；

    - Ext4 文件系统；

    - F2FS 文件系统；

    - JFS 文件系统；

    - 网络文件系统库；

    - 网络文件系统 (NFS) 服务器后台程序；

    - NTFS3 文件系统；

    - Overlay 文件系统；

    - SMB 网络文件系统；

    - 以太网桥接；

    - io_uring 子系统；

    - Perf 事件；

    - 内存管理；

    - Uprobes 跟踪

    - Amateur Radio 驱动程序；

    - SCTP 协议；

    - 网络套接字；

    - RDMA verbs API

    - BPF 子系统；

    - Kernel fork() syscall；

    - 休眠控制

    - 计划程序基础设施；

    - 跟踪基础设施；

    - 监视队列通知机制

    - 矢量 I/O 迭代器库

    - 802.1Q VLAN 协议；

    - 9P 文件系统网络协议；

    - 异步传输模式 (ATM) 子系统；

    - Networking 核心；

    - Distributed Switch 架构；

    - Ethtool 驱动程序；

    - IPv4 联网；

    - IPv6 联网；

    - MAC80211 子系统；

    - 管理组件传输协议 (MCTP)

    - 多路径 TCP；

    - Netfilter；

    - Open vSwitch；

    - 网络流量控制；

    - TIPC 协议；

    - TLS 协议；

    - 无线网络；

    - ALSA 框架；

    - WCD 音频编解码器

    - SoC Audio for Freescale CPU 驱动程序；

    - SoC 音频通用驱动程序

    - Intel ASoC 驱动程序；

    - QCOM ASoC 驱动程序；

    - Virtio 声音驱动程序

    - CPU电源监控子系统；(CVE-2025-37806, CVE-2025-22084, CVE-2025-39688, CVE-2025-22030, CVE-2025-37754, CVE-2025-37783, CVE-2025-37825, CVE-2025-37752, CVE-2025-22104, CVE-2025-40014, CVE-2025-22103, CVE-2025-37874, CVE-2025-37773, CVE-2025-37741, CVE-2025-37763, CVE-2025-37859, CVE-2025-37779, CVE-2025-23155, CVE-2025-23143, CVE-2025-37788, CVE-2025-22028, CVE-2024-58096, CVE-2025-37842, CVE-2025-37854, CVE-2025-38637, CVE-2024-58097, CVE-2023-53034, CVE-2025-37797, CVE-2025-37851, CVE-2025-37941, CVE-2025-37942, CVE-2025-37748, CVE-2025-37982, CVE-2025-22058, CVE-2025-37781, CVE-2025-23130, CVE-2025-23149, CVE-2025-23146, CVE-2025-37809, CVE-2025-37801, CVE-2025-22080, CVE-2025-23160, CVE-2025-37823, CVE-2025-37827, CVE-2025-39755, CVE-2025-22124, CVE-2025-22033, CVE-2025-22075, CVE-2025-37850, CVE-2025-37757, CVE-2025-22060, CVE-2025-37979, CVE-2025-22098, CVE-2025-39989, CVE-2025-37989, CVE-2025-37790, CVE-2025-37885, CVE-2025-37875, CVE-2025-22066, CVE-2025-37975, CVE-2025-37819, CVE-2025-37755, CVE-2025-37794, CVE-2025-23148, CVE-2025-22067, CVE-2025-22061, CVE-2025-22109, CVE-2025-37884, CVE-2025-37852, CVE-2025-37866, CVE-2025-37872, CVE-2025-37751, CVE-2025-23156, CVE-2025-22065, CVE-2025-37837, CVE-2025-22069, CVE-2025-37822, CVE-2025-22128, CVE-2025-22087, CVE-2025-22023, CVE-2025-22038, CVE-2025-22096, CVE-2025-22076, CVE-2025-22045, CVE-2025-38049, CVE-2025-37870, CVE-2025-37939, CVE-2025-37865, CVE-2025-37860, CVE-2025-37771, CVE-2025-23144, CVE-2025-22081, CVE-2025-39778, CVE-2025-23153, CVE-2025-22036, CVE-2025-23154, CVE-2025-22101, CVE-2025-37808, CVE-2025-37772, CVE-2025-22070, CVE-2025-37789, CVE-2025-22025, CVE-2025-22019, CVE-2025-37868, CVE-2025-22083, CVE-2025-22095, CVE-2025-23161, CVE-2025-22027, CVE-2025-37843, CVE-2025-37985, CVE-2025-23132, CVE-2025-22073, CVE-2025-37940, CVE-2025-23140, CVE-2025-37828, CVE-2025-22063, CVE-2025-22053, CVE-2025-37787, CVE-2025-23152, CVE-2025-37840, CVE-2025-22118, CVE-2025-37981, CVE-2025-22111, CVE-2025-22091, CVE-2025-37841, CVE-2025-23142, CVE-2025-37838, CVE-2025-37775, CVE-2025-23147, CVE-2025-22022, CVE-2025-37745, CVE-2025-37785, CVE-2025-37821, CVE-2025-37988, CVE-2025-37986, CVE-2025-23138, CVE-2025-37836, CVE-2025-37792, CVE-2025-23141, CVE-2025-23159, CVE-2025-38240, CVE-2025-37764, CVE-2025-22120, CVE-2025-37881, CVE-2025-37777, CVE-2025-37987, CVE-2025-37811, CVE-2025-22032, CVE-2025-22044, CVE-2025-37943, CVE-2025-37802, CVE-2025-37829, CVE-2025-37862, CVE-2025-38575, CVE-2025-37799, CVE-2025-37882, CVE-2025-37812, CVE-2025-37765, CVE-2025-37813, CVE-2025-37980, CVE-2025-37873, CVE-2025-37766, CVE-2025-37761, CVE-2025-37892, CVE-2025-22094, CVE-2025-22035, CVE-2025-22055, CVE-2025-22100, CVE-2025-37816, CVE-2025-22062, CVE-2025-22110, CVE-2025-22088, CVE-2025-23129, CVE-2025-38479, CVE-2025-37740, CVE-2025-23136, CVE-2025-37846, CVE-2025-23163, CVE-2025-37977, CVE-2025-37879, CVE-2025-22082, CVE-2025-22046, CVE-2025-22050, CVE-2025-22126, CVE-2025-37796, CVE-2025-37815, CVE-2025-22127, CVE-2025-22105, CVE-2025-22068, CVE-2025-22119, CVE-2025-22089, CVE-2025-37858, CVE-2025-37826, CVE-2025-37945, CVE-2025-23157, CVE-2025-22054, CVE-2025-37805, CVE-2025-37856, CVE-2025-37878, CVE-2025-37768, CVE-2025-22040, CVE-2025-37944, CVE-2025-37774, CVE-2025-22117, CVE-2025-37888, CVE-2025-37857, CVE-2025-37791, CVE-2025-37817, CVE-2025-22041, CVE-2025-37983, CVE-2025-22039, CVE-2025-37749, CVE-2025-22097, CVE-2025-37747, CVE-2025-37762, CVE-2025-22114, CVE-2025-37831, CVE-2025-23133, CVE-2025-22020, CVE-2025-22085, CVE-2025-37807, CVE-2025-22059, CVE-2025-22042, CVE-2025-22123, CVE-2025-22107, CVE-2025-37759, CVE-2024-58094, CVE-2025-40114, CVE-2025-37810, CVE-2025-37833, CVE-2025-23134, CVE-2025-23151, CVE-2025-37743, CVE-2025-22034, CVE-2025-37739, CVE-2025-37863, CVE-2025-39735, CVE-2025-39930, CVE-2025-37847, CVE-2025-37803, CVE-2025-37786, CVE-2025-22112, CVE-2025-37830, CVE-2025-22108, CVE-2025-37767, CVE-2025-37814, CVE-2025-37798, CVE-2025-22086, CVE-2025-37778, CVE-2024-58093, CVE-2025-37848, CVE-2025-22024, CVE-2025-37776, CVE-2025-38104, CVE-2025-37938, CVE-2025-37861, CVE-2025-23150, CVE-2025-22021, CVE-2025-22018, CVE-2025-23137, CVE-2025-37756, CVE-2025-37784, CVE-2025-37769, CVE-2025-37820, CVE-2025-37758, CVE-2025-22047, CVE-2025-37844, CVE-2025-22093, CVE-2025-23162, CVE-2025-22051, CVE-2025-22115, CVE-2025-37845, CVE-2025-22074, CVE-2025-37883, CVE-2025-22116, CVE-2025-37824, CVE-2025-22052, CVE-2025-22090, CVE-2025-37750, CVE-2025-39728, CVE-2025-23145, CVE-2025-22125, CVE-2025-37834, CVE-2025-37738, CVE-2025-37760, CVE-2025-22079, CVE-2025-37877, CVE-2025-37849, CVE-2025-22026, CVE-2025-37886, CVE-2025-22043, CVE-2025-22122, CVE-2025-37937, CVE-2025-22071, CVE-2025-37742, CVE-2025-37744, CVE-2025-22106, CVE-2025-38152, CVE-2025-37869, CVE-2025-23135, CVE-2025-22056, CVE-2024-58095, CVE-2025-37853, CVE-2025-37770, CVE-2025-22031, CVE-2025-23158, CVE-2025-22072, CVE-2025-22102, CVE-2025-40325, CVE-2025-22037, CVE-2025-37876, CVE-2025-37864, CVE-2025-37867, CVE-2025-37855, CVE-2025-37984, CVE-2025-37839, CVE-2025-23131, CVE-2025-22121, CVE-2025-22078, CVE-2025-37800, CVE-2025-37880, CVE-2025-37925, CVE-2025-22113, CVE-2025-22064, CVE-2025-22057, CVE-2025-22092, CVE-2025-37780, CVE-2025-37887, CVE-2025-22099, CVE-2025-37793, CVE-2025-37978, CVE-2025-37746)

Tenable 已直接从 Ubuntu 安全公告中提取上述描述块。

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
245606	Linux Distros 未修补的漏洞：CVE-2025-37941	Nessus	Misc.	2025/8/8	2025/8/21	medium
242347	Oracle Linux 9：Unbreakable Enterprise 内核 (ELSA-2025-20480)	Nessus	Oracle Linux Local Security Checks	2025/7/18	2025/7/19	medium
252244	Oracle Linux 10 / 9Unbreakable Enterprise 内核 (ELSA-2025-20530)	Nessus	Oracle Linux Local Security Checks	2025/8/19	2025/8/19	medium
242070	CentOS 9：kernel-5.14.0-598.el9	Nessus	CentOS Local Security Checks	2025/7/14	2025/7/14	high
240657	Ubuntu 25.04：Linux 内核漏洞 (USN-7594-1)	Nessus	Ubuntu Local Security Checks	2025/6/26	2025/6/26	high

检测

插件搜索

medium

medium

medium

high

high