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

  - iomapiomap修正回寫期間記錄錯誤時發生的記憶體損毀 我時常在 arm64 上看到此損毀情形： 無法處理虛擬位址 00000000000000f8 的核心 NULL 指標解除參照 dev dm-0 邏輯區塊 8733687非同步頁面讀取記憶體中止資訊ESR = 0x0000000096000006 EC = 0x25DABT (目前 EL)、IL = 32 位元 SET = 0、FnV = 0 EA = 0、S1PTW = 0 FSC = 0x06第 2 層轉譯錯誤資料中止資訊ISV = 0、ISS = 0x00000006 CM = 0、WnR = 0 使用者 pgtable
    64k 頁面、42 位元 VA、 pgdp=0000000139750000 [00000000000000f8] pgd=0000000000000000、p4d=0000000000000000、 pud=0000000000000000、 pmd=0000000000000000 內部錯誤Oops96000006 [#1] dev dm-0 邏輯區塊上有 PREEMPT SMP 緩衝區 I/O 錯誤8733688、非同步頁面讀取轉儲存 ftrace 緩衝區
    dev dm-0 上的緩衝區 I/O 錯誤邏輯區塊 8733689非同步頁面讀取 (ftrace 緩衝區空白) XFS (dm-0)記錄 I/O 錯誤 -5 模組連結dm_thin_pool dm_persistent_data XFS (dm-0)在 xfs_trans_read_buf_map+0x1ec/0x590 [xfs] (fs/xfs/xfs_trans_buf.c296) 上偵測到詮釋資料 I/O 錯誤 (0x1)。 dm_bio_prison XFS (dm-0)請卸載檔案系統並修正問題 XFS (dm-0): xfs_imap_lookup
    xfs_ialloc_read_agi() 傳回錯誤 -5, agno 0 dm_bufio dm_log_writes xfs nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_REJECT 可能發生非預期的嚴重訊號 6。
    nf_reject_ipv6 可能非預期的嚴重訊號 6. ipt_REJECT nf_reject_ipv4 CPU: 1 PID: 122166 Comm
    fsstress Tainted: GW 6.0.0-rc5-djwa #rc5 3004c9f1de887ebae86015f2677638ce51ee7 rpcsec_gss_krb5 auth_rpcgss xt_tcpudp ip_set_hash_ip ip_set_hash_net xt_set nft_compat ip_set_hash_mac ip_set nf_tables Hardware name: QEMU KVM Virtual Machine, BIOS 1.5.1 06/16/2021 pstate: 60001000 (nZCv daif -PAN -UAO -TCO
    -DIT +SSBS BTYPE=--) ip_tables pc : 000003fd6d7df200 x_tables lr : 000003fd6d7df1ec overlay nfsv4 CPU: 0 PID: 54031 Comm: u4:3 Tainted: GW 6.0.0-rc5-djwa #rc5 3004c9f1de887ebae86015f2677638ce51ee7405 Hardware name: QEMU KVM Virtual Machine 、 BIOS 1.5.1 2021 年 6 月 16 日 Workqueuewriteback wb_workfn sp 000003ffd9522fd0 (flush-253:0) pstate 60401005 (nZCv daif +PAN -UAO -TCO -DIT +SSBS BTYPE=--) pcerrseq_set+0x1c/ 0x100 x29 000003ffd9522fd0 x28 0000000000000023 x27 000002acefeb6780 x26 0000000000000005 x25
    0000000000000001 x240000000000000000 x2300000000ffffffff x220000000000000005 lr
    __filemap_set_wb_err+0x24/0xe0 x210000000000000006 spffffe000f80f760 x29fffffe000f80f760 x28
    0000000000000003 x27: fffffe000f80f9f8 x26: 0000000002523000 x25: 00000000fffffffb x24: fffffe000f80f868 x23: fffffe000f80fbb0 x22: fffffc0180c26a78 x21: 0000000002530000 x20: 0000000000000000 x19:
    0000000000000000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000001 x13: 0000000000470af3 x12: fffffc0058f70000 x11: 0000000000000040 x10:
    0000000000001b20 x9 : fffffe000836b288 x8 : fffffc00eb9fd480 x7 : 0000000000f83659 x6 : 0000000000000000 x5 : 0000000000000869 x4 : 0000000000000005 x3 : 00000000000000f8 x20: 000003fd6d740020 x19:
    000000000001dd36 x18: 0000000000000001 x17: 000003fd6d78704c x16: 0000000000000001 x15: 000002acfac87668 x2 : 0000000000000ffa x1 : 00000000fffffffb x0 : 00000000000000f8 Call trace: errseq_set+0x1c/0x100
    __filemap_set_wb_err+0x24/0xe0 iomap_do_writepage+0x5e4/0xd5c write_cache_pages+0x208/0x674 iomap_writepages+0x34/0x60 xfs_vm_writepages+0x8c/0xcc [xfs 7a861f39c43631f15d]x503a5884246d
    0000000000000000 x13: 2064656e72757465 x12: 0000000000002180 x11: 000003fd6d8a82d0 x10: 0000000000000000 x9 : 000003fd6d8ae288 x8 : 0000000000000083 x7 : 00000000ffffffff x6 : 00000000ffffffee x5 :
    00000000fbad2887 x4 000003fd6d9abb58 x3 000003fd6d740020 x2 0000000000000006 x1 00000000001dd36 x0 0000000000000000 CPU ---truncated--- (CVE-2022-50406)

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

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

    kernel-rt 套件提供即時 Linux 核心，其可針對具有極高決定機制需求的系統啟用微調。

    安全性修正：

    * 核心ALSAusb-audioALSA USB 音訊超出邊界錯誤 (CVE-2022-48701)

    * 核心：ipv6：mcast：在 mld_del_delrec() 中延遲放置 pmc->idev (CVE-2025-38550)

    * 核心：sctp：線性化 sctp_rcv 中的複制 gso 封包 (CVE-2025-38718)

    * 核心NFS修正更新現有寫入時的爭用情形 (CVE-2025-39697)

    * 核心：ipv6：sr：將 MAC 比較修復為常數時間 (CVE-2025-39702)

    * 核心：NFS：修正 nfs_fh_to_dentry() 中的 filehandle 邊界檢查 (CVE-2025-39730)

    * 核心：wifi：mac80211：檢查 S1G 動作框架大小 (CVE-2023-53257)

    * 核心wifibrcmfmacbrcmf_get_assoc_ies() 中發生 slab 超出邊界讀取 (CVE-2023-53213)

    * 核心wifiath9k不允許覆寫 ENDPOINT0 屬性 (CVE-2023-53185)

    * 核心mt76mt7921藉由存取未配置的 eeprom.data 修正核心錯誤 (CVE-2023-53232)

    * 核心mm修正 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心：wifi：mwifiex：修復 rx 封包時發生的 OOB 和整數反向溢位 (CVE-2023-53226)

    * 核心藍牙L2CAP修正釋放後使用 (CVE-2023-53305)

    * 核心：pstore/ram：檢查 init 期間空白 przs 的開始 (CVE-2023-53331)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心netschedsfb修正 sfb_init() 失敗時的 NULL 指標存取問題 (CVE-2022-50356)

    * 核心skbuffskb_segment在使用 skbuff 片段之前呼叫零複製函式 (CVE-2023-53354)

    * 核心mmkmem修正 obj_stock_flush_required() 中的 NULL 指標解除參照 (CVE-2023-53401)

    * 核心：Bluetooth：修正清除金鑰時的潛在釋放後使用 (CVE-2023-53386)

    * 核心：Bluetooth：L2CAP：修正釋放後使用 (CVE-2022-50386)

    * 核心wifibrcmfmac修正 brcmf_netdev_start_xmit() 中的釋放後使用錯誤 (CVE-2022-50408)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：crypto：xts - 正確處理 EBUSY (CVE-2023-53494)

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

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

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

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

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

    安全性修復：

    * 核心：NFS：修正更新現有寫入時的爭用情形 (CVE-2025-39697)

    * 核心：wifi：mwifiex：修復 rx 封包時發生的 OOB 和整數反向溢位 (CVE-2023-53226)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

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

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

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

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

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

    安全性修正：

    * 核心ALSAusb-audio也驗證 UAC3 power 網域描述元 (CVE-2025-38729)

    * 核心：ALSA：usb-audio：驗證 UAC3 叢集區段描述符號 (CVE-2025-39757)

    * 核心：mm：修復 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心：Bluetooth：L2CAP：修正 l2cap_disconnect_rsp 中的「錯誤解鎖平衡」(CVE-2023-53297)

    * 核心scsiqla2xxx終止 rport 時等待 io 傳回 (CVE-2023-53322)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心netschedsfb修正 sfb_init() 失敗時的 NULL 指標存取問題 (CVE-2022-50356)

    * 核心ext4修正 ext4_check_flag_values 位元移位中的未定義行為 (CVE-2022-50403)

    * 核心NFSD防止 NFSv2 READ 中的傳送緩衝區溢位 (CVE-2022-50410)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：tcp：清除 tcp_disconnect() 中的 tcp_sk(sk)->fastopen_rsk (CVE-2025-39955)

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

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

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

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

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

    安全性修正：

    * 核心ALSAusb-audioALSA USB 音訊超出邊界錯誤 (CVE-2022-48701)

    * 核心ASoCSOFIntelhda透過 snprintf() 修正潛在的緩衝區溢位 (CVE-2022-50050)

    * 核心wifibrcmfmacbrcmf_get_assoc_ies() 中發生 slab 超出邊界讀取 (CVE-2023-53213)

    * 核心wifiath9k不允許覆寫 ENDPOINT0 屬性 (CVE-2023-53185)

    * 核心mm修正 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心：crypto：seqiv - 正確處理 EBUSY (CVE-2023-53373)

    * 核心：Bluetooth：修正清除金鑰時的潛在釋放後使用 (CVE-2023-53386)

    * 核心wifibrcmfmac修正 brcmf_netdev_start_xmit() 中的釋放後使用錯誤 (CVE-2022-50408)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：wifi：cfg80211：修復 cmp_bss() 中的釋放後使用 (CVE-2025-39864)

    * 核心：scsi：lpfc：修正延遲接收路徑中的緩衝區釋放/清除順序 (CVE-2025-39841)

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

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

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

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

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

    安全性修正：

    * 核心：eventpoll：修正半無限制遞迴 (CVE-2025-38614)

    * 核心NFS修正更新現有寫入時的爭用情形 (CVE-2025-39697)

    * 核心wifibrcmfmacbrcmf_get_assoc_ies() 中發生 slab 超出邊界讀取 (CVE-2023-53213)

    * 核心wifiath9k不允許覆寫 ENDPOINT0 屬性 (CVE-2023-53185)

    * 核心mt76mt7921藉由存取未配置的 eeprom.data 修正核心錯誤 (CVE-2023-53232)

    * 核心mm修正 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心：wifi：mwifiex：修復 rx 封包時發生的 OOB 和整數反向溢位 (CVE-2023-53226)

    * 核心藍牙L2CAP修正釋放後使用 (CVE-2023-53305)

    * 核心：pstore/ram：檢查 init 期間空白 przs 的開始 (CVE-2023-53331)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心netschedsfb修正 sfb_init() 失敗時的 NULL 指標存取問題 (CVE-2022-50356)

    * 核心：crypto：seqiv - 正確處理 EBUSY (CVE-2023-53373)

    * 核心mmkmem修正 obj_stock_flush_required() 中的 NULL 指標解除參照 (CVE-2023-53401)

    * 核心：Bluetooth：修正清除金鑰時的潛在釋放後使用 (CVE-2023-53386)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：crypto：xts - 正確處理 EBUSY (CVE-2023-53494)

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

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

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

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

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

    安全性修正：

    * 核心ALSAusb-audioALSA USB 音訊超出邊界錯誤 (CVE-2022-48701)

    * 核心：ipv6：mcast：在 mld_del_delrec() 中延遲放置 pmc->idev (CVE-2025-38550)

    * 核心：sctp：線性化 sctp_rcv 中的複制 gso 封包 (CVE-2025-38718)

    * 核心NFS修正更新現有寫入時的爭用情形 (CVE-2025-39697)

    * 核心：ipv6：sr：將 MAC 比較修復為常數時間 (CVE-2025-39702)

    * 核心：NFS：修正 nfs_fh_to_dentry() 中的 filehandle 邊界檢查 (CVE-2025-39730)

    * 核心：wifi：mac80211：檢查 S1G 動作框架大小 (CVE-2023-53257)

    * 核心wifibrcmfmacbrcmf_get_assoc_ies() 中發生 slab 超出邊界讀取 (CVE-2023-53213)

    * 核心wifiath9k不允許覆寫 ENDPOINT0 屬性 (CVE-2023-53185)

    * 核心mt76mt7921藉由存取未配置的 eeprom.data 修正核心錯誤 (CVE-2023-53232)

    * 核心mm修正 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心：wifi：mwifiex：修復 rx 封包時發生的 OOB 和整數反向溢位 (CVE-2023-53226)

    * 核心藍牙L2CAP修正釋放後使用 (CVE-2023-53305)

    * 核心：pstore/ram：檢查 init 期間空白 przs 的開始 (CVE-2023-53331)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心netschedsfb修正 sfb_init() 失敗時的 NULL 指標存取問題 (CVE-2022-50356)

    * 核心skbuffskb_segment在使用 skbuff 片段之前呼叫零複製函式 (CVE-2023-53354)

    * 核心mmkmem修正 obj_stock_flush_required() 中的 NULL 指標解除參照 (CVE-2023-53401)

    * 核心：Bluetooth：修正清除金鑰時的潛在釋放後使用 (CVE-2023-53386)

    * 核心：Bluetooth：L2CAP：修正釋放後使用 (CVE-2022-50386)

    * 核心wifibrcmfmac修正 brcmf_netdev_start_xmit() 中的釋放後使用錯誤 (CVE-2022-50408)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：crypto：xts - 正確處理 EBUSY (CVE-2023-53494)

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

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

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

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

    kernel-rt 套件提供即時 Linux 核心，其可針對具有極高決定機制需求的系統啟用微調。

    安全性修正：

    * 核心：eventpoll：修正半無限制遞迴 (CVE-2025-38614)

    * 核心NFS修正更新現有寫入時的爭用情形 (CVE-2025-39697)

    * 核心wifibrcmfmacbrcmf_get_assoc_ies() 中發生 slab 超出邊界讀取 (CVE-2023-53213)

    * 核心wifiath9k不允許覆寫 ENDPOINT0 屬性 (CVE-2023-53185)

    * 核心mt76mt7921藉由存取未配置的 eeprom.data 修正核心錯誤 (CVE-2023-53232)

    * 核心mm修正 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心：wifi：mwifiex：修復 rx 封包時發生的 OOB 和整數反向溢位 (CVE-2023-53226)

    * 核心藍牙L2CAP修正釋放後使用 (CVE-2023-53305)

    * 核心：pstore/ram：檢查 init 期間空白 przs 的開始 (CVE-2023-53331)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心netschedsfb修正 sfb_init() 失敗時的 NULL 指標存取問題 (CVE-2022-50356)

    * 核心：crypto：seqiv - 正確處理 EBUSY (CVE-2023-53373)

    * 核心mmkmem修正 obj_stock_flush_required() 中的 NULL 指標解除參照 (CVE-2023-53401)

    * 核心：Bluetooth：修正清除金鑰時的潛在釋放後使用 (CVE-2023-53386)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：crypto：xts - 正確處理 EBUSY (CVE-2023-53494)

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

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

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

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

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

    安全性修正：

    * 核心ALSAusb-audioALSA USB 音訊超出邊界錯誤 (CVE-2022-48701)

    * 核心ethtool取得連結設定時檢查裝置是否存在 (CVE-2024-46679)

    * 核心ALSAusb-audio也驗證 UAC3 power 網域描述元 (CVE-2025-38729)

    * 核心：sctp：線性化 sctp_rcv 中的複制 gso 封包 (CVE-2025-38718)

    * 核心：nfsd：處理 nfsd4_setclientid_confirm() 中的 get_client_locked() 失敗 (CVE-2025-38724)

    * 核心：NFS：修正更新現有寫入時的爭用情形 (CVE-2025-39697)

    * 核心：ALSA：usb-audio：驗證 UAC3 叢集區段描述符號 (CVE-2025-39757)

    * 核心wifibrcmfmacbrcmf_get_assoc_ies() 中發生 slab 超出邊界讀取 (CVE-2023-53213)

    * 核心：mm：修復 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心：wifi：mwifiex：修復 rx 封包時發生的 OOB 和整數反向溢位 (CVE-2023-53226)

    * 核心：Bluetooth：L2CAP：修正 l2cap_disconnect_rsp 中的「錯誤解鎖平衡」(CVE-2023-53297)

    * 核心：smb：用戶端：修正 rename(2) 中與並行開啟爭用的問題 (CVE-2025-39825)

    * 核心：efivarfs：修正 efivarfs_d_compare 中的 slab-out-of-bounds (CVE-2025-39817)

    * 核心藍牙L2CAP修正釋放後使用 (CVE-2023-53305)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心ip6mr修正 ip6mr_cache_report() 中的 skb_under_panic (CVE-2023-53365)

    * 核心netschedsfb修正 sfb_init() 失敗時的 NULL 指標存取問題 (CVE-2022-50356)

    * 核心skbuffskb_segment在使用 skbuff 片段之前呼叫零複製函式 (CVE-2023-53354)

    * 核心RDMA/mlx5用於 裝置時修正 mlx5_ib_get_hw_stats (CVE-2023-53393)

    * 核心：crypto：seqiv - 正確處理 EBUSY (CVE-2023-53373)

    * 核心：Bluetooth：L2CAP：修正釋放後使用 (CVE-2022-50386)

    * 核心ext4修正 ext4_check_flag_values 位元移位中的未定義行為 (CVE-2022-50403)

    * 核心wifibrcmfmac修正 brcmf_netdev_start_xmit() 中的釋放後使用錯誤 (CVE-2022-50408)

    * 核心NFSD防止 NFSv2 READ 中的傳送緩衝區溢位 (CVE-2022-50410)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：wifi：cfg80211：修復 cmp_bss() 中的釋放後使用 (CVE-2025-39864)

    * 核心：scsi：lpfc：修正延遲接收路徑中的緩衝區釋放/清除順序 (CVE-2025-39841)

    * 核心：mm/memory-failure：修正記憶體解除毒害時的 VM_BUG_ON_PAGE(PagePoisoned(page)) (CVE-2025-39883)

    * 核心NFSD避免以 ops->opnum == OP_ILLEGAL 呼叫 OPDESC() (CVE-2023-53680)

    * 核心：tcp：清除 tcp_disconnect() 中的 tcp_sk(sk)->fastopen_rsk (CVE-2025-39955)

    * 核心tcp不要在 tcp_conn_request() 中呼叫 reqsk_fastopen_remove() (CVE-2025-40186)

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

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

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

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

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

    安全性修復：

    * 核心ethtool取得連結設定時檢查裝置是否存在 (CVE-2024-46679)

    * 核心ALSAusb-audio也驗證 UAC3 power 網域描述元 (CVE-2025-38729)

    * 核心：sctp：線性化 sctp_rcv 中的複制 gso 封包 (CVE-2025-38718)

    * 核心：nfsd：處理 nfsd4_setclientid_confirm() 中的 get_client_locked() 失敗 (CVE-2025-38724)

    * 核心：ALSA：usb-audio：驗證 UAC3 叢集區段描述符號 (CVE-2025-39757)

    * 核心：wifi：mwifiex：修復 rx 封包時發生的 OOB 和整數反向溢位 (CVE-2023-53226)

    * 核心：Bluetooth：L2CAP：修正 l2cap_disconnect_rsp 中的「錯誤解鎖平衡」(CVE-2023-53297)

    * 核心scsiqla2xxx終止 rport 時等待 io 傳回 (CVE-2023-53322)

    * 核心ip6mr修正 ip6mr_cache_report() 中的 skb_under_panic (CVE-2023-53365)

    * 核心RDMA/mlx5用於 裝置時修正 mlx5_ib_get_hw_stats (CVE-2023-53393)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：scsi：lpfc：修正延遲接收路徑中的緩衝區釋放/清除順序 (CVE-2025-39841)

    * 核心：tcp：清除 tcp_disconnect() 中的 tcp_sk(sk)->fastopen_rsk (CVE-2025-39955)

    * 核心tcp不要在 tcp_conn_request() 中呼叫 reqsk_fastopen_remove() (CVE-2025-40186)

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

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

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

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

  - 已解決 Linux 核心中的下列弱點：pid: take a reference when initializing `cad_pid` During boot, kernel_init_freeable() initializes `cad_pid` to the init task's struct pid. Later on, we may change `cad_pid` via a sysctl, and when this happens proc_do_cad_pid() will increment the refcount on the new pid via get_pid(), and will decrement the refcount on the old pid via put_pid(). As we never called get_pid() when we initialized `cad_pid`, we decrement a reference we never incremented, can therefore free the init task's struct pid early. As there can be dangling references to the struct pid, we can later encounter a use-after-free (e.g. when delivering signals). This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to have been around since the conversion of `cad_pid` to struct pid in commit 9ec52099e4b8 ([PATCH] replace cad_pid by a struct pid) from the pre-KASAN stone age of v2.6.19. Fix this by getting a reference to the init task's struct pid when we assign it to `cad_pid`.
    Full KASAN splat below. ================================================================== BUG: KASAN:
    use-after-free in ns_of_pid include/linux/pid.h:153 [inline] BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273 CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1 Hardware name: linux,dummy-virt (DT) Call trace: ns_of_pid include/linux/pid.h:153 [inline] task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 do_notify_parent+0x308/0xe60 kernel/signal.c:1950 exit_notify kernel/exit.c:682 [inline] do_exit+0x2334/0x2bd0 kernel/exit.c:845 do_group_exit+0x108/0x2c8 kernel/exit.c:922 get_signal+0x4e4/0x2a88 kernel/signal.c:2781 do_signal arch/arm64/kernel/signal.c:882 [inline] do_notify_resume+0x300/0x970 arch/arm64/kernel/signal.c:936 work_pending+0xc/0x2dc Allocated by task 0: slab_post_alloc_hook+0x50/0x5c0 mm/slab.h:516 slab_alloc_node mm/slub.c:2907 [inline] slab_alloc mm/slub.c:2915 [inline] kmem_cache_alloc+0x1f4/0x4c0 mm/slub.c:2920 alloc_pid+0xdc/0xc00 kernel/pid.c:180 copy_process+0x2794/0x5e18 kernel/fork.c:2129 kernel_clone+0x194/0x13c8 kernel/fork.c:2500 kernel_thread+0xd4/0x110 kernel/fork.c:2552 rest_init+0x44/0x4a0 init/main.c:687 arch_call_rest_init+0x1c/0x28 start_kernel+0x520/0x554 init/main.c:1064 0x0 Freed by task 270:
    slab_free_hook mm/slub.c:1562 [inline] slab_free_freelist_hook+0x98/0x260 mm/slub.c:1600 slab_free mm/slub.c:3161 [inline] kmem_cache_free+0x224/0x8e0 mm/slub.c:3177 put_pid.part.4+0xe0/0x1a8 kernel/pid.c:114 put_pid+0x30/0x48 kernel/pid.c:109 proc_do_cad_pid+0x190/0x1b0 kernel/sysctl.c:1401 proc_sys_call_handler+0x338/0x4b0 fs/proc/proc_sysctl.c:591 proc_sys_write+0x34/0x48 fs/proc/proc_sysctl.c:617 call_write_iter include/linux/fs.h:1977 [inline] new_sync_write+0x3ac/0x510 fs/read_write.c:518 vfs_write fs/read_write.c:605 [inline] vfs_write+0x9c4/0x1018 fs/read_write.c:585 ksys_write+0x124/0x240 fs/read_write.c:658 __do_sys_write fs/read_write.c:670 [inline] __se_sys_write fs/read_write.c:667 [inline] __arm64_sys_write+0x78/0xb0 fs/read_write.c:667 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall arch/arm64/kernel/syscall.c:49 [inline] el0_svc_common.constprop.1+0x16c/0x388 arch/arm64/kernel/syscall.c:129 do_el0_svc+0xf8/0x150 arch/arm64/kernel/syscall.c:168 el0_svc+0x28/0x38 arch/arm64/kernel/entry-common.c:416 el0_sync_handler+0x134/0x180 arch/arm64/kernel/entry-common.c:432 el0_sync+0x154/0x180 arch/arm64/kernel/entry.S:701 The buggy address belongs to the object at ffff23794dda0000 which belongs to the cache pid of size 224 The buggy address is located 4 bytes inside of 224-byte region [ff
    ---truncated--- (CVE-2021-47118)

  - 已解決 Linux 核心中的下列弱點：i2c: i801: Don't generate an interrupt on bus reset Now that the i2c-i801 driver supports interrupts, setting the KILL bit in a attempt to recover from a timed out transaction triggers an interrupt. Unfortunately, the interrupt handler (i801_isr) is not prepared for this situation and will try to process the interrupt as if it was signaling the end of a successful transaction. In the case of a block transaction, this can result in an out-of-range memory access. This condition was reproduced several times by syzbot:
    https://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e https://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e https://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e https://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb https://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a https://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79 So disable interrupts while trying to reset the bus. Interrupts will be enabled again for the following transaction. (CVE-2021-47153)

  - 已解決 Linux 核心中的下列弱點：scsi: target: Fix WRITE_SAME No Data Buffer crash In newer version of the SBC specs, we have a NDOB bit that indicates there is no data buffer that gets written out. If this bit is set using commands like sg_write_same --ndob we will crash in target_core_iblock/file's execute_write_same handlers when we go to access the se_cmd->t_data_sg because its NULL. This patch adds a check for the NDOB bit in the common WRITE SAME code because we don't support it. And, it adds a check for zero SG elements in each handler in case the initiator tries to send a normal WRITE SAME with no data buffer. (CVE-2022-21546)

  - 已解決 Linux 核心中的下列弱點：net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent A user is able to configure an arbitrary number of rx queues when creating an interface via netlink. This doesn't work for child PKEY interfaces because the child interface uses the parent receive channels. Although the child shares the parent's receive channels, the number of rx queues is important for the channel_stats array: the parent's rx channel index is used to access the child's channel_stats. So the array has to be at least as large as the parent's rx queue size for the counting to work correctly and to prevent out of bound accesses. This patch checks for the mentioned scenario and returns an error when trying to create the interface. The error is propagated to the user. (CVE-2022-48883)

  - 已解決 Linux 核心中的下列弱點：ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix The rxstatus->rs_keyix eventually gets passed to test_bit() so we need to ensure that it is within the bitmap. drivers/net/wireless/ath/ath9k/common.c:46 ath9k_cmn_rx_accept() error: passing untrusted data 'rx_stats->rs_keyix' to 'test_bit()' (CVE-2022-49503)

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

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

    kernel-rt 套件提供即時 Linux 核心，其可針對具有極高決定機制需求的系統啟用微調。

    安全性修正：

    * 核心ALSAusb-audio也驗證 UAC3 power 網域描述元 (CVE-2025-38729)

    * 核心：ALSA：usb-audio：驗證 UAC3 叢集區段描述符號 (CVE-2025-39757)

    * 核心：mm：修復 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心：Bluetooth：L2CAP：修正 l2cap_disconnect_rsp 中的「錯誤解鎖平衡」(CVE-2023-53297)

    * 核心scsiqla2xxx終止 rport 時等待 io 傳回 (CVE-2023-53322)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心netschedsfb修正 sfb_init() 失敗時的 NULL 指標存取問題 (CVE-2022-50356)

    * 核心ext4修正 ext4_check_flag_values 位元移位中的未定義行為 (CVE-2022-50403)

    * 核心NFSD防止 NFSv2 READ 中的傳送緩衝區溢位 (CVE-2022-50410)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：tcp：清除 tcp_disconnect() 中的 tcp_sk(sk)->fastopen_rsk (CVE-2025-39955)

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

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

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

AlmaLinux 9.2 主機已安裝的套件會受到 TuxCare ALMALINUX9.2：CLSA-2026：1786350974 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：isofs: Fix out of bound access for corrupted isofs image When isofs image is suitably corrupted isofs_read_inode() can read data beyond the end of buffer. Sanity-check the directory entry length before using it. (CVE-2021-47478)

  - 已解決 Linux 核心中的下列弱點：ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl Hulk Robot reported a KASAN report about use-after-free:
    ================================================================== BUG: KASAN: use-after-free in
    __list_del_entry_valid+0x13d/0x160 Read of size 8 at addr ffff888035e37d98 by task ubiattach/1385 [...] Call Trace: klist_dec_and_del+0xa7/0x4a0 klist_put+0xc7/0x1a0 device_del+0x4d4/0xed0 cdev_device_del+0x1a/0x80 ubi_attach_mtd_dev+0x2951/0x34b0 [ubi] ctrl_cdev_ioctl+0x286/0x2f0 [ubi] Allocated by task 1414: device_add+0x60a/0x18b0 cdev_device_add+0x103/0x170 ubi_create_volume+0x1118/0x1a10 [ubi] ubi_cdev_ioctl+0xb7f/0x1ba0 [ubi] Freed by task 1385:
    cdev_device_del+0x1a/0x80 ubi_remove_volume+0x438/0x6c0 [ubi] ubi_cdev_ioctl+0xbf4/0x1ba0 [ubi] [...] ================================================================== The lock held by ctrl_cdev_ioctl is ubi_devices_mutex, but the lock held by ubi_cdev_ioctl is ubi->device_mutex. Therefore, the two locks can be concurrent. ctrl_cdev_ioctl contains two operations: ubi_attach and ubi_detach. ubi_detach is bug-free because it uses reference counting to prevent concurrency. However, uif_init and uif_close in ubi_attach may race with ubi_cdev_ioctl. uif_init will race with ubi_cdev_ioctl as in the following stack. cpu1 cpu2 cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_add_volume // sysfs exist kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // first free ubi_free_volume cdev_del // double free cdev_device_del And uif_close will race with ubi_cdev_ioctl as in the following stack. cpu1 cpu2 cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_debugfs_init_dev //error goto out_uif; uif_close kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // first free ubi_free_volume // double free The cause of this problem is that commit 714fb87e8bc0 make device available before it becomes accessible via sysfs. Therefore, we roll back the modification. We will fix the race condition between ubi device creation and udev by removing ubi_get_device in vol_attribute_show and dev_attribute_show.This avoids accessing uninitialized ubi_devices[ubi_num]. ubi_get_device is used to prevent devices from being deleted during sysfs execution. However, now kernfs ensures that devices will not be deleted before all reference counting are released. The key process is shown in the following stack. device_del device_remove_attrs device_remove_groups sysfs_remove_groups sysfs_remove_group remove_files kernfs_remove_by_name kernfs_remove_by_name_ns __kernfs_remove kernfs_drain (CVE-2021-47634)

  - 已解決 Linux 核心中的下列弱點：scsi: qla2xxx: Fix memory leak in
    __qlt_24xx_handle_abts() Commit 8f394da36a36 (scsi: qla2xxx: Drop TARGET_SCF_LOOKUP_LUN_FROM_TAG) made the __qlt_24xx_handle_abts() function return early if tcm_qla2xxx_find_cmd_by_tag() didn't find a command, but it missed to clean up the allocated memory for the management command. (CVE-2022-48650)

  - 已解決 Linux 核心中的下列弱點：ubi: ubi_create_volume: Fix use-after-free when volume creation failed There is an use-after-free problem for 'eba_tbl' in ubi_create_volume()'s error handling path: ubi_eba_replace_table(vol, eba_tbl) vol->eba_tbl = tbl out_mapping:
    ubi_eba_destroy_table(eba_tbl) // Free 'eba_tbl' out_unlock: put_device(&vol->dev) vol_release kfree(tbl->entries) // UAF Fix it by removing redundant 'eba_tbl' releasing. Fetch a reproducer in [Link].
    (CVE-2022-49388)

  - 已解決 Linux 核心中的下列弱點：irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. When kcalloc fails, it missing of_node_put() and results in refcount leak. Fix this by goto out_put_node label. (CVE-2022-49716)

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

CentOS Linux 7 主機安裝的套件會受到 TuxCare CENTOS7：CLSA-2026：1770040438 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：cifs: fix oops during encryption When running xfstests against Azure the following oops occurred on an arm64 system Unable to handle kernel write to read-only memory at virtual address ffff0001221cf000 Mem abort info: ESR = 0x9600004f EC = 0x25:
    DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x0f: level 3 permission fault Data abort info: ISV = 0, ISS = 0x0000004f CM = 0, WnR = 1 swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000294f3000 [ffff0001221cf000] pgd=18000001ffff8003, p4d=18000001ffff8003, pud=18000001ff82e003, pmd=18000001ff71d003, pte=00600001221cf787 Internal error: Oops: 9600004f [#1] PREEMPT SMP ... pstate:
    80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--) pc : __memcpy+0x40/0x230 lr :
    scatterwalk_copychunks+0xe0/0x200 sp : ffff800014e92de0 x29: ffff800014e92de0 x28: ffff000114f9de80 x27:
    0000000000000008 x26: 0000000000000008 x25: ffff800014e92e78 x24: 0000000000000008 x23: 0000000000000001 x22: 0000040000000000 x21: ffff000000000000 x20: 0000000000000001 x19: ffff0001037c4488 x18:
    0000000000000014 x17: 235e1c0d6efa9661 x16: a435f9576b6edd6c x15: 0000000000000058 x14: 0000000000000001 x13: 0000000000000008 x12: ffff000114f2e590 x11: ffffffffffffffff x10: 0000040000000000 x9 :
    ffff8000105c3580 x8 : 2e9413b10000001a x7 : 534b4410fb86b005 x6 : 534b4410fb86b005 x5 : ffff0001221cf008 x4 : ffff0001037c4490 x3 : 0000000000000001 x2 : 0000000000000008 x1 : ffff0001037c4488 x0 :
    ffff0001221cf000 Call trace: __memcpy+0x40/0x230 scatterwalk_map_and_copy+0x98/0x100 crypto_ccm_encrypt+0x150/0x180 crypto_aead_encrypt+0x2c/0x40 crypt_message+0x750/0x880 smb3_init_transform_rq+0x298/0x340 smb_send_rqst.part.11+0xd8/0x180 smb_send_rqst+0x3c/0x100 compound_send_recv+0x534/0xbc0 smb2_query_info_compound+0x32c/0x440 smb2_set_ea+0x438/0x4c0 cifs_xattr_set+0x5d4/0x7c0 This is because in scatterwalk_copychunks(), we attempted to write to a buffer (@sign) that was allocated in the stack (vmalloc area) by crypt_message() and thus accessing its remaining 8 (x2) bytes ended up crossing a page boundary. To simply fix it, we could just pass @sign kmalloc'd from crypt_message() and then we're done. Luckily, we don't seem to pass any other vmalloc'd buffers in smb_rqst::rq_iov... Instead, let's map the correct pages and offsets from vmalloc buffers as well in cifs_sg_set_buf() and then avoiding such oopses. (CVE-2022-50341)

  - 已解決 Linux 核心中的下列弱點：iomap: iomap: fix memory corruption when recording errors during writeback Every now and then I see this crash on arm64: Unable to handle kernel NULL pointer dereference at virtual address 00000000000000f8 Buffer I/O error on dev dm-0, logical block 8733687, async page read Mem abort info: ESR = 0x0000000096000006 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x06: level 2 translation fault Data abort info: ISV = 0, ISS = 0x00000006 CM = 0, WnR = 0 user pgtable: 64k pages, 42-bit VAs, pgdp=0000000139750000 [00000000000000f8] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000, pmd=0000000000000000 Internal error: Oops: 96000006 [#1] PREEMPT SMP Buffer I/O error on dev dm-0, logical block 8733688, async page read Dumping ftrace buffer: Buffer I/O error on dev dm-0, logical block 8733689, async page read (ftrace buffer empty) XFS (dm-0): log I/O error -5 Modules linked in: dm_thin_pool dm_persistent_data XFS (dm-0): Metadata I/O Error (0x1) detected at xfs_trans_read_buf_map+0x1ec/0x590 [xfs] (fs/xfs/xfs_trans_buf.c:296). dm_bio_prison XFS (dm-0): Please unmount the filesystem and rectify the problem(s) XFS (dm-0): xfs_imap_lookup: xfs_ialloc_read_agi() returned error -5, agno 0 dm_bufio dm_log_writes xfs nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_REJECT potentially unexpected fatal signal 6. nf_reject_ipv6 potentially unexpected fatal signal 6. ipt_REJECT nf_reject_ipv4 CPU: 1 PID: 122166 Comm: fsstress Tainted: G W 6.0.0-rc5-djwa #rc5 3004c9f1de887ebae86015f2677638ce51ee7 rpcsec_gss_krb5 auth_rpcgss xt_tcpudp ip_set_hash_ip ip_set_hash_net xt_set nft_compat ip_set_hash_mac ip_set nf_tables Hardware name: QEMU KVM Virtual Machine, BIOS 1.5.1 06/16/2021 pstate: 60001000 (nZCv daif -PAN -UAO -TCO -DIT +SSBS BTYPE=--) ip_tables pc : 000003fd6d7df200 x_tables lr : 000003fd6d7df1ec overlay nfsv4 CPU: 0 PID: 54031 Comm: u4:3 Tainted: G W 6.0.0-rc5-djwa #rc5 3004c9f1de887ebae86015f2677638ce51ee7405 Hardware name: QEMU KVM Virtual Machine, BIOS 1.5.1 06/16/2021 Workqueue: writeback wb_workfn sp : 000003ffd9522fd0 (flush-253:0) pstate: 60401005 (nZCv daif +PAN -UAO
    -TCO -DIT +SSBS BTYPE=--) pc : errseq_set+0x1c/0x100 x29: 000003ffd9522fd0 x28: 0000000000000023 x27:
    000002acefeb6780 x26: 0000000000000005 x25: 0000000000000001 x24: 0000000000000000 x23: 00000000ffffffff x22: 0000000000000005 lr : __filemap_set_wb_err+0x24/0xe0 x21: 0000000000000006 sp : fffffe000f80f760 x29:
    fffffe000f80f760 x28: 0000000000000003 x27: fffffe000f80f9f8 x26: 0000000002523000 x25: 00000000fffffffb x24: fffffe000f80f868 x23: fffffe000f80fbb0 x22: fffffc0180c26a78 x21: 0000000002530000 x20:
    0000000000000000 x19: 0000000000000000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000001 x13: 0000000000470af3 x12: fffffc0058f70000 x11:
    0000000000000040 x10: 0000000000001b20 x9 : fffffe000836b288 x8 : fffffc00eb9fd480 x7 : 0000000000f83659 x6 : 0000000000000000 x5 : 0000000000000869 x4 : 0000000000000005 x3 : 00000000000000f8 x20:
    000003fd6d740020 x19: 000000000001dd36 x18: 0000000000000001 x17: 000003fd6d78704c x16: 0000000000000001 x15: 000002acfac87668 x2 : 0000000000000ffa x1 : 00000000fffffffb x0 : 00000000000000f8 Call trace:
    errseq_set+0x1c/0x100 __filemap_set_wb_err+0x24/0xe0 iomap_do_writepage+0x5e4/0xd5c write_cache_pages+0x208/0x674 iomap_writepages+0x34/0x60 xfs_vm_writepages+0x8c/0xcc [xfs 7a861f39c43631f15d3a5884246ba5035d4ca78b] x14: 0000000000000000 x13: 2064656e72757465 x12:
    0000000000002180 x11: 000003fd6d8a82d0 x10: 0000000000000000 x9 : 000003fd6d8ae288 x8 : 0000000000000083 x7 : 00000000ffffffff x6 : 00000000ffffffee x5 : 00000000fbad2887 x4 : 000003fd6d9abb58 x3 :
    000003fd6d740020 x2 : 0000000000000006 x1 : 000000000001dd36 x0 : 0000000000000000 CPU: ---truncated--- (CVE-2022-50406)

  - 已解決 Linux 核心中的下列弱點：Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times device_add shall not be called multiple times as stated in its documentation: 'Do not call this routine or device_register() more than once for any device structure' Syzkaller reports a bug as follows [1]: ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:33! invalid opcode: 0000 [#1] PREEMPT SMP KASAN [...] Call Trace: <TASK> __list_add include/linux/list.h:69 [inline] list_add_tail include/linux/list.h:102 [inline] kobj_kset_join lib/kobject.c:164 [inline] kobject_add_internal+0x18f/0x8f0 lib/kobject.c:214 kobject_add_varg lib/kobject.c:358 [inline] kobject_add+0x150/0x1c0 lib/kobject.c:410 device_add+0x368/0x1e90 drivers/base/core.c:3452 hci_conn_add_sysfs+0x9b/0x1b0 net/bluetooth/hci_sysfs.c:53 hci_le_cis_estabilished_evt+0x57c/0xae0 net/bluetooth/hci_event.c:6799 hci_le_meta_evt+0x2b8/0x510 net/bluetooth/hci_event.c:7110 hci_event_func net/bluetooth/hci_event.c:7440 [inline] hci_event_packet+0x63d/0xfd0 net/bluetooth/hci_event.c:7495 hci_rx_work+0xae7/0x1230 net/bluetooth/hci_core.c:4007 process_one_work+0x991/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> (CVE-2022-50419)

  - 已解決 Linux 核心中的下列弱點：scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() When executing SMP task failed, the smp_execute_task_sg() calls del_timer() to delete slow_task->timer. However, if the timer handler sas_task_internal_timedout() is running, the del_timer() in smp_execute_task_sg() will not stop it and a UAF will happen. The process is shown below:
    (thread 1) | (thread 2) smp_execute_task_sg() | sas_task_internal_timedout() ... | del_timer() | ... | ...
    sas_free_task(task) | kfree(task->slow_task) //FREE| | task->slow_task->... //USE Fix by calling del_timer_sync() in smp_execute_task_sg(), which makes sure the timer handler have finished before the task->slow_task is deallocated. (CVE-2022-50422)

  - 已解決 Linux 核心中的下列弱點：scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write During the sysfs firmware write process, a use-after-free read warning is logged from the lpfc_wr_object() routine: BUG: KFENCE: use-after-free read in lpfc_wr_object+0x235/0x310 [lpfc] Use-after-free read at 0x0000000000cf164d (in kfence-#111):
    lpfc_wr_object+0x235/0x310 [lpfc] lpfc_write_firmware.cold+0x206/0x30d [lpfc] lpfc_sli4_request_firmware_update+0xa6/0x100 [lpfc] lpfc_request_firmware_upgrade_store+0x66/0xb0 [lpfc] kernfs_fop_write_iter+0x121/0x1b0 new_sync_write+0x11c/0x1b0 vfs_write+0x1ef/0x280 ksys_write+0x5f/0xe0 do_syscall_64+0x59/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd The driver accessed wr_object pointer data, which was initialized into mailbox payload memory, after the mailbox object was released back to the mailbox pool. Fix by moving the mailbox free calls to the end of the routine ensuring that we don't reference internal mailbox memory after release. (CVE-2023-53282)

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

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

  - 已解決 Linux 核心中的下列弱點：pid: take a reference when initializing `cad_pid` During boot, kernel_init_freeable() initializes `cad_pid` to the init task's struct pid. Later on, we may change `cad_pid` via a sysctl, and when this happens proc_do_cad_pid() will increment the refcount on the new pid via get_pid(), and will decrement the refcount on the old pid via put_pid(). As we never called get_pid() when we initialized `cad_pid`, we decrement a reference we never incremented, can therefore free the init task's struct pid early. As there can be dangling references to the struct pid, we can later encounter a use-after-free (e.g. when delivering signals). This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to have been around since the conversion of `cad_pid` to struct pid in commit 9ec52099e4b8 ([PATCH] replace cad_pid by a struct pid) from the pre-KASAN stone age of v2.6.19. Fix this by getting a reference to the init task's struct pid when we assign it to `cad_pid`.
    Full KASAN splat below. ================================================================== BUG: KASAN:
    use-after-free in ns_of_pid include/linux/pid.h:153 [inline] BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273 CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1 Hardware name: linux,dummy-virt (DT) Call trace: ns_of_pid include/linux/pid.h:153 [inline] task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 do_notify_parent+0x308/0xe60 kernel/signal.c:1950 exit_notify kernel/exit.c:682 [inline] do_exit+0x2334/0x2bd0 kernel/exit.c:845 do_group_exit+0x108/0x2c8 kernel/exit.c:922 get_signal+0x4e4/0x2a88 kernel/signal.c:2781 do_signal arch/arm64/kernel/signal.c:882 [inline] do_notify_resume+0x300/0x970 arch/arm64/kernel/signal.c:936 work_pending+0xc/0x2dc Allocated by task 0: slab_post_alloc_hook+0x50/0x5c0 mm/slab.h:516 slab_alloc_node mm/slub.c:2907 [inline] slab_alloc mm/slub.c:2915 [inline] kmem_cache_alloc+0x1f4/0x4c0 mm/slub.c:2920 alloc_pid+0xdc/0xc00 kernel/pid.c:180 copy_process+0x2794/0x5e18 kernel/fork.c:2129 kernel_clone+0x194/0x13c8 kernel/fork.c:2500 kernel_thread+0xd4/0x110 kernel/fork.c:2552 rest_init+0x44/0x4a0 init/main.c:687 arch_call_rest_init+0x1c/0x28 start_kernel+0x520/0x554 init/main.c:1064 0x0 Freed by task 270:
    slab_free_hook mm/slub.c:1562 [inline] slab_free_freelist_hook+0x98/0x260 mm/slub.c:1600 slab_free mm/slub.c:3161 [inline] kmem_cache_free+0x224/0x8e0 mm/slub.c:3177 put_pid.part.4+0xe0/0x1a8 kernel/pid.c:114 put_pid+0x30/0x48 kernel/pid.c:109 proc_do_cad_pid+0x190/0x1b0 kernel/sysctl.c:1401 proc_sys_call_handler+0x338/0x4b0 fs/proc/proc_sysctl.c:591 proc_sys_write+0x34/0x48 fs/proc/proc_sysctl.c:617 call_write_iter include/linux/fs.h:1977 [inline] new_sync_write+0x3ac/0x510 fs/read_write.c:518 vfs_write fs/read_write.c:605 [inline] vfs_write+0x9c4/0x1018 fs/read_write.c:585 ksys_write+0x124/0x240 fs/read_write.c:658 __do_sys_write fs/read_write.c:670 [inline] __se_sys_write fs/read_write.c:667 [inline] __arm64_sys_write+0x78/0xb0 fs/read_write.c:667 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall arch/arm64/kernel/syscall.c:49 [inline] el0_svc_common.constprop.1+0x16c/0x388 arch/arm64/kernel/syscall.c:129 do_el0_svc+0xf8/0x150 arch/arm64/kernel/syscall.c:168 el0_svc+0x28/0x38 arch/arm64/kernel/entry-common.c:416 el0_sync_handler+0x134/0x180 arch/arm64/kernel/entry-common.c:432 el0_sync+0x154/0x180 arch/arm64/kernel/entry.S:701 The buggy address belongs to the object at ffff23794dda0000 which belongs to the cache pid of size 224 The buggy address is located 4 bytes inside of 224-byte region [ff
    ---truncated--- (CVE-2021-47118)

  - 已解決 Linux 核心中的下列弱點：i2c: i801: Don't generate an interrupt on bus reset Now that the i2c-i801 driver supports interrupts, setting the KILL bit in a attempt to recover from a timed out transaction triggers an interrupt. Unfortunately, the interrupt handler (i801_isr) is not prepared for this situation and will try to process the interrupt as if it was signaling the end of a successful transaction. In the case of a block transaction, this can result in an out-of-range memory access. This condition was reproduced several times by syzbot:
    https://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e https://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e https://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e https://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb https://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a https://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79 So disable interrupts while trying to reset the bus. Interrupts will be enabled again for the following transaction. (CVE-2021-47153)

  - 已解決 Linux 核心中的下列弱點：scsi: target: Fix WRITE_SAME No Data Buffer crash In newer version of the SBC specs, we have a NDOB bit that indicates there is no data buffer that gets written out. If this bit is set using commands like sg_write_same --ndob we will crash in target_core_iblock/file's execute_write_same handlers when we go to access the se_cmd->t_data_sg because its NULL. This patch adds a check for the NDOB bit in the common WRITE SAME code because we don't support it. And, it adds a check for zero SG elements in each handler in case the initiator tries to send a normal WRITE SAME with no data buffer. (CVE-2022-21546)

  - 已解決 Linux 核心中的下列弱點：net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent A user is able to configure an arbitrary number of rx queues when creating an interface via netlink. This doesn't work for child PKEY interfaces because the child interface uses the parent receive channels. Although the child shares the parent's receive channels, the number of rx queues is important for the channel_stats array: the parent's rx channel index is used to access the child's channel_stats. So the array has to be at least as large as the parent's rx queue size for the counting to work correctly and to prevent out of bound accesses. This patch checks for the mentioned scenario and returns an error when trying to create the interface. The error is propagated to the user. (CVE-2022-48883)

  - 已解決 Linux 核心中的下列弱點：be2net: Fix buffer overflow in be_get_module_eeprom be_cmd_read_port_transceiver_data assumes that it is given a buffer that is at least PAGE_DATA_LEN long, or twice that if the module supports SFF 8472. However, this is not always the case.
    Fix this by passing the desired offset and length to be_cmd_read_port_transceiver_data so that we only copy the bytes once. (CVE-2022-49581)

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
265505	Linux Distros 未修補的弱點：CVE-2022-50406	Nessus	Misc.	2025/9/19	2026/9/30	high
275173	RHEL 9：kernel-rt (RHSA-2025:21136)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
278028	RHEL 8：核心 (RHSA-2025:22998)	Nessus	Red Hat Local Security Checks	2025/12/10	2026/2/25	high
279558	RHEL 7: 核心 (RHSA-2025:23947)	Nessus	Red Hat Local Security Checks	2025/12/22	2026/2/20	high
274973	RHEL 8：核心 (RHSA-2025:21084)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
274937	RHEL 9：核心 (RHSA-2025:21051)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
275174	RHEL 9：核心 (RHSA-2025:21091)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
275176	RHEL 9：kernel-rt (RHSA-2025:21128)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
278950	RHEL 8：核心 (RHSA-2025:23445)	Nessus	Red Hat Local Security Checks	2025/12/17	2025/12/17	high
279030	RHEL 8：核心 (RHSA-2025:23463)	Nessus	Red Hat Local Security Checks	2025/12/17	2026/2/23	high
361173	CentOS Linux 8.4 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc 多個弱點（CENTOS8.4：CLSA-2026：1771078945）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
279557	RHEL 7：kernel-rt (RHSA-2025:23960)	Nessus	Red Hat Local Security Checks	2025/12/22	2026/2/20	high
360716	AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / etc 多個弱點（ALMALINUX9.2：CLSA-2026：1786350974）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	high
360828	CentOS Linux 7 [TuxCare] 安全性更新：bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc 多個弱點（CENTOS7：CLSA-2026：1770040438）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
360928	CentOS Linux 8.5 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc多個弱點（CENTOS8.5：CLSA-2026：1771077729）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high

偵測

搜尋 Plugin

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high