遠端 Redhat Enterprise Linux 8 主機上安裝的套件受到 RHSA-2023:2951 公告中提及的多個弱點影響。

    核心套件中包含 Linux 核心，後者是任何 Linux 作業系統的核心。

    下列套件已升級至更新的上游版本核心 (4.18.0)。 (BZ#2122230、 BZ#2122267)

    安全性修正：

    * net/bluetooth/l2cap_core.c 中的 l2cap_reassemble_sdu() 造成的釋放後使用 (CVE-2022-3564)

    * net/ulp接聽 ULP 通訊端時發生釋放後使用 (CVE-2023-0461)

    * hwcpuAMD CPU 可能會暫時執行超出無條件直接分支的範圍 (CVE-2021-26341)

    * FBIOPUT_VSCREENINFO ioctl 的惡意資料可能造成 OOB 寫入記憶體 (CVE-2021-33655)

    * 當 ioctl PIO_FONT 使用惡意資料設定字型時核心會將記憶體寫入超出邊界 (CVE-2021-33656)

    * drivers/tty/tty_buffers.c 中可能存在爭用情形 (CVE-2022-1462)

    * ath9k_htc_probe_device() 中的釋放後使用問題可造成權限提升 (CVE-2022-1679)

    * KVMkvm_mmu_invpcid_gva 中的 NULL 指標解除參照 (CVE-2022-1789)

    * KVMnVMX結束巢狀來賓時遺漏 IBPB可導致 Spectre v2 攻擊 (CVE-2022-2196)

    * netfilternf_conntrack_irc 訊息處理問題 (CVE-2022-2663)

    * xfrm_probe_algs 中的爭用情形可導致 OOB 讀取/寫入 (CVE-2022-3028)

    * mediaem28xx在 kref_get 之前初始化 refcount (CVE-2022-3239)

    * mm/hugetlb.c 中 hugetlb_no_page() 的爭用情形 (CVE-2022-3522)

    * ipv6_renew_options() 中發生記憶體洩漏 (CVE-2022-3524)

    * do_ipv6_setsockopt 中有關 icsk->icsk_af_ops 的資料爭用 (CVE-2022-3566)

    * sk->sk_prot 發生資料爭用 (CVE-2022-3567)

    * net/bluetooth/l2cap_core.c 檔案的 l2cap_recv_acldata 中發生記憶體洩漏 (CVE-2022-3619)

    * 在 mm/gup.c 中follow_page_pte 中的拒絕服務這是因為 pte 項目毒害所導致 (CVE-2022-3623)

    * 在 devlink_param_get 中的 devlink 重新載入失敗後發生釋放後使用 (CVE-2022-3625)

    * brcmfmac 中發生 USB 可存取緩衝區溢位 (CVE-2022-3628)

    * 當 intel_gvt_dma_map_guest_page 函式失敗時在 split_2MB_gtt_entry 中發生雙重釋放 (CVE-2022-3707)

    * l2tp清除 sk_user_data 時遺漏鎖定可導致 NULL 指標解除參照 (CVE-2022-4129)

    * igmp當開啟和關閉 inet 通訊端時ip_check_mc_rcu 中發生釋放後使用 (CVE-2022-20141)

    * 可執行檔空間保護繞過 (CVE-2022-25265)

    * 無權限的使用者可使用 PTRACE_SEIZE 設定 PTRACE_O_SUSPEND_SECCOMP 選項 (CVE-2022-30594)

    * unmap_mapping_range() 與 VM_PFNMAP 對應上的 munmap() 爭用導致過時 TLB 項目 (CVE-2022-39188)

    * TLB 排清作業在某些 KVM_VCPU_PREEMPTED 中遭到錯誤處理進而導致來賓運作失常 (CVE-2022-39189)

    * 報告 dvb-core/dmxdev 中的 vmalloc UAF (CVE-2022-41218)

    * cfg80211_update_notlisted_nontrans() 中的 u8 溢位問題 (CVE-2022-41674)

    * 與分葉 anon_vma 重複使用相關的釋放後使用 (CVE-2022-42703)

    * 在 net/wireless/scan.c 中bss_ref_get 中的 bss_ref_get 存在釋放後使用 (CVE-2022-42720)

    * net/wireless/scan.c 的 cfg80211_add_nontrans_list 中存在 BSS 清單損毀 (CVE-2022-42721)

    * P2P 裝置信標保護中的拒絕服務 (CVE-2022-42722)

    * usbmon 驅動程式中的記憶體損毀 (CVE-2022-43750)

    * 流量控制子系統中的 NULL 指標解除參照 (CVE-2022-47929)

    * rawv6_push_pending_frames 中發生 NULL 指標解除參照 (CVE-2023-0394)

    * fs/cifs/connect.c 中的無效指標主機名稱造成的釋放後使用 (CVE-2023-1195)

    * 在 __page_mapcount 期間發生軟鎖定 (CVE-2023-1582)

    * cbq_classify 中的 slab 超出邊界讀取弱點 (CVE-2023-23454)

    如需安全性問題的詳細資料，包括影響、CVSS 分數、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

    其他變更：

    如需有關此發行版本的詳細變更資訊，請參閱可從「參考資料」一節連結的 Red Hat Enterprise Linux 8.8 版本資訊。

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

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

CentOS Linux 8.4 主機安裝的套件會受到 TuxCare CENTOS8.4：CLSA-2025：1757961864 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：can: peak_usb: fix use after free bugs After calling peak_usb_netif_rx_ni(skb), dereferencing skb is unsafe. Especially, the can_frame cf which aliases skb memory is accessed after the peak_usb_netif_rx_ni(). Reordering the lines solves the issue.
    (CVE-2021-47670)

  - 已解決 Linux 核心中的下列弱點：scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq storvsc_error_wq workqueue should not be marked as WQ_MEM_RECLAIM as it doesn't need to make forward progress under memory pressure. Marking this workqueue as WQ_MEM_RECLAIM may cause deadlock while flushing a non-WQ_MEM_RECLAIM workqueue. In the current state it causes the following warning: [ 14.506347] ------------[ cut here ]------------ [ 14.506354] workqueue: WQ_MEM_RECLAIM storvsc_error_wq_0:storvsc_remove_lun is flushing !WQ_MEM_RECLAIM events_freezable_power_:disk_events_workfn [ 14.506360] WARNING: CPU: 0 PID: 8 at <-snip->kernel/workqueue.c:2623 check_flush_dependency+0xb5/0x130 [ 14.506390] CPU: 0 PID: 8 Comm:
    kworker/u4:0 Not tainted 5.4.0-1086-azure #91~18.04.1-Ubuntu [ 14.506391] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022 [ 14.506393] Workqueue: storvsc_error_wq_0 storvsc_remove_lun [ 14.506395] RIP: 0010:check_flush_dependency+0xb5/0x130 <-snip-> [ 14.506408] Call Trace: [ 14.506412] __flush_work+0xf1/0x1c0 [ 14.506414]
    __cancel_work_timer+0x12f/0x1b0 [ 14.506417] ? kernfs_put+0xf0/0x190 [ 14.506418] cancel_delayed_work_sync+0x13/0x20 [ 14.506420] disk_block_events+0x78/0x80 [ 14.506421] del_gendisk+0x3d/0x2f0 [ 14.506423] sr_remove+0x28/0x70 [ 14.506427] device_release_driver_internal+0xef/0x1c0 [ 14.506428] device_release_driver+0x12/0x20 [ 14.506429] bus_remove_device+0xe1/0x150 [ 14.506431] device_del+0x167/0x380 [ 14.506432]
    __scsi_remove_device+0x11d/0x150 [ 14.506433] scsi_remove_device+0x26/0x40 [ 14.506434] storvsc_remove_lun+0x40/0x60 [ 14.506436] process_one_work+0x209/0x400 [ 14.506437] worker_thread+0x34/0x400 [ 14.506439] kthread+0x121/0x140 [ 14.506440] ? process_one_work+0x400/0x400 [14.506441] ? kthread_park+0x90/0x90 [ 14.506443] ret_from_fork+0x35/0x40 [ 14.506445] ---[ end trace 2d9633159fdc6ee7 ]--- (CVE-2022-49986)

  - 已解決 Linux 核心中的下列弱點：netfilter: nft_tproxy: restrict to prerouting hook TPROXY is only allowed from prerouting, but nft_tproxy doesn't check this. This fixes a crash (null dereference) when using tproxy from e.g. output. (CVE-2022-50001)

  - 已解決 Linux 核心中的下列弱點：ice: xsk: prohibit usage of non-balanced queue id Fix the following scenario: 1. ethtool -L $IFACE rx 8 tx 96 2. xdpsock -q 10 -t -z Above refers to a case where user would like to attach XSK socket in txonly mode at a queue id that does not have a corresponding Rx queue. At this moment ice's XSK logic is tightly bound to act on a queue pair, e.g. both Tx and Rx queues at a given queue id are disabled/enabled and both of them will get XSK pool assigned, which is broken for the presented queue configuration. This results in the splat included at the bottom, which is basically an OOB access to Rx ring array. To fix this, allow using the ids only in scope of combined queues reported by ethtool. However, logic should be rewritten to allow such configurations later on, which would end up as a complete rewrite of the control path, so let us go with this temporary fix. [420160.558008] BUG: kernel NULL pointer dereference, address: 0000000000000082 [420160.566359] #PF:
    supervisor read access in kernel mode [420160.572657] #PF: error_code(0x0000) - not-present page [420160.579002] PGD 0 P4D 0 [420160.582756] Oops: 0000 [#1] PREEMPT SMP NOPTI [420160.588396] CPU: 10 PID:
    21232 Comm: xdpsock Tainted: G OE 5.19.0-rc7+ #10 [420160.597893] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019 [420160.609894] RIP:
    0010:ice_xsk_pool_setup+0x44/0x7d0 [ice] [420160.616968] Code: f3 48 83 ec 40 48 8b 4f 20 48 8b 3f 65 48 8b 04 25 28 00 00 00 48 89 44 24 38 31 c0 48 8d 04 ed 00 00 00 00 48 01 c1 48 8b 11 <0f> b7 92 82 00 00 00 48 85 d2 0f 84 2d 75 00 00 48 8d 72 ff 48 85 [420160.639421] RSP: 0018:ffffc9002d2afd48 EFLAGS: 00010282 [420160.646650] RAX: 0000000000000050 RBX: ffff88811d8bdd00 RCX: ffff888112c14ff8 [420160.655893] RDX:
    0000000000000000 RSI: ffff88811d8bdd00 RDI: ffff888109861000 [420160.665166] RBP: 000000000000000a R08:
    000000000000000a R09: 0000000000000000 [420160.674493] R10: 000000000000889f R11: 0000000000000000 R12:
    000000000000000a [420160.683833] R13: 000000000000000a R14: 0000000000000000 R15: ffff888117611828 [420160.693211] FS: 00007fa869fc1f80(0000) GS:ffff8897e0880000(0000) knlGS:0000000000000000 [420160.703645] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [420160.711783] CR2: 0000000000000082 CR3: 00000001d076c001 CR4: 00000000007706e0 [420160.721399] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [420160.731045] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [420160.740707] PKRU: 55555554 [420160.745960] Call Trace: [420160.750962] <TASK> [420160.755597] ? kmalloc_large_node+0x79/0x90 [420160.762703] ? __kmalloc_node+0x3f5/0x4b0 [420160.769341] xp_assign_dev+0xfd/0x210 [420160.775661] ? shmem_file_read_iter+0x29a/0x420 [420160.782896] xsk_bind+0x152/0x490 [420160.788943] __sys_bind+0xd0/0x100 [420160.795097] ? exit_to_user_mode_prepare+0x20/0x120 [420160.802801] __x64_sys_bind+0x16/0x20 [420160.809298] do_syscall_64+0x38/0x90 [420160.815741] entry_SYSCALL_64_after_hwframe+0x63/0xcd [420160.823731] RIP:
    0033:0x7fa86a0dd2fb [420160.830264] Code: c3 66 0f 1f 44 00 00 48 8b 15 69 8b 0c 00 f7 d8 64 89 02 b8 ff ff ff ff eb bc 0f 1f 44 00 00 f3 0f 1e fa b8 31 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 3d 8b 0c 00 f7 d8 64 89 01 48 [420160.855410] RSP: 002b:00007ffc1146f618 EFLAGS: 00000246 ORIG_RAX:
    0000000000000031 [420160.866366] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa86a0dd2fb [420160.876957] RDX: 0000000000000010 RSI: 00007ffc1146f680 RDI: 0000000000000003 [420160.887604] RBP:
    000055d7113a0520 R08: 00007fa868fb8000 R09: 0000000080000000 [420160.898293] R10: 0000000000008001 R11:
    0000000000000246 R12: 000055d7113a04e0 [420160.909038] R13: 000055d7113a0320 R14: 000000000000000a R15:
    0000000000000000 [420160.919817] </TASK> [420160.925659] Modules linked in: ice(OE) af_packet binfmt_misc
    ---truncated--- (CVE-2022-50003)

  - 已解決 Linux 核心中的下列弱點：ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot It is not yet clear, but it is possible to create a firmware so broken that it will send a reply message before a FW_READY message (it is not yet clear if FW_READY will arrive later). Since the reply_data is allocated only after the FW_READY message, this will lead to a NULL pointer dereference if not filtered out. The issue was reported with IPC4 firmware but the same condition is present for IPC3. (CVE-2022-50015)

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

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - 已解決 Linux 核心中的下列弱點：usb: xhci_plat_remove: avoid NULL dereference Since commit 4736ebd7fcaff1eb8481c140ba494962847d6e0a (usb: host: xhci-plat: omit shared hcd if either root hub has no ports) xhci->shared_hcd can be NULL, which causes the following Oops on reboot:
    [ 710.124450] systemd-shutdown[1]: Rebooting. [ 710.298861] xhci-hcd xhci-hcd.2.auto: remove, state 4 [710.304217] usb usb3: USB disconnect, device number 1 [ 710.317441] xhci-hcd xhci-hcd.2.auto: USB bus 3 deregistered [ 710.323280] xhci-hcd xhci-hcd.2.auto: remove, state 1 [ 710.328401] usb usb2: USB disconnect, device number 1 [ 710.333515] usb 2-3: USB disconnect, device number 2 [ 710.467649] xhci-hcd xhci-hcd.2.auto: USB bus 2 deregistered [ 710.475450] Unable to handle kernel NULL pointer dereference at virtual address 00000000000003b8 [ 710.484425] Mem abort info: [ 710.487265] ESR = 0x0000000096000004 [710.491060] EC = 0x25: DABT (current EL), IL = 32 bits [ 710.496427] SET = 0, FnV = 0 [ 710.499525] EA = 0, S1PTW = 0 [ 710.502716] FSC = 0x04: level 0 translation fault [ 710.507648] Data abort info: [710.510577] ISV = 0, ISS = 0x00000004 [ 710.514462] CM = 0, WnR = 0 [ 710.517480] user pgtable: 4k pages, 48-bit VAs, pgdp=00000008b0050000 [ 710.523976] [00000000000003b8] pgd=0000000000000000, p4d=0000000000000000 [ 710.530961] Internal error: Oops: 96000004 [#1] PREEMPT SMP [ 710.536551] Modules linked in: rfkill input_leds snd_soc_simple_card snd_soc_simple_card_utils snd_soc_nau8822 designware_i2s snd_soc_core dw_hdmi_ahb_audio snd_pcm_dmaengine arm_ccn panfrost ac97_bus gpu_sched snd_pcm at24 fuse configfs sdhci_of_dwcmshc sdhci_pltfm sdhci nvme led_class mmc_core nvme_core bt1_pvt polynomial tp_serio snd_seq_midi snd_seq_midi_event snd_seq snd_timer snd_rawmidi snd_seq_device snd soundcore efivarfs ipv6 [710.575286] CPU: 7 PID: 1 Comm: systemd-shutdow Not tainted 5.19.0-rc7-00043-gfd8619f4fd54 #1 [710.583822] Hardware name: T-Platforms TF307-MB/BM1BM1-A, BIOS 5.6 07/06/2022 [ 710.590972] pstate:
    40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 710.597949] pc : usb_remove_hcd+0x34/0x1e4 [710.602067] lr : xhci_plat_remove+0x74/0x140 [ 710.606351] sp : ffff800009f3b7c0 [ 710.609674] x29:
    ffff800009f3b7c0 x28: ffff000800960040 x27: 0000000000000000 [ 710.616833] x26: ffff800008dc22a0 x25:
    0000000000000000 x24: 0000000000000000 [ 710.623992] x23: 0000000000000000 x22: ffff000805465810 x21:
    ffff000805465800 [ 710.631149] x20: ffff000800f80000 x19: 0000000000000000 x18: ffffffffffffffff [710.638307] x17: ffff000805096000 x16: ffff00080633b800 x15: ffff000806537a1c [ 710.645465] x14:
    0000000000000001 x13: 0000000000000000 x12: ffff00080378d6f0 [ 710.652621] x11: ffff00080041a900 x10:
    ffff800009b204e8 x9 : ffff8000088abaa4 [ 710.659779] x8 : ffff000800960040 x7 : ffff800009409000 x6 :
    0000000000000001 [ 710.666936] x5 : ffff800009241000 x4 : ffff800009241440 x3 : 0000000000000000 [710.674094] x2 : ffff000800960040 x1 : ffff000800960040 x0 : 0000000000000000 [ 710.681251] Call trace: [710.683704] usb_remove_hcd+0x34/0x1e4 [ 710.687467] xhci_plat_remove+0x74/0x140 [ 710.691400] platform_remove+0x34/0x70 [ 710.695165] device_remove+0x54/0x90 [ 710.698753] device_release_driver_internal+0x200/0x270 [ 710.703992] device_release_driver+0x24/0x30 [ 710.708273] bus_remove_device+0xe0/0x16c [ 710.712293] device_del+0x178/0x390 [ 710.715797] platform_device_del.part.0+0x24/0x90 [ 710.720514] platform_device_unregister+0x30/0x50 [ 710.725232] dwc3_host_exit+0x20/0x30 [ 710.728907] dwc3_remove+0x174/0x1b0 [ 710.732494] platform_remove+0x34/0x70 [710.736254] device_remove+0x54/0x90 [ 710.739840] device_release_driver_internal+0x200/0x270 [ 710.745078] device_release_driver+0x24/0x30 [ 710.749359] bus_remove_device+0xe0/0x16c [ 710.753380] device_del+0x178/0x390 [ 710.756881] platform_device_del.part ---truncated--- (CVE-2022-50133)

請注意，Nessus 依賴供應商報告的套件存在。

Rocky Linux 8 主機已安裝的套件會受到 CIQ ciqsa-2026_0634 公告中提及的多個弱點影響。

    此公告彙總了 CIQ FIPS 8 相容中核心 SRPM 的安全修正。它解決了 34 個 CVE：
    CVE-2022-50137、CVE-2022-50070、 CVE-2022-50022CVE-2022-49111CVE-2022-49986和 29 個。

Tenable 已直接從 CIQ 安全性公告中擷取上述描述區塊。

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

CentOS Linux 8.5 主機已安裝的套件會受到 TuxCare CENTOS8.5：CLSA-2025：1757962453 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：can: peak_usb: fix use after free bugs After calling peak_usb_netif_rx_ni(skb), dereferencing skb is unsafe. Especially, the can_frame cf which aliases skb memory is accessed after the peak_usb_netif_rx_ni(). Reordering the lines solves the issue.
    (CVE-2021-47670)

  - 已解決 Linux 核心中的下列弱點：scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq storvsc_error_wq workqueue should not be marked as WQ_MEM_RECLAIM as it doesn't need to make forward progress under memory pressure. Marking this workqueue as WQ_MEM_RECLAIM may cause deadlock while flushing a non-WQ_MEM_RECLAIM workqueue. In the current state it causes the following warning: [ 14.506347] ------------[ cut here ]------------ [ 14.506354] workqueue: WQ_MEM_RECLAIM storvsc_error_wq_0:storvsc_remove_lun is flushing !WQ_MEM_RECLAIM events_freezable_power_:disk_events_workfn [ 14.506360] WARNING: CPU: 0 PID: 8 at <-snip->kernel/workqueue.c:2623 check_flush_dependency+0xb5/0x130 [ 14.506390] CPU: 0 PID: 8 Comm:
    kworker/u4:0 Not tainted 5.4.0-1086-azure #91~18.04.1-Ubuntu [ 14.506391] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022 [ 14.506393] Workqueue: storvsc_error_wq_0 storvsc_remove_lun [ 14.506395] RIP: 0010:check_flush_dependency+0xb5/0x130 <-snip-> [ 14.506408] Call Trace: [ 14.506412] __flush_work+0xf1/0x1c0 [ 14.506414]
    __cancel_work_timer+0x12f/0x1b0 [ 14.506417] ? kernfs_put+0xf0/0x190 [ 14.506418] cancel_delayed_work_sync+0x13/0x20 [ 14.506420] disk_block_events+0x78/0x80 [ 14.506421] del_gendisk+0x3d/0x2f0 [ 14.506423] sr_remove+0x28/0x70 [ 14.506427] device_release_driver_internal+0xef/0x1c0 [ 14.506428] device_release_driver+0x12/0x20 [ 14.506429] bus_remove_device+0xe1/0x150 [ 14.506431] device_del+0x167/0x380 [ 14.506432]
    __scsi_remove_device+0x11d/0x150 [ 14.506433] scsi_remove_device+0x26/0x40 [ 14.506434] storvsc_remove_lun+0x40/0x60 [ 14.506436] process_one_work+0x209/0x400 [ 14.506437] worker_thread+0x34/0x400 [ 14.506439] kthread+0x121/0x140 [ 14.506440] ? process_one_work+0x400/0x400 [14.506441] ? kthread_park+0x90/0x90 [ 14.506443] ret_from_fork+0x35/0x40 [ 14.506445] ---[ end trace 2d9633159fdc6ee7 ]--- (CVE-2022-49986)

  - 已解決 Linux 核心中的下列弱點：netfilter: nft_tproxy: restrict to prerouting hook TPROXY is only allowed from prerouting, but nft_tproxy doesn't check this. This fixes a crash (null dereference) when using tproxy from e.g. output. (CVE-2022-50001)

  - 已解決 Linux 核心中的下列弱點：ice: xsk: prohibit usage of non-balanced queue id Fix the following scenario: 1. ethtool -L $IFACE rx 8 tx 96 2. xdpsock -q 10 -t -z Above refers to a case where user would like to attach XSK socket in txonly mode at a queue id that does not have a corresponding Rx queue. At this moment ice's XSK logic is tightly bound to act on a queue pair, e.g. both Tx and Rx queues at a given queue id are disabled/enabled and both of them will get XSK pool assigned, which is broken for the presented queue configuration. This results in the splat included at the bottom, which is basically an OOB access to Rx ring array. To fix this, allow using the ids only in scope of combined queues reported by ethtool. However, logic should be rewritten to allow such configurations later on, which would end up as a complete rewrite of the control path, so let us go with this temporary fix. [420160.558008] BUG: kernel NULL pointer dereference, address: 0000000000000082 [420160.566359] #PF:
    supervisor read access in kernel mode [420160.572657] #PF: error_code(0x0000) - not-present page [420160.579002] PGD 0 P4D 0 [420160.582756] Oops: 0000 [#1] PREEMPT SMP NOPTI [420160.588396] CPU: 10 PID:
    21232 Comm: xdpsock Tainted: G OE 5.19.0-rc7+ #10 [420160.597893] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019 [420160.609894] RIP:
    0010:ice_xsk_pool_setup+0x44/0x7d0 [ice] [420160.616968] Code: f3 48 83 ec 40 48 8b 4f 20 48 8b 3f 65 48 8b 04 25 28 00 00 00 48 89 44 24 38 31 c0 48 8d 04 ed 00 00 00 00 48 01 c1 48 8b 11 <0f> b7 92 82 00 00 00 48 85 d2 0f 84 2d 75 00 00 48 8d 72 ff 48 85 [420160.639421] RSP: 0018:ffffc9002d2afd48 EFLAGS: 00010282 [420160.646650] RAX: 0000000000000050 RBX: ffff88811d8bdd00 RCX: ffff888112c14ff8 [420160.655893] RDX:
    0000000000000000 RSI: ffff88811d8bdd00 RDI: ffff888109861000 [420160.665166] RBP: 000000000000000a R08:
    000000000000000a R09: 0000000000000000 [420160.674493] R10: 000000000000889f R11: 0000000000000000 R12:
    000000000000000a [420160.683833] R13: 000000000000000a R14: 0000000000000000 R15: ffff888117611828 [420160.693211] FS: 00007fa869fc1f80(0000) GS:ffff8897e0880000(0000) knlGS:0000000000000000 [420160.703645] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [420160.711783] CR2: 0000000000000082 CR3: 00000001d076c001 CR4: 00000000007706e0 [420160.721399] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [420160.731045] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [420160.740707] PKRU: 55555554 [420160.745960] Call Trace: [420160.750962] <TASK> [420160.755597] ? kmalloc_large_node+0x79/0x90 [420160.762703] ? __kmalloc_node+0x3f5/0x4b0 [420160.769341] xp_assign_dev+0xfd/0x210 [420160.775661] ? shmem_file_read_iter+0x29a/0x420 [420160.782896] xsk_bind+0x152/0x490 [420160.788943] __sys_bind+0xd0/0x100 [420160.795097] ? exit_to_user_mode_prepare+0x20/0x120 [420160.802801] __x64_sys_bind+0x16/0x20 [420160.809298] do_syscall_64+0x38/0x90 [420160.815741] entry_SYSCALL_64_after_hwframe+0x63/0xcd [420160.823731] RIP:
    0033:0x7fa86a0dd2fb [420160.830264] Code: c3 66 0f 1f 44 00 00 48 8b 15 69 8b 0c 00 f7 d8 64 89 02 b8 ff ff ff ff eb bc 0f 1f 44 00 00 f3 0f 1e fa b8 31 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 3d 8b 0c 00 f7 d8 64 89 01 48 [420160.855410] RSP: 002b:00007ffc1146f618 EFLAGS: 00000246 ORIG_RAX:
    0000000000000031 [420160.866366] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa86a0dd2fb [420160.876957] RDX: 0000000000000010 RSI: 00007ffc1146f680 RDI: 0000000000000003 [420160.887604] RBP:
    000055d7113a0520 R08: 00007fa868fb8000 R09: 0000000080000000 [420160.898293] R10: 0000000000008001 R11:
    0000000000000246 R12: 000055d7113a04e0 [420160.909038] R13: 000055d7113a0320 R14: 000000000000000a R15:
    0000000000000000 [420160.919817] </TASK> [420160.925659] Modules linked in: ice(OE) af_packet binfmt_misc
    ---truncated--- (CVE-2022-50003)

  - 已解決 Linux 核心中的下列弱點：ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot It is not yet clear, but it is possible to create a firmware so broken that it will send a reply message before a FW_READY message (it is not yet clear if FW_READY will arrive later). Since the reply_data is allocated only after the FW_READY message, this will lead to a NULL pointer dereference if not filtered out. The issue was reported with IPC4 firmware but the same condition is present for IPC3. (CVE-2022-50015)

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

遠端 Redhat Enterprise Linux 9 主機上安裝的多個套件受到 RHSA-2023:2458 公告中提及的多個弱點影響。

    核心套件中包含 Linux 核心，後者是任何 Linux 作業系統的核心。

    安全性修正：

    * net/bluetooth/l2cap_core.c 中 l2cap_connect 和 l2cap_le_connect_req 中的釋放後使用問題 (CVE-2022-42896)

    * net/ulp接聽 ULP 通訊端時發生釋放後使用 (CVE-2023-0461)

    * cpuAMD CPU 可能會暫時執行超出無條件直接分支的範圍 (CVE-2021-26341)

    * FBIOPUT_VSCREENINFO ioctl 的惡意資料可能造成 OOB 寫入記憶體 (CVE-2021-33655)

    * drivers/tty/tty_buffers.c 中可能存在爭用情形 (CVE-2022-1462)

    * KVMkvm_mmu_invpcid_gva 中的 NULL 指標解除參照 (CVE-2022-1789)

    * free_pipe_info() 中的釋放後使用可導致權限提升 (CVE-2022-1882)

    * KVMnVMX結束巢狀來賓時遺漏 IBPB可導致 Spectre v2 攻擊 (CVE-2022-2196)

    * netfilternf_conntrack_irc 訊息處理問題 (CVE-2022-2663)

    * xfrm_probe_algs 中的爭用情形可導致 OOB 讀取/寫入 (CVE-2022-3028)

    * 檔案 net/ipv4/fib_semantics.c 的 fib_nh_match 發生超出邊界讀取 (CVE-2022-3435)

    * mm/hugetlb.c 中 hugetlb_no_page() 的爭用情形 (CVE-2022-3522)

    * ipv6_renew_options() 中發生記憶體洩漏 (CVE-2022-3524)

    * do_ipv6_setsockopt 中有關 icsk->icsk_af_ops 的資料爭用 (CVE-2022-3566)

    * sk->sk_prot 發生資料爭用 (CVE-2022-3567)

    * net/bluetooth/l2cap_core.c 檔案的 l2cap_recv_acldata 中發生記憶體洩漏 (CVE-2022-3619)

    * 在 mm/gup.c 中follow_page_pte 中的拒絕服務這是因為 pte 項目毒害所導致 (CVE-2022-3623)

    * 在 devlink_param_get 中的 devlink 重新載入失敗後發生釋放後使用 (CVE-2022-3625)

    * brcmfmac 中發生 USB 可存取緩衝區溢位 (CVE-2022-3628)

    * net/bluetooth/l2cap_core.c 中 l2cap_conn_del 中的釋放後使用瑕疵 (CVE-2022-3640)

    * 當 intel_gvt_dma_map_guest_page 函式失敗時在 split_2MB_gtt_entry 中發生雙重釋放 (CVE-2022-3707)

    * mptcp中斷連線時子流程遊走中的 NULL 指標解除參照 (CVE-2022-4128)

    * l2tp清除 sk_user_data 時遺漏鎖定可導致 NULL 指標解除參照 (CVE-2022-4129)

    * igmp當開啟和關閉 inet 通訊端時ip_check_mc_rcu 中發生釋放後使用 (CVE-2022-20141)

    * 使用 IMA 的鎖定繞過 (CVE-2022-21505)

    * drivers/net/can/usb/usb_8dev.c 中的 usb_8dev_start_xmit 發生雙重釋放 (CVE-2022-28388)

    * 網路後端可能造成 Linux netfront 使用已釋放的 SKB (XSA-405) (CVE-2022-33743)

    * unmap_mapping_range() 與 VM_PFNMAP 對應上的 munmap() 爭用導致過時 TLB 項目 (CVE-2022-39188)

    * TLB 排清作業在某些 KVM_VCPU_PREEMPTED 中遭到錯誤處理進而導致來賓運作失常 (CVE-2022-39189)

    * cfg80211_update_notlisted_nontrans() 中的 u8 溢位問題 (CVE-2022-41674)

    * 與分葉 anon_vma 重複使用相關的釋放後使用 (CVE-2022-42703)

    * 在 net/wireless/scan.c 中bss_ref_get 中的 bss_ref_get 存在釋放後使用 (CVE-2022-42720)

    * net/wireless/scan.c 的 cfg80211_add_nontrans_list 中存在 BSS 清單損毀 (CVE-2022-42721)

    * P2P 裝置信標保護中的拒絕服務 (CVE-2022-42722)

    * usbmon 驅動程式中的記憶體損毀 (CVE-2022-43750)

    * 流量控制子系統中的 NULL 指標解除參照 (CVE-2022-47929)

    * rawv6_push_pending_frames 中發生 NULL 指標解除參照 (CVE-2023-0394)

    * qdisc_graft() 中的爭用情形導致釋放後使用 (CVE-2023-0590)

    * fs/cifs/connect.c 中的無效指標主機名稱造成的釋放後使用 (CVE-2023-1195)

    * tipc_conn_close 中的拒絕服務 (CVE-2023-1382)

    如需安全性問題的詳細資料，包括影響、CVSS 分數、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

    其他變更：

    如需有關此發行版本的詳細變更資訊，請參閱可從「參考資料」一節連結的 Red Hat Enterprise Linux 9.2 版本資訊。

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

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
175900	RHEL 8：核心 (RHSA-2023:2951)	Nessus	Red Hat Local Security Checks	2023/5/17	2025/9/10	high
352831	CentOS Linux 8.4 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc 多個弱點（CENTOS8.4：CLSA-2025：1757961864）	Nessus	CentOS Local Security Checks	2026/9/30	2026/10/1	high
245926	Linux Distros 未修補的弱點：CVE-2022-50133	Nessus	Misc.	2025/8/8	2026/7/17	medium
357212	Rocky Linux 8 [CIQ] 安全性更新：bpftool / bpftool-debuginfo / kernel / kernel-abi-stablelists / etc 多個弱點（ciqsa-2026_0634）	Nessus	Rocky Linux Local Security Checks	2026/10/1	2026/10/1	high
360866	CentOS Linux 8.5 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc 多個弱點（CENTOS8.5：CLSA-2025：1757962453）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/2	high
175477	RHEL 9：核心 (RHSA-2023:2458)	Nessus	Red Hat Local Security Checks	2023/5/13	2025/9/10	high

偵測

搜尋 Plugin

high

high

medium

high

high

high