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 10 / 9 主機已安裝受到多個弱點影響的套件如 ELSA-2025-20530 公告中所提及。

    - sunrpc將 svc 驗證處理期間視為驗證錯誤的 SVC_GARBAGE處理 (Jeff Layton) [Orabug: 38137447] {CVE-2025-38089}
    - 新增 Zen34 用戶端 (Borislav Petkov (AMD)) [Orabug: 38172252] {CVE-2024-36350} {CVE-2024-36357}
    - x86/處理程序將緩衝區清除移至 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)) [Orabug38172252] {CVE-2024-36350} {CVE-2024-36357}
    - x86/錯誤新增暫時性排程器攻擊緩解 (Borislav Petkov (AMD)) [Orabug38172252] {CVE-2024-36350} {CVE-2024-36357}

Tenable 已直接從 Oracle Linux 安全公告擷取前置描述區塊。

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端 Oracle Linux 9 主機中安裝的套件受到 ELSA-2025-20480 公告中提及的多個弱點影響。

    - sunrpc在 svc 驗證處理期間將 SVC_GARBAGE視為驗證錯誤處理 (Jeff Layton) [Orabug: 38178286] {CVE-2025-38089}
    - 新增 Zen34 用戶端 (Borislav Petkov (AMD)) [Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - x86/處理程序將緩衝區清除移至 MONITOR 之前 (Kim Phillips) [Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - 新增一般計數器 (Borislav Petkov (AMD)) [Orabug38023239] {CVE-2024-36350} {CVE-2024-36357}
    - KVMSVM將 TSA CPUID 位元公告給客體 (Borislav Petkov (AMD)) [Orabug38023239] {CVE-2024-36350} {CVE-2024-36357}
    - x86/錯誤新增暫時性排程器攻擊緩解 (Borislav Petkov (AMD)) [Orabug38023239] {CVE-2024-36350} {CVE-2024-36357}
    - x86/錯誤將 MDS 機器重新命名為更通用的名稱 (Borislav Petkov (AMD)) [Orabug38023239] {CVE-2024-36350} {CVE-2024-36357}
    - block修正將作品集新增到 bio 的問題 (Ming Lei) [Orabug: 37844657] {CVE-2025-22122}
    - f2fs修正以避免存取未初始化的 curseg (Chao Yu) [Orabug: 37844644] {CVE-2025-22123}
    - gpiovirtuser修正潛在的超出邊界寫入 (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 中的 refcount (Dominik Grzegorzek) [Orabug: 38094842] {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 Liang) [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 的 segfault (Adrian Hunter) [Orabug: 38094988] {CVE-2025-38055}
    - ASoCSOFIntelhda重新載入模組時修正 UAF (Tavian Barnes) [Orabug: 38094991] {CVE-2025-38056}
    - espintcp修正 skb 洩漏 (Sabrina Dubroca) [Orabug: 38094993] {CVE-2025-38057}
    - __legitimize_mnt()MNT_SYNC_UMOUNT 的檢查應位於 mount_lock 之下 (Al Viro) [Orabug38095000] {CVE-2025-38058}
    - x86/Kconfig使 CFI_AUTO_DEFAULT 相依於 !RUST 或 Rust >= 1.88 (Pawel Anikiel) [Orabug38094847] {CVE-2025-38033}
    - btrfs如果沒有有效的 csum 樹狀結構避免 NULL 指標解除參照 (Qu Wenruo) [Orabug: 38095010] {CVE-2025-38059}
    - btrfs更正 btrfs__prelim_ref 中 prelim_ref 引數的順序 (Goldwyn Rodrigues) [Orabug:
    38094856] {CVE-2025-38034}
    - nvmet-tcp不還原 null sk_state_change (Alistair Francis) [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) [Orabug: 38095164] {CVE-2025-38080}
    - bpfcopy_verifier_state() 應複製 'loop_entry' 欄位 (Eduard Zingerman) [Orabug: 38095018] {CVE-2025-38060}
    - serialmctrl_gpio將 disable_ms 分割為 sync 和 no_sync API (Alexis Lothore) [Orabug: 38094901] {CVE-2025-38040}
    - net: pktgen修正 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) [Orabug: 38095038] {CVE-2025-38063}
    - firmwarearm_ffa針對 ffa 裝置設定 dma_mask (Viresh Kumar) [Orabug: 38094925] {CVE-2025-38043}
    - mediacx231xx設定 417 的 device_caps (Hans Verkuil) [Orabug: 38094934] {CVE-2025-38044}
    - Orangefs不截斷檔案大小 (Matthew Wilcox) [Orabug: 38095056] {CVE-2025-38065}
    - dm cache透過封鎖失敗的裝置恢復時的重試來防止 BUG_ON (Ming-Hung Tsai) [Orabug
    38095063] {CVE-2025-38066}
    - cryptolzo - 修正壓縮緩衝區滿溢 (Herbert Xu) [Orabug: 38095079] {CVE-2025-38068}
    - PCI: endpoint: pci-epf-test修正導致核心 oops 的重複釋放 (Christian Bruel) [Orabug
    38095087] {CVE-2025-38069}
    - wifiiwlwifi修正除錯動作順序 (Johannes Berg) [Orabug: 38094942] {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) [Orabug: 38095173] {CVE-2025-38081}
    - x86/fred修正在啟用 FRED 的情況下 S4 恢復期間發生的系統懸置 (Xin Li) [Orabug: 38094951] {CVE-2025-38047}
    - block修正 set_blocksize 和讀取路徑之間的爭用 (Darrick J. Wong) [Orabug: 38095117] {CVE-2025-38073}
    - virtio_ring將 KCSAN 的 event_triggered 標記為 racy進而修正資料爭用 (Zhongqiu Han) [Orabug
    38094958] {CVE-2025-38048}
    - scsi目標iscsi修正刪除的連線逾時 (Dmitry Bogdanov) [Orabug: 38095134] {CVE-2025-38075}
    - usbtypecucsidisplayport修正鎖死 (Andrei Kuzynski) [Orabug: 37977018] {CVE-2025-37967}
    - 藍牙btnxpuart修正 FW 釋放期間的核心錯誤 (Neeraj Sanjay Kale) [Orabug: 37844459] {CVE-2025-22102}
    - iiolightopt3001修正因並行旗標存取造成的鎖死 (Luca Ceresoli) [Orabug: 37977026] {CVE-2025-37968}
    - mm/page_alloc修正未接受的記憶體處理中的爭用情形 (Kirill A. Shutemov) [Orabug: 38094767] {CVE-2025-38008}
    - dmaengineidxd使用 idxd_cleanup() 協助程式重構移除呼叫 (Shuai Xue) [Orabug: 38094790] {CVE-2025-38014}
    - dmaengineidxd修正 idxd_alloc 錯誤處理路徑中的記憶體洩漏 (Shuai Xue) [Orabug: 38094793] {CVE-2025-38015}
    - dmaengineti: k3-udma新增缺少的鎖定 (Ronald Wahl) [Orabug: 38094756] {CVE-2025-38005}
    - wifimt76移除驅動程式時停用 napi (Fedor Pchelkin) [Orabug: 38094770] {CVE-2025-38009}
    - phytegraxusb使用位元遮罩進行 UTMI pad 電源狀態追踪 (Wayne Chang) [Orabug: 38094777] {CVE-2025-38010}
    - drm/amdgpucsa 取消對應使用不中斷的鎖定 (Philip Yang) [Orabug: 38094779] {CVE-2025-38011}
    - HIDbpf如果裝置遭到損毀則中止分派 (Rongrong) [Orabug: 38094796] {CVE-2025-38016}
    - sched_extbpf_iter_scx_dsq_new() 應一律初始化 iterator (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}
    - wifi: mac80211配置 struct cfg80211_scan_request 後設定 n_channels (Kees Cook) [Orabug:
    38094788] {CVE-2025-38013}
    -ulatormax20086修正無效的記憶體存取 (Cosmin Tanislav) [Orabug: 38094833] {CVE-2025-38027}
    - net/mlx5e停用上傳連結代表設定檔的 MACsec 卸載 (Carolina Jubran) [Orabug: 38094808] {CVE-2025-38020}
    - net_sched在 ->change() 期間也排清 gso_skb 清單 (Cong Wang) [Orabug: 37998128] {CVE-2025-37992}
    - RDMA/核心修正「KASAN: slab-use-after-free Read in ib_register_device」問題 (Zhu Yanjun) [Orabug:
    38094813] {CVE-2025-38022}
    - nfs處理解除鎖定路徑中的 nfs_get_lock_context 失敗 (Li Lingfeng) [Orabug: 38094818] {CVE-2025-38023}
    - HIDuclogic在 uclogic_input_configured() 中新增 NULL 檢查 (Henry Martin) [Orabug: 38094764] {CVE-2025-38007}
    - RDMA/rxe修正 rxe_queue_cleanup 錯誤中的 slab-use-after-free Read (Zhu Yanjun) [Orabug38094827] {CVE-2025-38024}
    - arm64bpf僅緩解無權限使用者載入的 cBPF 程式 (James Morse) [Orabug: 37977004] {CVE-2025-37963}
    - arm64bpf將 BHB 緩解措施新增至 cBPF 程式的結尾 (James Morse) [Orabug: 37976926] {CVE-2025-37948}
    - usbtypecucsi: displayport修正 NULL 指標存取 (Andrei Kuzynski) [Orabug: 38015126] {CVE-2025-37994}
    - module確保 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}
    - smbclient避免租用中斷在 open_cached_dir 中發生爭用 (Paul Aurich) [Orabug: 37976959] {CVE-2025-37954}
    - drm/amd/display修正 dml 協助程式中的無效內容錯誤 (Roman Li) [Orabug: 37977185] {CVE-2025-37965}
    - drm/v3d如果略過重設則新增工作至擱置清單 (Maira Canal) [Orabug: 37976942] {CVE-2025-37951}
    - iio: imu: st_lsm6dsx修正 st_lsm6dsx_read_tugged_fifo 中可能的鎖定 (Silvano Seva) [Orabug:
    37977031] {CVE-2025-37969}
    - iioimu st_lsm6dsx修正 st_lsm6dsx_read_fifo 中可能的鎖定 (Silvano Seva) [Orabug: 37977037] {CVE-2025-37970}
    - KVMSVM在 SHUTDOWN 攔截時強制離開 SMM 模式 (Mikhail Lobanov) [Orabug: 37976977] {CVE-2025-37957}
    - mm/huge_memory修正無效的 pmd 移轉項目解除參照 (Gavin Guo) [Orabug: 37976982] {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}
    - Input: mtk-pmic-keys - 修正可能的 null 指標解除參照 (Gary Bisson) [Orabug: 37977044] {CVE-2025-37972}
    - bpf在 bpf_redirect_peer 上抹除封包 (Paul Chaignon) [Orabug: 37976990] {CVE-2025-37959}
    - netfilteripset修正雜湊類型中的區域鎖定 (Jozsef Kadlecsik) [Orabug: 38015141] {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) [Orabug: 38015148] {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) [Orabug: 37976972] {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 Thompson) [Orabug:
    37964051,38037120] {CVE-2025-37866}

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 架構；

    - 使用者模式 Linux (UML)；

    - x86 架構；

    - 區塊層子系統；

    - 密碼編譯 API；

    - 計算加速架構；

    - ACPI 驅動程式；

    - Serial ATA 和 Parallel ATA 驅動程式；

    - 驅動程式核心；

    - Ublk 使用者空間區塊驅動程式 ;

    - 藍牙驅動程式;

    - 匯流排裝置；

    - TPM 裝置驅動程式；

    - 時鐘架構和驅動程式；

    - CPU 頻率縮放架構;

    - 緩衝區共用和同步處理架構;

    - DMA 引擎子系統;

    - GPU 驅動程式；

    - HID 子系統；

    - HSI 子系統

    - I2C 子系統；

    - I3C 子系統;

    - IIO 子系統;

    - InfiniBand 驅動程式；

    - IOMMU 子系統；

    - IRQ 晶片驅動程式；

    - MCB 驅動程式

    - 多個裝置驅動程式；

    - 媒體驅動程式；

    - MemoryStick 子系統；

    - 多功能裝置驅動程式；

    - Microchip PCI 驅動程式;

    - Intel Management Engine 介面驅動程式

    - PCI 端點測試驅動程式

    - MTD 區塊裝置驅動程式；

    - 網路驅動程式；

    - 乙太網路綁定驅動程式;

    - Mellanox 網路驅動程式；

    - STMicroelectronics 網路驅動程式；

    - NTB 驅動程式；

    - NVME 驅動程式；

    - PCI 子系統；

    - Synopsys DesignWare PCIe PMU

    - Mellanox 平台驅動程式

    - PWM 驅動程式

    - Remote Processor 子系統;

    - 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) 子系統;

    - 背光驅動程式；

    - Framebuffer 層；

    - W1dallas 的 1-wire 匯流排驅動程式

    - 9P 分散式檔案系統 ;

    - 檔案系統基礎架構 ;

    - BTRFS 檔案系統 ;

    - Ext4 檔案系統;

    - F2FS 檔案系統;

    - JFS 檔案系統;

    - 網路檔案系統程式庫;

    - 網路檔案系統 (NFS) 伺服器程序；

    - NTFS3 檔案系統；

    - 重疊檔案系統；

    - SMB 網路檔案系統；

    - 乙太網路橋接器；

    - io_uring 子系統;

    - Perf 事件；

    - 記憶體管理；

    - UProbes 追踪

    - Amateur Radio 驅動程式；

    - SCTP 通訊協定；

    - 網路通訊端；

    - RDMA 動詞 API

    - BPF 子系統；

    - 核心 fork() 系統呼叫；

    - 休眠控制

    - 排程器基礎架構；

    - 追蹤基礎架構；

    - 觀察佇列通知機制

    - Vector I/O iterator 程式庫

    - 802.1Q VLAN 通訊協定；

    - 9P 檔案系統網路通訊協定；

    - 非同步傳輸模式 (ATM) 子系統；

    - 網路核心；

    - 分散式交換架構;

    - Ethtool 驅動程式；

    - IPv4 網路 ;

    - IPv6 網路；

    - MAC80211 子系統；

    - 管理元件傳輸通訊協定 (MCTP)

    - 多重路徑 TCP;

    - Netfilter；

    Open vSwitch；

    - 網路流量控制；

    - TIPC 通訊協定；

    - TLS 通訊協定；

    - 無線網路 ；

    - ALSA 架構;

    - WCD 音訊轉碼器

    - 適用於 Freescale CPU 的 SoC Audio 驅動程式 ;

    - SoC Audio 通用驅動程式

    - 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
252244	Oracle Linux 10 / 9Unbreakable Enterprise 核心 (ELSA-2025-20530)	Nessus	Oracle Linux Local Security Checks	2025/8/19	2025/8/19	medium
242347	Oracle Linux 9：Unbreakable Enterprise 核心 (ELSA-2025-20480)	Nessus	Oracle Linux Local Security Checks	2025/7/18	2025/7/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

偵測

搜尋 Plugin

medium

medium

medium

high

high