遠端主機上安裝的核心版本早於 5.4.129-62.227。因此，會受到 ALAS2KERNEL-54-2022-004 公告中所提及的多個弱點影響。

    在 Linux 核心的 WiFi 片段處理實作中發現一個缺陷。能夠在存取點的無線傳輸範圍內傳輸的攻擊者可以濫用此缺陷，將先前的 WiFi 片段內容意外傳輸到另一個裝置。(CVE-2020-24586)

    在 Linux 核心的 WiFi 實作中發現一個缺陷。位於無線範圍內的攻擊者可濫用 WiFi 實作中的邏輯缺陷，重組不同金鑰下多個片段中的封包，並將其視為有效。此缺陷允許攻擊者傳送錯誤金鑰下的片段，並將其視為新金鑰下的有效片段。此弱點對機密性的威脅最大。(CVE-2020-24587)

    在 Linux 核心的 WiFi 實作中發現一個缺陷。位於無線廣播範圍內的攻擊者可將自訂資料插入無線通訊，以規避資料檢查。這可造成幀通過檢查，並被視為不同類型的有效幀。(CVE-2020-24588)

    幀用於 AP 和所連用戶端之間的驗證和金鑰管理，部分用戶端可能會將這些重新導向的幀偽裝成來自 AP 的控制機制。(CVE-2020-26139)

    在 Linux 核心的 WiFi 實作中發現一個弱點。位於無線範圍內的攻擊者可插入控制封包片段，此時核心不會驗證片段化 TKIP 幀的訊息完整性檢查 (真實性)。(CVE-2020-26141)

    在 Linux 核心的 WiFi 實作中，發現 drivers/net/wireless/ath/ath10k/htt_rx.c 的 ath10k_htt_rx_proc_rx_frag_ind_hl 中存在缺陷，內核會接受第二個 (或後續) 廣播片段 (即使以純文字傳送)，然後將其視為完整的未片段化幀處理。此弱點對完整性的威脅最大。(CVE-2020-26145)

    在 Linux 核心的 WiFi 實作中，發現 net/mac80211/rx.c 的 ieee80211_rx_h_defragment 中存在缺陷。攻擊者可利用此弱點，在其他裝置傳送片段化幀並使用 WEP、CCMP 或 GCMP 資料機密通訊協定時，插入封包和/或洩漏所選片段。
    此弱點對完整性的威脅最大。(CVE-2020-26147)

    在 Linux 核心的 certs/blacklist.c 中發現一個缺陷。當 EFI_CERT_X509_GUID 的簽章項目包含在 Secure Boot Forbidden Signature Database 中時，系統會略過這些項目。這可造成安全性威脅，並破壞系統的完整性和機密性，甚至導致拒絕服務問題。
    (CVE-2020-26541)

    在 bluez 中發現一個弱點，即藍牙核心規格的安全簡易配對 (SSP)、安全連線 (SC) 和 LE 安全連線 (LESC) 中使用的 Passkey Entry 通訊協定容易受到假冒攻擊，主動攻擊者可在先前不知情的情況下假冒啟動裝置。(CVE-2020-26558)

    在 Linux 核心中發現一個缺陷。BlueZ 中的不當存取控制可能會允許經驗證的使用者透過相鄰存取造成資訊洩漏。此弱點對資料機密性與完整性的威脅最大。(CVE-2021-0129)

    - 在 Linux 核心的 KVM 實作中發現一個缺陷，由於對 KVM 中的 VM_IO|VM_PFNMAP vmas 處理不當，此缺陷可造成使用者繞過 RO 檢查，並導致頁面被釋放，但 VMM 和來賓仍可存取頁面。
    這讓能夠啟動和控制 VM 的使用者可以讀取/寫入隨機的記憶體頁面，並可能導致本機特權提升。此弱點對機密性、完整性以及系統可用性的威脅最大。(CVE-2021-22543)

    在 Linux 核心處理藍牙 HCI 控制器移除的方式中發現一個缺陷。此缺陷允許擁有本機帳戶的攻擊者利用爭用條件來造成記憶體損毀，並可能提升權限。此弱點對於機密性、完整性以及系統可用性的威脅最大。(CVE-2021-32399)

    在 Linux 核心的藍牙主機控制器介面 (HCI) 的 hci_send_acl 中發現釋放後使用缺陷，具有存取權限的本機攻擊者可在系統上造成拒絕服務問題。產生此問題的原因是物件 hchan 已在 hci_disconn_loglink_complete_evt 中釋放，但仍在其他地方使用。此弱點對資料完整性、機密性以及系統可用性的威脅最大。(CVE-2021-33034)

    Linux 核心的 canbus 檔案系統包含資訊洩漏弱點，可導致核心記憶體中的資訊洩漏給 CAN 匯流排網路連結層上的裝置。能夠在 CAN 匯流排上轉儲存訊息的攻擊者可藉由轉儲存 CAN 匯流排上的訊息，得知未初始化的堆疊值。(CVE-2021-34693)

    在 Linux 核心的 f2fs 模組的 fs/f2fs/node.c 中發現超出邊界 (OOB) 記憶體存取缺陷。邊界檢查失敗允許本機攻擊者取得超出邊界存取記憶體的權限，進而導致系統損毀或內部核心資訊洩漏。此弱點對系統可用性威脅最大。(CVE-2021-3506)

    在 Linux 核心的 HCI 裝置初始化子系統中發現重複釋放記憶體損毀缺陷，此缺陷與使用者附加惡意 HCI TTY 藍牙裝置的方式有關。本機使用者可利用此缺陷造成系統當機。(CVE-2021-3564)

    在使用者呼叫 ioct HCIUNBLOCKADDR 的方式中，或是其他觸發呼叫 hci_unregister_dev() 以及呼叫 hci_sock_blacklist_add()、hci_sock_blacklist_del()、hci_get_conn_info()、hci_get_auth_info() 之一的爭用情形的方式中，發現 Linux 核心 HCI 子系統的 hci_sock_bound_ioctl() 函式中存在釋放後使用問題。本機特權使用者可利用此缺陷來造成系統損毀，或提高自己的系統權限。(CVE-2021-3573)

    在 Linux 核心的 NFC 實作中發現一個缺陷。本機非特權使用者可觸發 NULL 指標解除參照和可導致拒絕服務的錯誤，造成核心錯誤。(CVE-2021-38208)

    在 Linux 核心中，下列弱點已解決：

    HID: usbhid：修復 hid_submit_ctrl 中的資訊洩漏問題

    在 hid_submit_ctrl() 中，計算報告長度的方式未將 report->size 可能為零的情況納入考量。執行 syzkaller 再生器時，大小為 0 的報告會導致 hid_submit_ctrl) 將 transfer_buffer_length 計算為 16384。將此 urb 傳遞至 usb 核心層時，KMSAN 會報告 16384 位元組的資訊洩漏問題。

    若要修復此問題，請先修改 hid_report_len()，使用除數的 DIV_ROUND_UP 來解決報告大小為零的情況。然後，再從 hid_submit_ctrl() 呼叫它。(CVE-2021-46906)

    在 Linux 核心中，下列弱點已解決：

    dm rq：修復表格載入失敗後 dev remove 中的 blk_mq_tag_set 重複釋放的問題 (CVE-2021-46938)

    在 Linux 核心中，下列弱點已解決：

    tracing：將 trace_clock_global() 重組為從不封鎖 (CVE-2021-46939)

    在 Linux 核心中，下列弱點已解決：

    md/raid1：結束失敗的寫入要求時正確指示失敗

    此修補程式可使用點陣圖解決 raid1 陣列中的資料損毀錯誤。若無此修復，失敗 I/O 的點陣圖位元最終會遭到清除。

    由於我們處於 raid1_end_write_request 的失敗分支中，因此要求需要為重試 (R1BIO_WriteError) 或失敗 (R1BIO_Degraded) 狀態。 (CVE-2021-46950)

    在 Linux 核心中，下列弱點已解決：

    tpm：efi：使用本機變數計算最終記錄大小 (CVE-2021-46951)

    在 Linux 核心中，下列弱點已解決：

    ACPI：GTDT：watchdow 探查失敗時不損毀中斷對應 (CVE-2021-46953)

    在 Linux 核心中，下列弱點已解決：

    openvswitch：修復分割 IPv4 封包時的堆疊 OOB 讀取問題 (CVE-2021-46955)

    在 Linux 核心中，下列弱點已解決：

    virtiofs：修復 virtio_fs_probe() 中的記憶體流失問題 (CVE-2021-46956)

    在 Linux 核心中，下列弱點已解決：

    spi：修正 devm_spi_alloc_* 的釋放後使用 (CVE-2021-46959)

    在 Linux 核心中，下列弱點已解決：

    cifs：從 smb2_get_enc_key 傳回正確的錯誤碼 (CVE-2021-46960)

    在 Linux 核心中，下列弱點已解決：

    irqchip/gic-v3：處理假性中斷時不啟用 irqs (CVE-2021-46961)

    在 Linux 核心中，下列弱點已解決：

    scsi：qla2xxx：修復 qla2xxx_mqueuecommand() 中的損毀問題 (CVE-2021-46963)

    在 Linux 核心中，下列弱點已解決：

    nbd：修復 flush_workqueue 中的 NULL 指標 (CVE-2021-46981)

    在 Linux 核心中，下列弱點已解決：

    kyber：修正先佔時的超出邊界存取問題 (CVE-2021-46984)

    在 Linux 核心中，下列弱點已解決：

    ACPI：掃描：修復錯誤處理路徑中的記憶體流失問題 (CVE-2021-46985)

    在 Linux 核心中，下列弱點已解決：

    userfaultfd釋放錯誤路徑中的頁面以避免 BUG_ON (CVE-2021-46988)

    在 Linux 核心中，下列弱點已解決：

    hfsplus防止縮小截斷時發生損毀 (CVE-2021-46989)

    在 Linux 核心中，下列弱點已解決：

    i40e：修正 i40e_client_subtask() 中的釋放後使用 (CVE-2021-46991)

    在 Linux 核心中，下列弱點已解決：

    netfilter：nftables：避免 nft_hash_buckets() 中的溢位 (CVE-2021-46992)

    在 Linux 核心中，下列弱點已解決：

    sched：修復 uclamp 中的超出邊界存取問題 (CVE-2021-46993)

    在 Linux 核心中，下列弱點已解決：

    sctp：在 sctp_sf_do_dupcook_a 中提早執行 asoc 更新 (CVE-2021-46999)

    在 Linux 核心中，下列弱點已解決：

    ceph：修復 __fh_to_dentry 中因 getattr 錯誤導致的 inode 洩漏問題 (CVE-2021-47000)

    在 Linux 核心中，下列弱點已解決：

    ARM：9064/1：hw_breakpoint：不直接檢查事件的 overflow_handler 勾點 (CVE-2021-47006)

    在 Linux 核心中，下列弱點已解決：

    net：僅允許 init netns 將預設 tcp cong 設定為受限制的 algo (CVE-2021-47010)

    在 Linux 核心中，下列弱點已解決：

    net:emac/emac-mac：修復 emac_mac_tx_buf_send 中的釋放後使用問題 (CVE-2021-47013)

    在 Linux 核心中，下列弱點已解決：

    bnxt_en：修復錯誤路徑中的 RX 消費者索引邏輯。(CVE-2021-47015)

    在 Linux 核心中，下列弱點已解決：

    匯流排：qcom：在傳回前放置子節點 (CVE-2021-47054)

    在 Linux 核心中，下列弱點已解決：

    mtd：需要取得鎖定和 badblock ioctl 的寫入權限 (CVE-2021-47055)

    在 Linux 核心中，下列弱點已解決：

    regmap：在釋放 debugfs_name 後將其設為 NULL (CVE-2021-47058)

    在 Linux 核心中，下列弱點已解決：

    KVM：如果匯流排損毀，停止尋找合併的 MMIO 區域 (CVE-2021-47060)

    在 Linux 核心中，下列弱點已解決：

    uio_hv_generic：修正錯誤處理路徑中的記憶體流失 (CVE-2021-47071)

    在 Linux 核心中，下列弱點已解決：

    RDMA/rxe：如果建立失敗，則清除所有 QP 欄位 (CVE-2021-47078)

    在 Linux 核心中，下列弱點已解決：

    neighbour：允許強制對 NUD_NOARP 項目進行 GC (CVE-2021-47109)

    在 Linux 核心中，下列弱點已解決：

    x86/kvm：關機時停用所有 CPU 上的 kvmclock (CVE-2021-47110)

    在 Linux 核心中，下列弱點已解決：

    x86/kvm：也卸除啟動 CPU 上的 PV 功能 (CVE-2021-47112)

    在 Linux 核心中，下列弱點已解決：

    ext4：修正 ext4_es_cache_extent 中因為 ext4_split_extent_at 失敗而出現的錯誤 (CVE-2021-47117)

    在 Linux 核心中，下列弱點已解決：

    pid：在初始化 `cad_pid` 時進行參照 (CVE-2021-47118)

    在 Linux 核心中，下列弱點已解決：

    HID：magicmouse：修正中斷連線時的 NULL 解除參照 (CVE-2021-47120)

    在 Linux 核心中，下列弱點已解決：

    ipv6：修正 KASAN：fib6_nh_flush_exceptions 中的 Slab 越界讀取 (CVE-2021-47126)

    在 Linux 核心中，下列弱點已解決：

    netfilter：nft_ct：略過已確認 conntrack 的預期 (CVE-2021-47129)

    在 Linux 核心中，下列弱點已解決：

    cxgb4：避免在清除篩選器時存取暫存器 (CVE-2021-47138)

    在 Linux 核心中，下列弱點已解決：

    drm/amdgpu：修正釋放後使用錯誤 (CVE-2021-47142)

    在 Linux 核心中，下列弱點已解決：

    btrfs：不在 link_to_fixup_dir 中執行 BUG_ON (CVE-2021-47145)

    在 Linux 核心中，下列弱點已解決：

    mld：修正 mld_newpack() 中的嚴重錯誤 (CVE-2021-47146)

    在 Linux 核心中，下列弱點已解決：

    net：dsa：修正 ->get_sset_count() 失敗時當機的情形 (CVE-2021-47159)

    在 Linux 核心中，下列弱點已解決：

    tipc：重組 msg 時針對主要 skb 進行 skb_linearize (CVE-2021-47162)

    在 Linux 核心中，下列弱點已解決：

    tipc：等待並結束，直到完成所有工作佇列 (CVE-2021-47163)

    在 Linux 核心中，下列弱點已解決：

    NFS：不損毀 nfs_do_recoalesce() 中 pg_bytes_written 的值 (CVE-2021-47166)

    在 Linux 核心中，下列弱點已解決：

    NFS：修正 __nfs_pageio_add_request() 中的 Oopsable 條件 (CVE-2021-47167)

    在 Linux 核心中，下列弱點已解決：

    NFS：修正 filelayout_decode_layout() 中的錯誤限制 (CVE-2021-47168)

    在 Linux 核心中，下列弱點已解決：

    USB：usbfs：不針對過大的記憶體配置發出警告 (CVE-2021-47170)

    在 Linux 核心中，下列弱點已解決：

    net：usb：修正 smsc75xx_bind 中的記憶體流失 (CVE-2021-47171)

    在 Linux 核心中，下列弱點已解決：

    iommu/vt-d：修正 alloc_iommu() 中的 sysfs 洩漏 (CVE-2021-47177)

    在 Linux 核心中，下列弱點已解決：

    netbridge修正傳出時的 vlan 通道 dst refcnt (CVE-2021-47222)

    在 Linux 核心中，下列弱點已解決：

    netbridge修正 vlan 通道 dst null 指標解除參照 (CVE-2021-47223)

    在 Linux 核心中，下列弱點已解決：

    KVMx86SMM 旗標清除時立即重設 MMU 內容 (CVE-2021-47230)

    在 Linux 核心中，下列弱點已解決：

    netcdc_eem修正 tx fixup skb 洩漏 (CVE-2021-47236)

    在 Linux 核心中，下列弱點已解決：

    netipv4修正 ip_mc_add1_src 中的記憶體洩漏 (CVE-2021-47238)

    在 Linux 核心中，下列弱點已解決：

    netfilter：synproxy：修正剖析 TCP 選項時的超出邊界 (CVE-2021-47245)

    在 Linux 核心中，下列弱點已解決：

    net/mlx5e修正無作用對等髮夾的頁面回收 (CVE-2021-47246)

    在 Linux 核心中，下列弱點已解決：

    udp修正 close() 和 udp_abort() 之間的爭用 (CVE-2021-47248)

    在 Linux 核心中，下列弱點已解決：

    netrds修正 rds_recvmsg 中的記憶體洩漏 (CVE-2021-47249)

    在 Linux 核心中，下列弱點已解決：

    netipv4修正 netlbl_cipsov4_add_std 中的記憶體洩漏 (CVE-2021-47250)

    在 Linux 核心中，下列弱點已解決：

    gfs2：修復 gfs2_glock_shrink_scan 中的釋放後使用問題 (CVE-2021-47254)

    在 Linux 核心中，下列弱點已解決：

    kvmLAPIC還原防護以防止非法 APIC 暫存器存取 (CVE-2021-47255)

    在 Linux 核心中，下列弱點已解決：

    mm/memory-failure：確保在 memory_failure 中等待頁面回寫 (CVE-2021-47256)

    在 Linux 核心中，下列弱點已解決：

    scsi核心修正 scsi_host_alloc() 的錯誤處理 (CVE-2021-47258)

    在 Linux 核心中，下列弱點已解決：

    NFS：修正 nfs4_init_client() 中的使用已釋放記憶體 (CVE-2021-47259)

    在 Linux 核心中，下列弱點已解決：

    NFS修正 nfs_get_client() 中可能的 NULL 解除參照 (CVE-2021-47260)

    在 Linux 核心中，下列弱點已解決：

    IB/mlx5：修正初始化 CQ 片段緩衝區 (CVE-2021-47261)

    在 Linux 核心中，下列弱點已解決：

    KVM：x86：確保巢狀 VM-Enter 失敗追踪點訊息的活躍度 (CVE-2021-47262)

    在 Linux 核心中，下列弱點已解決：

    RDMA/ipoib：修正因損毀非初始 netns 而產生的警告 (CVE-2021-47266)

    在 Linux 核心中，下列弱點已解決：

    追踪：更正導致記憶體損毀的長度檢查 (CVE-2021-47274)

    在 Linux 核心中，下列弱點已解決：

    ftrace不要盲目讀取 ftrace_bug() 中的 ip 位址 (CVE-2021-47276)

    在 Linux 核心中，下列弱點已解決：

    kvm避免超出範圍 memslot 存取造成的推測型攻擊 (CVE-2021-47277)

    在 Linux 核心中，下列弱點已解決：

    drm：修復 drm_getunique() 中的釋放後使用讀取問題 (CVE-2021-47280)

Tenable 已直接從所測試產品的安全公告擷取前置描述區塊。

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

远程主机上安装的内核版本低于 5.4.129-62.227。因此，会受到 ALAS2KERNEL-5.4-2022-004 公告中提及的多个漏洞影响。

    在 Linux 内核的 WIFI 碎片处理实现中发现一个缺陷。能够在接入点的无线传输范围内进行传输的攻击者可滥用缺陷，于无意间将之前的 WiFi 片段内容传输至另一设备。(CVE-2020-24586)

    在 Linux 内核的 WiFi 实现中发现了一个缺陷。无线传输范围内的攻击者可以重组来自不同密钥下多个片段的数据包并将其视为有效，以此滥用 WiFi 实现中的逻辑缺陷。此缺陷允许攻击者发送错误密钥下的片段，并将之视为新密钥下的有效片段。此漏洞最主要的威胁对象是机密性。(CVE-2020-24587)

    在 Linux 内核的 WiFi 实现中发现了一个缺陷。无线广播范围内的攻击者可将自定义数据注入能避开数据检查的无线通信中。这可造成帧通过检查，并被视为不同类型的有效帧。(CVE-2020-24588)

    用于 AP 和被连接客户端之间身份验证和密钥管理的帧。某些客户端可能会将这些冒充的重定向帧视为 AP 的控制机制。(CVE-2020-26139)

    在 Linux 内核的 WiFi 实现中发现了一个漏洞。在无线范围内的攻击者可注入控制数据包片段，这时内核不会验证片段化 TKIP 帧的消息完整性检查（真实性）。(CVE-2020-26141)

    在 Linux 内核的 WiFi 实现中，发现 drivers/net/wireless/ath/ath10k/htt_rx.c 的 ath10k_htt_rx_proc_rx_frag_ind_hl 中包含一个缺陷，内核会接受第二个（或后续的）广播碎片（即使以明文发送），然后将其作为完整的未碎片化帧进行处理。此漏洞最主要的威胁对象是数据完整性。(CVE-2020-26145)

    在 Linux 内核的 WiFi 实现中，发现 net/mac80211/rx.c 的 ieee80211_rx_h_defragment 中包含一个缺陷。当其他设备发送碎片化帧且使用了 WEP、CCMP 或 GCMP 数据机密协议时，恶意用户可利用此漏洞来注入数据包和/或泄露选中的碎片。
    此漏洞最主要的威胁对象是数据完整性。(CVE-2020-26147)

    在 Linux 内核中的 certs/blacklist.c 中发现了一个缺陷。当安全启动禁止签名数据库中包含 EFI_CERT_X509_GUID 的签名条目时，系统会跳过该条目。这可造成安全威胁，并破坏系统的完整性和机密性，甚至可能导致拒绝服务问题。
    (CVE-2020-26541)

    在 bluez 中发现一个漏洞，蓝牙核心规范的安全简单配对 (SSP)、安全连接 (SC) 和 LE 安全连接 (LESC) 中使用的密码输入协议容易受到假冒攻击，主动攻击者可以在事先不知情的情况下冒充启动设备。(CVE-2020-26558)

    在 Linux 内核中发现一个缺陷。BlueZ 中存在访问控制不当问题，使经过身份验证的用户可以通过邻近访问造成信息泄露。此漏洞最主要的威胁对象是数据机密性和完整性。(CVE-2021-0129)

    在 Linux 内核的 KVM 实现中发现了一个缺陷，这是由程序对 KVM 中的 VM_IO|VM_PFNMAP vmas 处理不当造成。此问题可造成用户绕过 RO 检查，并导致页面在 VMM 和来宾机仍可访问时被释放。
    能够启动和控制 VM 的用户可以利用此缺陷来读取/写入随机内存页面，进而导致本地特权提升。此漏洞最主要的威胁对象是机密性、完整性，以及系统可用性。(CVE-2021-22543)

    在 Linux 内核处理 Bluetooth HCI 控制器删除的过程中发现缺陷。此缺陷允许具有本地帐户的攻击者利用争用情形，导致内存损坏并可能提升特权。此漏洞最大的威胁在于机密性、完整性，以及系统可用性。(CVE-2021-32399)

    在 Linux 内核的蓝牙主机控制器接口 (HCI) 的 hci_send_acl 中发现了一个释放后使用缺陷，具有访问权限的本地攻击者可在系统上造成拒绝服务问题。此问题源于对象 hchan 已在 hci_disconn_loglink_complete_evt 中释放，但仍在其他地方使用。此漏洞对数据完整性、机密性和系统可用性威胁最大。(CVE-2021-33034)

    Linux 内核中的 canbus 文件系统包含信息泄漏漏洞，内核内存中的信息会泄露给 CAN 总线网络链路层上的设备。能够在 CAN 总线上转储消息的攻击者可通过转储 can 总线上的消息来了解未初始化的堆栈值。(CVE-2021-34693)

    在 Linux 内核中 f2fs 模块的 fs/f2fs/node.c 中发现越界 (OOB) 内存访问缺陷。由于边界检查失败，本地攻击者可获取越界内存的访问权限，从而导致系统崩溃或内部内核信息泄露。此漏洞最大的威胁在于系统可用性。(CVE-2021-3506)

    在用户连接恶意 HCI TTY 蓝牙设备的方式中，发现 Linux 内核 HCI 设备初始化子系统中存在双重释放内存损坏缺陷。本地用户可利用此缺陷导致系统崩溃。(CVE-2021-3564)

    在用户调用 ioct HCIUNBLOCKADDR 的方式中或触发 hci_unregister_dev() 调用以及 hci_sock_blacklist_add()、hci_sock_blacklist_del()、hci_get_conn_info()、hci_get_auth_info() 调用之一的争用情形的方式中，发现 Linux 内核 HCI 子系统的 hci_sock_bound_ioctl() 函数中存在一个释放后使用漏洞。具有特权的本地用户可利用此缺陷造成系统崩溃，或提升其在系统中的特权。(CVE-2021-3573)

    在 Linux 内核的 NFC 实现中发现了一个缺陷，本地非特权用户可触发空指针取消引用和能够导致拒绝服务的 BUG，从而造成内核错误。(CVE-2021-38208)

    在 Linux 内核中，以下漏洞已修复：

    HID：usbhid：修复 hid_submit_ctrl 中的信息泄漏漏洞

    在 hid_submit_ctrl() 中，计算报告长度的方式未考虑 report->size 可以为零的情况。运行 syzkaller 复制器时，大小为 0 的报告会造成 hid_submit_ctrl) 将 transfer_buffer_length 计算为 16384。将此 urb 传递到 usb 核心层时，KMSAN 会报告 16384 字节的信息泄漏。

    若要修复此问题，请首先修改 hid_report_len()，通过在除法中使用 DIV_ROUND_UP 来说明报告大小为零的情况。然后，从 hid_submit_ctrl() 调用它。(CVE-2021-46906)

    在 Linux 内核中，以下漏洞已修复：

    dm rq：修复表加载失败后 dev 删除中的 blk_mq_tag_set 双重释放问题 (CVE-2021-46938)

    在 Linux 内核中，以下漏洞已修复：

    tracing：重构 trace_clock_global() 以永不阻断 (CVE-2021-46939)

    在 Linux 内核中，以下漏洞已修复：

    md/raid1：结束失败的写入请求时正确指示失败

    此补丁使用位图解决 raid1 阵列中的数据损坏缺陷。如果不进行此修复，失败的 I/O 的位图位最终会被清除。

    由于我们处于 raid1_end_write_request 的失败段中，如果不再次尝试提出请求 (R1BIO_WriteError)，则会发生失败 (R1BIO_Degraded)。(CVE-2021-46950)

    在 Linux 内核中，以下漏洞已修复：

    tpm：efi：使用本地变量计算最终日志大小 (CVE-2021-46951)

    在 Linux 内核中，以下漏洞已修复：

    ACPI：GTDT：监视窗口探测失败时不损坏中断映射 (CVE-2021-46953)

    在 Linux 内核中，以下漏洞已修复：

    openvswitch：修复拆分 IPv4 数据包时的堆栈 OOB 读取问题 (CVE-2021-46955)

    在 Linux 内核中，以下漏洞已修复：

    virtiofs：修复 virtio_fs_probe() 中的内存流失问题 (CVE-2021-46956)

    在 Linux 内核中，以下漏洞已修复：

    spi：使用 devm_spi_alloc_* 修复释放后使用 (CVE-2021-46959)

    在 Linux 内核中，以下漏洞已修复：

    cifs：从 smb2_get_enc_key 返回正确的错误代码 (CVE-2021-46960)

    在 Linux 内核中，以下漏洞已修复：

    irqchip/gic-v3：处理虚假中断时不启用 irqs (CVE-2021-46961)

    在 Linux 内核中，以下漏洞已修复：

    scsi：qla2xxx：修复 qla2xxx_mqueuecommand() 中的崩溃问题 (CVE-2021-46963)

    在 Linux 内核中，以下漏洞已修复：

    nbd：修复了 flush_workqueue 中的空指针问题 (CVE-2021-46981)

    在 Linux 内核中，以下漏洞已修复：

    kyber : 修复抢占时的越界访问 CVE-2021-46984

    在 Linux 内核中，以下漏洞已修复：

    ACPI：scan：修复错误处理路径中的内存流失问题 (CVE-2021-46985)

    在 Linux 内核中，以下漏洞已修复：

    userfaultfd错误路径中的版本页面以避免 BUG_ON (CVE-2021-46988)

    在 Linux 内核中，以下漏洞已修复：

    hfsplus防止缩小截断中的损坏 (CVE-2021-46989)

    在 Linux 内核中，以下漏洞已修复：

    i40e：修复 i40e_client_subtask() 中的释放后使用 (CVE-2021-46991)

    在 Linux 内核中，以下漏洞已修复：

    netfilter: nftables：避免 nft_hash_buckets() 中的溢出 (CVE-2021-46992)

    在 Linux 内核中，以下漏洞已修复：

    sched：修复 uclamp 中的越界访问问题 (CVE-2021-46993)

    在 Linux 内核中，以下漏洞已修复：

    sctp : 在 sctp_sf_do_dupcook_a 中提早执行 asoc 更新 (CVE-2021-46999)

    在 Linux 内核中，以下漏洞已修复：

    ceph：修复了 __fh_to_dentry 中的 getattr 错误的 inode 泄漏 (CVE-2021-47000)

    在 Linux 内核中，以下漏洞已修复：

    ARM：9064/1：hw_breakpoint：不要直接检查事件的 overflow_handler 挂钩 (CVE-2021-47006)

    在 Linux 内核中，以下漏洞已修复：

    net：只允许 init netns 将默认 tcp cong 设置为受限的 algo (CVE-2021-47010)

    在 Linux 内核中，以下漏洞已修复：

    net:emac/emac-mac：修复 emac_mac_tx_buf_send 中的释放后使用问题 (CVE-2021-47013)

    在 Linux 内核中，以下漏洞已修复：

    bnxt_en：修复错误路径中的 RX 使用者索引逻辑。(CVE-2021-47015)

    在 Linux 内核中，以下漏洞已修复：

    bus：qcom：在返回前放置子节点 (CVE-2021-47054)

    在 Linux 内核中，以下漏洞已修复：

    mtd：需要 locking 和 badblock ioctls 的写入权限 (CVE-2021-47055)

    在 Linux 内核中，以下漏洞已修复：

    regmap：在释放 debugfs_name 之后将其设置为空 (CVE-2021-47058)

    在 Linux 内核中，以下漏洞已修复：

    KVM：如果总线遭到破坏，则停止查找合并的 MMIO 区域 (CVE-2021-47060)

    在 Linux 内核中，以下漏洞已修复：

    uio_hv_generic：修复错误处理路径中的内存泄漏 (CVE-2021-47071)

    在 Linux 内核中，以下漏洞已修复：

    RDMA/rxe：如果创建失败，则清除所有 QP 字段 (CVE-2021-47078)

    在 Linux 内核中，以下漏洞已修复：

    neighbor：允许对 NUD_NOARP 条目强制执行 GCed (CVE-2021-47109)

    在 Linux 内核中，以下漏洞已修复：

    x86/kvm：关闭时禁用所有 CPU 上的 kvmclock (CVE-2021-47110)

    在 Linux 内核中，以下漏洞已修复：

    x86/kvm：启动 CPU 上的拆卸 PV 功能 (CVE-2021-47112)

    在 Linux 内核中，以下漏洞已修复：

    ext4：修复了 ext4_es_cache_extent 中由于 ext4_split_extent_at 失败造成的缺陷 (CVE-2021-47117)

    在 Linux 内核中，以下漏洞已修复：

    pid：初始化“cad_pid”时引用 (CVE-2021-47118)

    在 Linux 内核中，以下漏洞已修复：

    HID：magicmouse：修复断开连接时的空取消引用 (CVE-2021-47120)

    在 Linux 内核中，以下漏洞已修复：

    ipv6：修复 KASAN：fib6_nh_flush_exceptions 中的 slab-out-of-bound 读取 (CVE-2021-47126)

    在 Linux 内核中，以下漏洞已修复：

    netfilter: nft_ct：跳过已确认 conntrack 的预期 (CVE-2021-47129)

    在 Linux 内核中，以下漏洞已修复：

    cxgb4：避免在清除过滤器时访问寄存器 (CVE-2021-47138)

    在 Linux 内核中，以下漏洞已修复：

    drm/amdgpu：修复一个释放后使用错误 (CVE-2021-47142)

    在 Linux 内核中，以下漏洞已修复：

    btrfs：不在 link_to_fixup_dir 中执行 BUG_ON (CVE-2021-47145)

    在 Linux 内核中，以下漏洞已修复：

    mld：修复 mld_newpack() 中的错误 (CVE-2021-47146)

    在 Linux 内核中，以下漏洞已修复：

    net: dsa：修复 ->get_get_sset_count() 失败时导致的崩溃 (CVE-2021-47159)

    在 Linux 内核中，以下漏洞已修复：

    tipc：重组 msgs 时，使用 skb_linearize 转换头部 skb (CVE-2021-47162)

    在 Linux 内核中，以下漏洞已修复：

    tipc：等待并退出，直到所有工作队列完成为止 (CVE-2021-47163)

    在 Linux 内核中，以下漏洞已修复：

    NFS：不要损坏 nfs_do_recoalesce() 中的 pg_bytes_written 值 (CVE-2021-47166)

    在 Linux 内核中，以下漏洞已修复：

    NFS：修复 __nfs_pageio_add_request() 中的 Oopsable 情况 (CVE-2021-47167)

    在 Linux 内核中，以下漏洞已修复：

    NFS：修复 filelayout_decode_layout() 中的一个错误限制 (CVE-2021-47168)

    在 Linux 内核中，以下漏洞已修复：

    USB：usbfs：不对过大的内存分配发出警告 (CVE-2021-47170)

    在 Linux 内核中，以下漏洞已修复：

    net: usb：修复 smsc75xx_bind 中的内存泄漏问题 (CVE-2021-47171)

    在 Linux 内核中，以下漏洞已修复：

    iommu/vt-d：修复 alloc_iommu() 中的 sysfs 泄漏 (CVE-2021-47177)

    在 Linux 内核中，以下漏洞已修复：

    netbridge修复 vlan 隧道 dst refcnt 传出时 (CVE-2021-47222)

    在 Linux 内核中，以下漏洞已修复：

    net: bridge修复 vlan 隧道 dst 空指针取消引用 (CVE-2021-47223)

    在 Linux 内核中，以下漏洞已修复：

    KVMx86清除 SMM 标记时立即重置 MMU 上下文 (CVE-2021-47230)

    在 Linux 内核中，以下漏洞已修复：

    netcdc_eem修复 tx 修复 skb 泄漏 (CVE-2021-47236)

    在 Linux 内核中，以下漏洞已修复：

    netipv4修复 ip_mc_add1_src 中的内存泄漏 (CVE-2021-47238)

    在 Linux 内核中，以下漏洞已修复：

    netfilter：synproxy：修复解析 TCP 选项时的越界问题 (CVE-2021-47245)

    在 Linux 内核中，以下漏洞已修复：

    net/mlx5e修复死对等发夹结构的页面回收 (CVE-2021-47246)

    在 Linux 内核中，以下漏洞已修复：

    udp修复 close() 和 udp_abort() 之间的争用 (CVE-2021-47248)

    在 Linux 内核中，以下漏洞已修复：

    netrds修复 rds_recvmsg 中的内存泄漏 (CVE-2021-47249)

    在 Linux 内核中，以下漏洞已修复：

    netipv4修复 netlbl_cipsov4_add_std 中的内存泄漏 (CVE-2021-47250)

    在 Linux 内核中，以下漏洞已修复：

    gfs2：修复 gfs2_glock_shrink_scan 中的释放后使用问题 (CVE-2021-47254)

    在 Linux 内核中，以下漏洞已修复：

    kvmLAPIC恢复保护以防止非法 APIC 寄存器访问 (CVE-2021-47255)

    在 Linux 内核中，以下漏洞已修复：

    mm/memory-failure：确保等待 memory_failure 中的页面回写 (CVE-2021-47256)

    在 Linux 内核中，以下漏洞已修复：

    scsicore修复 scsi_host_alloc() 的错误处理 (CVE-2021-47258)

    在 Linux 内核中，以下漏洞已修复：

    NFS：修复 nfs4_init_client() 中的释放后使用 (CVE-2021-47259)

    在 Linux 内核中，以下漏洞已修复：

    NFS修复 nfs_get_client() 中的潜在空取消引用 (CVE-2021-47260)

    在 Linux 内核中，以下漏洞已修复：

    IB/mlx5：修复初始化 CQ 片段缓冲区 (CVE-2021-47261)

    在 Linux 内核中，以下漏洞已修复：

    KVM：x86：确保嵌套 VM-Enter 失败跟踪点消息的活跃性 (CVE-2021-47262)

    在 Linux 内核中，以下漏洞已修复：

    RDMA/ipoib：修复因破坏非初始 netns 造成的警告 (CVE-2021-47266)

    在 Linux 内核中，以下漏洞已修复：

    tracing：修正造成内存损坏的长度检查 (CVE-2021-47274)

    在 Linux 内核中，以下漏洞已修复：

    ftrace不盲目读取 ftrace_bug() 中的 IP 地址 (CVE-2021-47276)

    在 Linux 内核中，以下漏洞已修复：

    kvm避免来自超出范围的 memslot 访问的基于推测的攻击 (CVE-2021-47277)

    在 Linux 内核中，以下漏洞已修复：

    drm：修复 drm_getunique() 中的释放后使用读取 (CVE-2021-47280)

Tenable 已直接从测试产品的安全公告中提取上述描述块。

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

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

  - 已解決 Linux 核心中的下列弱點：sched: Fix out-of-bound access in uclamp Util-clamp places tasks in different buckets based on their clamp values for performance reasons.
    However, the size of buckets is currently computed using a rounding division, which can lead to an off-by-one error in some configurations. For instance, with 20 buckets, the bucket size will be 1024/20=51. A task with a clamp of 1024 will be mapped to bucket id 1024/51=20. Sadly, correct indexes are in range [0,19], hence leading to an out of bound memory access. Clamp the bucket id to fix the issue.
    (CVE-2021-46993)

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

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

  - 已修复 Linux 内核中的下列漏洞：sched: Fix out-of-bound access in uclamp Util-clamp places tasks in different buckets based on their clamp values for performance reasons.
    However, the size of buckets is currently computed using a rounding division, which can lead to an off-by-one error in some configurations. For instance, with 20 buckets, the bucket size will be 1024/20=51. A task with a clamp of 1024 will be mapped to bucket id 1024/51=20. Sadly, correct indexes are in range [0,19], hence leading to an out of bound memory access. Clamp the bucket id to fix the issue.
    (CVE-2021-46993)

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

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - Linux カーネルでは、以下の脆弱性が解決されています: sched: Fix out-of-bound access in uclamp Util-clamp places tasks in different buckets based on their clamp values for performance reasons.
    However, the size of buckets is currently computed using a rounding division, which can lead to an off-by-one error in some configurations. For instance, with 20 buckets, the bucket size will be 1024/20=51. A task with a clamp of 1024 will be mapped to bucket id 1024/51=20. Sadly, correct indexes are in range [0,19], hence leading to an out of bound memory access. Clamp the bucket id to fix the issue.
    (CVE-2021-46993)

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

The version of Tencent Linux installed on the remote TencentOS Server 2 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0436 advisory.

    Package updates are available for TencentOS Server 2 that fix the following vulnerabilities:

    CVE-2024-42104:
    In the Linux kernel, the following vulnerability has been resolved:

    nilfs2: add missing check for inode numbers on directory entries

    Syzbot reported that mounting and unmounting a specific pattern of     corrupted nilfs2 filesystem images causes a use-after-free of metadata     file inodes, which triggers a kernel bug in lru_add_fn().

    As Jan Kara pointed out, this is because the link count of a metadata file     gets corrupted to 0, and nilfs_evict_inode(), which is called from iput(),     tries to delete that inode (ifile inode in this case).

    The inconsistency occurs because directories containing the inode numbers     of these metadata files that should not be visible in the namespace are     read without checking.

    Fix this issue by treating the inode numbers of these internal files as     errors in the sanity check helper when reading directory folios/pages.

    Also thanks to Hillf Danton and Matthew Wilcox for their initial mm-layer     analysis.

    CVE-2024-38599:
    In the Linux kernel, the following vulnerability has been resolved:

    jffs2: prevent xattr node from overflowing the eraseblock

    Add a check to make sure that the requested xattr node size is no larger     than the eraseblock minus the cleanmarker.

    Unlike the usual inode nodes, the xattr nodes aren't split into parts     and spread across multiple eraseblocks, which means that a xattr node     must not occupy more than one eraseblock. If the requested xattr value is     too large, the xattr node can spill onto the next eraseblock, overwriting     the nodes and causing errors such as:

    jffs2: argh. node added in wrong place at 0x0000b050(2)     jffs2: nextblock 0x0000a000, expected at 0000b00c     jffs2: error: (823) do_verify_xattr_datum: node CRC failed at 0x01e050,     read=0xfc892c93, calc=0x000000     jffs2: notice: (823) jffs2_get_inode_nodes: Node header CRC failed     at 0x01e00c. {848f,2fc4,0fef511f,59a3d171}     jffs2: Node at 0x0000000c with length 0x00001044 would run over the     end of the erase block     jffs2: Perhaps the file system was created with the wrong erase size?     jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found     at 0x00000010: 0x1044 instead

    This breaks the filesystem and can lead to KASAN crashes such as:

    BUG: KASAN: slab-out-of-bounds in jffs2_sum_add_kvec+0x125e/0x15d0     Read of size 4 at addr ffff88802c31e914 by task repro/830     CPU: 0 PID: 830 Comm: repro Not tainted 6.9.0-rc3+ #1     Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),     BIOS Arch Linux 1.16.3-1-1 04/01/2014     Call Trace:
     <TASK>      dump_stack_lvl+0xc6/0x120      print_report+0xc4/0x620      ? __virt_addr_valid+0x308/0x5b0      kasan_report+0xc1/0xf0      ? jffs2_sum_add_kvec+0x125e/0x15d0      ? jffs2_sum_add_kvec+0x125e/0x15d0      jffs2_sum_add_kvec+0x125e/0x15d0      jffs2_flash_direct_writev+0xa8/0xd0      jffs2_flash_writev+0x9c9/0xef0      ? __x64_sys_setxattr+0xc4/0x160      ? do_syscall_64+0x69/0x140      ? entry_SYSCALL_64_after_hwframe+0x76/0x7e      [...]

    Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

    CVE-2024-38583:
    In the Linux kernel, the following vulnerability has been resolved:

    nilfs2: fix use-after-free of timer for log writer thread

    Patch series nilfs2: fix log writer related issues.

    This bug fix series covers three nilfs2 log writer-related issues,     including a timer use-after-free issue and potential deadlock issue on     unmount, and a potential freeze issue in event synchronization found     during their analysis.  Details are described in each commit log.


    This patch (of 3):

    A use-after-free issue has been reported regarding the timer sc_timer on     the nilfs_sc_info structure.

    The problem is that even though it is used to wake up a sleeping log     writer thread, sc_timer is not shut down until the nilfs_sc_info structure     is about to be freed, and is used regardless of the thread's lifetime.

    Fix this issue by limiting the use of sc_timer only while the log writer     thread is alive.

    CVE-2024-36964:
    In the Linux kernel, the following vulnerability has been resolved:

    fs/9p: only translate RWX permissions for plain 9P2000

    Garbage in plain 9P2000's perm bits is allowed through, which causes it     to be able to set (among others) the suid bit. This was presumably not     the intent since the unix extended bits are handled explicitly and     conditionally on .u.

    CVE-2021-47505:
    In the Linux kernel, the following vulnerability has been resolved:

    aio: fix use-after-free due to missing POLLFREE handling

    signalfd_poll() and binder_poll() are special in that they use a     waitqueue whose lifetime is the current task, rather than the struct     file as is normally the case.  This is okay for blocking polls, since a     blocking poll occurs within one task; however, non-blocking polls     require another solution.  This solution is for the queue to be cleared     before it is freed, by sending a POLLFREE notification to all waiters.

    Unfortunately, only eventpoll handles POLLFREE.  A second type of     non-blocking poll, aio poll, was added in kernel v4.18, and it doesn't     handle POLLFREE.  This allows a use-after-free to occur if a signalfd or     binder fd is polled with aio poll, and the waitqueue gets freed.

    Fix this by making aio poll handle POLLFREE.

    A patch by Ramji Jiyani <ramjiyani@google.com>     (https://lore.kernel.org/r/20211027011834.2497484-1-ramjiyani@google.com)     tried to do this by making aio_poll_wake() always complete the request     inline if POLLFREE is seen.  However, that solution had two bugs.
    First, it introduced a deadlock, as it unconditionally locked the aio     context while holding the waitqueue lock, which inverts the normal     locking order.  Second, it didn't consider that POLLFREE notifications     are missed while the request has been temporarily de-queued.

    The second problem was solved by my previous patch.  This patch then     properly fixes the use-after-free by handling POLLFREE in a     deadlock-free way.  It does this by taking advantage of the fact that     freeing of the waitqueue is RCU-delayed, similar to what eventpoll does.

    CVE-2021-46993:
    In the Linux kernel, the following vulnerability has been resolved:

    sched: Fix out-of-bound access in uclamp

    Util-clamp places tasks in different buckets based on their clamp values     for performance reasons. However, the size of buckets is currently     computed using a rounding division, which can lead to an off-by-one     error in some configurations.

    For instance, with 20 buckets, the bucket size will be 1024/20=51. A     task with a clamp of 1024 will be mapped to bucket id 1024/51=20. Sadly,     correct indexes are in range [0,19], hence leading to an out of bound     memory access.

    Clamp the bucket id to fix the issue.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of kernel installed on the remote host is prior to 5.4.129-62.227. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2022-004 advisory.

    A flaw was found in the Linux kernels implementation of wifi fragmentation handling. An attacker with the     ability to transmit within the wireless transmission range of an access point can abuse a flaw where     previous contents of wifi fragments can be unintentionally transmitted to another device. (CVE-2020-24586)

    A flaw was found in the Linux kernel's WiFi implementation. An attacker within the wireless range can     abuse a logic flaw in the WiFi implementation by reassembling packets from multiple fragments under     different keys, treating them as valid. This flaw allows an attacker to send a fragment under an incorrect     key, treating them as a valid fragment under the new key. The highest threat from this vulnerability is to     confidentiality. (CVE-2020-24587)

    A flaw was found in the Linux kernels wifi implementation. An attacker within wireless broadcast range can     inject custom data into the wireless communication circumventing checks on the data.  This can cause the     frame to pass checks and be considered a valid frame of a different type. (CVE-2020-24588)

    Frames used for authentication and key management between the AP and connected clients.  Some clients may     take these redirected frames masquerading as control mechanisms from the AP. (CVE-2020-26139)

    A vulnerability was found in Linux kernel's WiFi implementation.  An attacker within wireless range can     inject a control packet fragment where the kernel does not verify the Message Integrity Check     (authenticity) of fragmented TKIP frames. (CVE-2020-26141)

    A flaw was found in ath10k_htt_rx_proc_rx_frag_ind_hl in drivers/net/wireless/ath/ath10k/htt_rx.c in the     Linux kernel WiFi implementations, where it accepts a second (or subsequent) broadcast fragments even when     sent in plaintext and then process them as full unfragmented frames. The highest threat from this     vulnerability is to integrity. (CVE-2020-26145)

    A flaw was found in ieee80211_rx_h_defragment in net/mac80211/rx.c in the Linux Kernel's WiFi     implementation. This vulnerability can be abused to inject packets or exfiltrate selected fragments when     another device sends fragmented frames, and the WEP, CCMP, or GCMP data-confidentiality protocol is used.
    The highest threat from this vulnerability is to integrity. (CVE-2020-26147)

    A flaw was found in the Linux kernel in certs/blacklist.c, When signature entries for EFI_CERT_X509_GUID     are contained in the Secure Boot Forbidden Signature Database, the entries are skipped. This can cause a     security threat and breach system integrity, confidentiality and even lead to a denial of service problem.
    (CVE-2020-26541)

    A vulnerability was found in the bluez, where Passkey Entry protocol used in Secure Simple Pairing (SSP),     Secure Connections (SC) and LE Secure Connections (LESC) of the Bluetooth Core Specification is vulnerable     to an impersonation attack where an active attacker can impersonate the initiating device without any     previous knowledge. (CVE-2020-26558)

    A flaw was found in the Linux kernel. Improper access control in BlueZ may allow an authenticated user to     potentially enable information disclosure via adjacent access. The highest threat from this vulnerability     is to data confidentiality and integrity. (CVE-2021-0129)

    A flaw was found in the Linux kernel's KVM implementation, where improper handing of the VM_IO|VM_PFNMAP     VMAs in KVM bypasses RO checks and leads to pages being freed while still accessible by the VMM and guest.
    This flaw allows users who can start and control a VM to read/write random pages of memory, resulting in     local privilege escalation. The highest threat from this vulnerability is to confidentiality, integrity,     and system availability. (CVE-2021-22543)

    A flaw was found in the Linux kernel's handling of the removal of Bluetooth HCI controllers. This flaw     allows an attacker with a local account to exploit a race condition, leading to corrupted memory and     possible privilege escalation. The highest threat from this vulnerability is to confidentiality,     integrity, as well as system availability. (CVE-2021-32399)

    A use-after-free flaw was found in hci_send_acl in the bluetooth host controller interface (HCI) in Linux     kernel, where a local attacker with an access rights could cause a denial of service problem on the system     The issue results from the object hchan, freed in hci_disconn_loglink_complete_evt, yet still used in     other places. The highest threat from this vulnerability is to data integrity, confidentiality and system     availability. (CVE-2021-33034)

    The canbus filesystem in the Linux kernel contains an information leak of kernel memory to devices on the     CAN bus network link layer.  An attacker with the ability to dump messages on the CAN bus is able to learn     of uninitialized stack values by dumbing messages on the can bus. (CVE-2021-34693)

    An out-of-bounds (OOB) memory access flaw was found in fs/f2fs/node.c in the f2fs module in the Linux     kernel. A bounds check failure allows a local attacker to gain access to out-of-bounds memory leading to a     system crash or a leak of internal kernel information. The highest threat from this vulnerability is to     system availability. (CVE-2021-3506)

    A flaw double-free memory corruption in the Linux kernel HCI device initialization subsystem was found in     the way user attach malicious HCI TTY Bluetooth device. A local user could use this flaw to crash the     system. (CVE-2021-3564)

    A flaw use-after-free in function hci_sock_bound_ioctl() of the Linux kernel HCI subsystem was found in     the way user calls ioct HCIUNBLOCKADDR or other way triggers race condition of the call     hci_unregister_dev() together with one of the calls hci_sock_blacklist_add(), hci_sock_blacklist_del(),     hci_get_conn_info(), hci_get_auth_info(). A privileged local user could use this flaw to crash the system     or escalate their privileges on the system. (CVE-2021-3573)

    A flaw was found in the Linux kernels NFC implementation, A NULL pointer dereference and BUG leading to a     denial of service can be triggered by a local unprivileged user causing a kernel panic. (CVE-2021-38208)

    In the Linux kernel, the following vulnerability has been resolved:

    HID: usbhid: fix info leak in hid_submit_ctrl

    In hid_submit_ctrl(), the way of calculating the report length doesn'ttake into account that report->size     can be zero. When running thesyzkaller reproducer, a report of size 0 causes hid_submit_ctrl) tocalculate     transfer_buffer_length as 16384. When this urb is passed tothe usb core layer, KMSAN reports an info leak     of 16384 bytes.

    To fix this, first modify hid_report_len() to account for the zeroreport size case by using DIV_ROUND_UP     for the division. Then, call itfrom hid_submit_ctrl(). (CVE-2021-46906)

    In the Linux kernel, the following vulnerability has been resolved:

    dm rq: fix double free of blk_mq_tag_set in dev remove after table load fails (CVE-2021-46938)

    In the Linux kernel, the following vulnerability has been resolved:

    tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)

    In the Linux kernel, the following vulnerability has been resolved:

    md/raid1: properly indicate failure when ending a failed write request

    This patch addresses a data corruption bug in raid1 arrays using bitmaps.Without this fix, the bitmap bits     for the failed I/O end up being cleared.

    Since we are in the failure leg of raid1_end_write_request, the requesteither needs to be retried     (R1BIO_WriteError) or failed (R1BIO_Degraded). (CVE-2021-46950)

    In the Linux kernel, the following vulnerability has been resolved:

    tpm: efi: Use local variable for calculating final log size (CVE-2021-46951)

    In the Linux kernel, the following vulnerability has been resolved:

    ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure (CVE-2021-46953)

    In the Linux kernel, the following vulnerability has been resolved:

    openvswitch: fix stack OOB read while fragmenting IPv4 packets (CVE-2021-46955)

    In the Linux kernel, the following vulnerability has been resolved:

    virtiofs: fix memory leak in virtio_fs_probe() (CVE-2021-46956)

    In the Linux kernel, the following vulnerability has been resolved:

    spi: Fix use-after-free with devm_spi_alloc_* (CVE-2021-46959)

    In the Linux kernel, the following vulnerability has been resolved:

    cifs: Return correct error code from smb2_get_enc_key (CVE-2021-46960)

    In the Linux kernel, the following vulnerability has been resolved:

    irqchip/gic-v3: Do not enable irqs when handling spurious interrups (CVE-2021-46961)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: qla2xxx: Fix crash in qla2xxx_mqueuecommand() (CVE-2021-46963)

    In the Linux kernel, the following vulnerability has been resolved:

    nbd: Fix NULL pointer in flush_workqueue (CVE-2021-46981)

    In the Linux kernel, the following vulnerability has been resolved:

    kyber: fix out of bounds access when preempted (CVE-2021-46984)

    In the Linux kernel, the following vulnerability has been resolved:

    ACPI: scan: Fix a memory leak in an error handling path (CVE-2021-46985)

    In the Linux kernel, the following vulnerability has been resolved:

    userfaultfd: release page in error path to avoid BUG_ON (CVE-2021-46988)

    In the Linux kernel, the following vulnerability has been resolved:

    hfsplus: prevent corruption in shrinking truncate (CVE-2021-46989)

    In the Linux kernel, the following vulnerability has been resolved:

    i40e: Fix use-after-free in i40e_client_subtask() (CVE-2021-46991)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nftables: avoid overflows in nft_hash_buckets() (CVE-2021-46992)

    In the Linux kernel, the following vulnerability has been resolved:

    sched: Fix out-of-bound access in uclamp (CVE-2021-46993)

    In the Linux kernel, the following vulnerability has been resolved:

    sctp: do asoc update earlier in sctp_sf_do_dupcook_a (CVE-2021-46999)

    In the Linux kernel, the following vulnerability has been resolved:

    ceph: fix inode leak on getattr error in __fh_to_dentry (CVE-2021-47000)

    In the Linux kernel, the following vulnerability has been resolved:

    ARM: 9064/1: hw_breakpoint: Do not directly check the event's overflow_handler hook (CVE-2021-47006)

    In the Linux kernel, the following vulnerability has been resolved:

    net: Only allow init netns to set default tcp cong to a restricted algo (CVE-2021-47010)

    In the Linux kernel, the following vulnerability has been resolved:

    net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send (CVE-2021-47013)

    In the Linux kernel, the following vulnerability has been resolved:

    bnxt_en: Fix RX consumer index logic in the error path. (CVE-2021-47015)

    In the Linux kernel, the following vulnerability has been resolved:

    bus: qcom: Put child node before return (CVE-2021-47054)

    In the Linux kernel, the following vulnerability has been resolved:

    mtd: require write permissions for locking and badblock ioctls (CVE-2021-47055)

    In the Linux kernel, the following vulnerability has been resolved:

    regmap: set debugfs_name to NULL after it is freed (CVE-2021-47058)

    In the Linux kernel, the following vulnerability has been resolved:

    KVM: Stop looking for coalesced MMIO zones if the bus is destroyed (CVE-2021-47060)

    In the Linux kernel, the following vulnerability has been resolved:

    uio_hv_generic: Fix a memory leak in error handling paths (CVE-2021-47071)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/rxe: Clear all QP fields if creation failed (CVE-2021-47078)

    In the Linux kernel, the following vulnerability has been resolved:

    neighbour: allow NUD_NOARP entries to be forced GCed (CVE-2021-47109)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/kvm: Disable kvmclock on all CPUs on shutdown (CVE-2021-47110)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/kvm: Teardown PV features on boot CPU as well (CVE-2021-47112)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: fix bug on in ext4_es_cache_extent as ext4_split_extent_at failed (CVE-2021-47117)

    In the Linux kernel, the following vulnerability has been resolved:

    pid: take a reference when initializing `cad_pid` (CVE-2021-47118)

    In the Linux kernel, the following vulnerability has been resolved:

    HID: magicmouse: fix NULL-deref on disconnect (CVE-2021-47120)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv6: Fix KASAN: slab-out-of-bounds Read in fib6_nh_flush_exceptions (CVE-2021-47126)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nft_ct: skip expectations for confirmed conntrack (CVE-2021-47129)

    In the Linux kernel, the following vulnerability has been resolved:

    cxgb4: avoid accessing registers when clearing filters (CVE-2021-47138)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/amdgpu: Fix a use-after-free (CVE-2021-47142)

    In the Linux kernel, the following vulnerability has been resolved:

    btrfs: do not BUG_ON in link_to_fixup_dir (CVE-2021-47145)

    In the Linux kernel, the following vulnerability has been resolved:

    mld: fix panic in mld_newpack() (CVE-2021-47146)

    In the Linux kernel, the following vulnerability has been resolved:

    net: dsa: fix a crash if ->get_sset_count() fails (CVE-2021-47159)

    In the Linux kernel, the following vulnerability has been resolved:

    tipc: skb_linearize the head skb when reassembling msgs (CVE-2021-47162)

    In the Linux kernel, the following vulnerability has been resolved:

    tipc: wait and exit until all work queues are done (CVE-2021-47163)

    In the Linux kernel, the following vulnerability has been resolved:

    NFS: Don't corrupt the value of pg_bytes_written in nfs_do_recoalesce() (CVE-2021-47166)

    In the Linux kernel, the following vulnerability has been resolved:

    NFS: Fix an Oopsable condition in __nfs_pageio_add_request() (CVE-2021-47167)

    In the Linux kernel, the following vulnerability has been resolved:

    NFS: fix an incorrect limit in filelayout_decode_layout() (CVE-2021-47168)

    In the Linux kernel, the following vulnerability has been resolved:

    USB: usbfs: Don't WARN about excessively large memory allocations (CVE-2021-47170)

    In the Linux kernel, the following vulnerability has been resolved:

    net: usb: fix memory leak in smsc75xx_bind (CVE-2021-47171)

    In the Linux kernel, the following vulnerability has been resolved:

    iommu/vt-d: Fix sysfs leak in alloc_iommu() (CVE-2021-47177)

    In the Linux kernel, the following vulnerability has been resolved:

    net: bridge: fix vlan tunnel dst refcnt when egressing (CVE-2021-47222)

    In the Linux kernel, the following vulnerability has been resolved:

    net: bridge: fix vlan tunnel dst null pointer dereference (CVE-2021-47223)

    In the Linux kernel, the following vulnerability has been resolved:

    KVM: x86: Immediately reset the MMU context when the SMM flag is cleared (CVE-2021-47230)

    In the Linux kernel, the following vulnerability has been resolved:

    net: cdc_eem: fix tx fixup skb leak (CVE-2021-47236)

    In the Linux kernel, the following vulnerability has been resolved:

    net: ipv4: fix memory leak in ip_mc_add1_src (CVE-2021-47238)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: synproxy: Fix out of bounds when parsing TCP options (CVE-2021-47245)

    In the Linux kernel, the following vulnerability has been resolved:

    net/mlx5e: Fix page reclaim for dead peer hairpin (CVE-2021-47246)

    In the Linux kernel, the following vulnerability has been resolved:

    udp: fix race between close() and udp_abort() (CVE-2021-47248)

    In the Linux kernel, the following vulnerability has been resolved:

    net: rds: fix memory leak in rds_recvmsg (CVE-2021-47249)

    In the Linux kernel, the following vulnerability has been resolved:

    net: ipv4: fix memory leak in netlbl_cipsov4_add_std (CVE-2021-47250)

    In the Linux kernel, the following vulnerability has been resolved:

    gfs2: Fix use-after-free in gfs2_glock_shrink_scan (CVE-2021-47254)

    In the Linux kernel, the following vulnerability has been resolved:

    kvm: LAPIC: Restore guard to prevent illegal APIC register access (CVE-2021-47255)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/memory-failure: make sure wait for page writeback in memory_failure (CVE-2021-47256)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: core: Fix error handling of scsi_host_alloc() (CVE-2021-47258)

    In the Linux kernel, the following vulnerability has been resolved:

    NFS: Fix use-after-free in nfs4_init_client() (CVE-2021-47259)

    In the Linux kernel, the following vulnerability has been resolved:

    NFS: Fix a potential NULL dereference in nfs_get_client() (CVE-2021-47260)

    In the Linux kernel, the following vulnerability has been resolved:

    IB/mlx5: Fix initializing CQ fragments buffer (CVE-2021-47261)

    In the Linux kernel, the following vulnerability has been resolved:

    KVM: x86: Ensure liveliness of nested VM-Enter fail tracepoint message (CVE-2021-47262)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/ipoib: Fix warning caused by destroying non-initial netns (CVE-2021-47266)

    In the Linux kernel, the following vulnerability has been resolved:

    tracing: Correct the length check which causes memory corruption (CVE-2021-47274)

    In the Linux kernel, the following vulnerability has been resolved:

    ftrace: Do not blindly read the ip address in ftrace_bug() (CVE-2021-47276)

    In the Linux kernel, the following vulnerability has been resolved:

    kvm: avoid speculation-based attacks from out-of-range memslot accesses (CVE-2021-47277)

    In the Linux kernel, the following vulnerability has been resolved:

    drm: Fix use-after-free read in drm_getunique() (CVE-2021-47280)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0434 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

    CVE-2024-42104:
    In the Linux kernel, the following vulnerability has been resolved:

    nilfs2: add missing check for inode numbers on directory entries

    Syzbot reported that mounting and unmounting a specific pattern of     corrupted nilfs2 filesystem images causes a use-after-free of metadata     file inodes, which triggers a kernel bug in lru_add_fn().

    As Jan Kara pointed out, this is because the link count of a metadata file     gets corrupted to 0, and nilfs_evict_inode(), which is called from iput(),     tries to delete that inode (ifile inode in this case).

    The inconsistency occurs because directories containing the inode numbers     of these metadata files that should not be visible in the namespace are     read without checking.

    Fix this issue by treating the inode numbers of these internal files as     errors in the sanity check helper when reading directory folios/pages.

    Also thanks to Hillf Danton and Matthew Wilcox for their initial mm-layer     analysis.

    CVE-2024-38599:
    In the Linux kernel, the following vulnerability has been resolved:

    jffs2: prevent xattr node from overflowing the eraseblock

    Add a check to make sure that the requested xattr node size is no larger     than the eraseblock minus the cleanmarker.

    Unlike the usual inode nodes, the xattr nodes aren't split into parts     and spread across multiple eraseblocks, which means that a xattr node     must not occupy more than one eraseblock. If the requested xattr value is     too large, the xattr node can spill onto the next eraseblock, overwriting     the nodes and causing errors such as:

    jffs2: argh. node added in wrong place at 0x0000b050(2)     jffs2: nextblock 0x0000a000, expected at 0000b00c     jffs2: error: (823) do_verify_xattr_datum: node CRC failed at 0x01e050,     read=0xfc892c93, calc=0x000000     jffs2: notice: (823) jffs2_get_inode_nodes: Node header CRC failed     at 0x01e00c. {848f,2fc4,0fef511f,59a3d171}     jffs2: Node at 0x0000000c with length 0x00001044 would run over the     end of the erase block     jffs2: Perhaps the file system was created with the wrong erase size?     jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found     at 0x00000010: 0x1044 instead

    This breaks the filesystem and can lead to KASAN crashes such as:

    BUG: KASAN: slab-out-of-bounds in jffs2_sum_add_kvec+0x125e/0x15d0     Read of size 4 at addr ffff88802c31e914 by task repro/830     CPU: 0 PID: 830 Comm: repro Not tainted 6.9.0-rc3+ #1     Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),     BIOS Arch Linux 1.16.3-1-1 04/01/2014     Call Trace:
     <TASK>      dump_stack_lvl+0xc6/0x120      print_report+0xc4/0x620      ? __virt_addr_valid+0x308/0x5b0      kasan_report+0xc1/0xf0      ? jffs2_sum_add_kvec+0x125e/0x15d0      ? jffs2_sum_add_kvec+0x125e/0x15d0      jffs2_sum_add_kvec+0x125e/0x15d0      jffs2_flash_direct_writev+0xa8/0xd0      jffs2_flash_writev+0x9c9/0xef0      ? __x64_sys_setxattr+0xc4/0x160      ? do_syscall_64+0x69/0x140      ? entry_SYSCALL_64_after_hwframe+0x76/0x7e      [...]

    Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

    CVE-2024-38583:
    In the Linux kernel, the following vulnerability has been resolved:

    nilfs2: fix use-after-free of timer for log writer thread

    Patch series nilfs2: fix log writer related issues.

    This bug fix series covers three nilfs2 log writer-related issues,     including a timer use-after-free issue and potential deadlock issue on     unmount, and a potential freeze issue in event synchronization found     during their analysis.  Details are described in each commit log.


    This patch (of 3):

    A use-after-free issue has been reported regarding the timer sc_timer on     the nilfs_sc_info structure.

    The problem is that even though it is used to wake up a sleeping log     writer thread, sc_timer is not shut down until the nilfs_sc_info structure     is about to be freed, and is used regardless of the thread's lifetime.

    Fix this issue by limiting the use of sc_timer only while the log writer     thread is alive.

    CVE-2024-36964:
    In the Linux kernel, the following vulnerability has been resolved:

    fs/9p: only translate RWX permissions for plain 9P2000

    Garbage in plain 9P2000's perm bits is allowed through, which causes it     to be able to set (among others) the suid bit. This was presumably not     the intent since the unix extended bits are handled explicitly and     conditionally on .u.

    CVE-2021-47505:
    In the Linux kernel, the following vulnerability has been resolved:

    aio: fix use-after-free due to missing POLLFREE handling

    signalfd_poll() and binder_poll() are special in that they use a     waitqueue whose lifetime is the current task, rather than the struct     file as is normally the case.  This is okay for blocking polls, since a     blocking poll occurs within one task; however, non-blocking polls     require another solution.  This solution is for the queue to be cleared     before it is freed, by sending a POLLFREE notification to all waiters.

    Unfortunately, only eventpoll handles POLLFREE.  A second type of     non-blocking poll, aio poll, was added in kernel v4.18, and it doesn't     handle POLLFREE.  This allows a use-after-free to occur if a signalfd or     binder fd is polled with aio poll, and the waitqueue gets freed.

    Fix this by making aio poll handle POLLFREE.

    A patch by Ramji Jiyani <ramjiyani@google.com>     (https://lore.kernel.org/r/20211027011834.2497484-1-ramjiyani@google.com)     tried to do this by making aio_poll_wake() always complete the request     inline if POLLFREE is seen.  However, that solution had two bugs.
    First, it introduced a deadlock, as it unconditionally locked the aio     context while holding the waitqueue lock, which inverts the normal     locking order.  Second, it didn't consider that POLLFREE notifications     are missed while the request has been temporarily de-queued.

    The second problem was solved by my previous patch.  This patch then     properly fixes the use-after-free by handling POLLFREE in a     deadlock-free way.  It does this by taking advantage of the fact that     freeing of the waitqueue is RCU-delayed, similar to what eventpoll does.

    CVE-2021-46993:
    In the Linux kernel, the following vulnerability has been resolved:

    sched: Fix out-of-bound access in uclamp

    Util-clamp places tasks in different buckets based on their clamp values     for performance reasons. However, the size of buckets is currently     computed using a rounding division, which can lead to an off-by-one     error in some configurations.

    For instance, with 20 buckets, the bucket size will be 1024/20=51. A     task with a clamp of 1024 will be mapped to bucket id 1024/51=20. Sadly,     correct indexes are in range [0,19], hence leading to an out of bound     memory access.

    Clamp the bucket id to fix the issue.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In the Linux kernel, the following vulnerability has been resolved: sched: Fix out-of-bound access in     uclamp Util-clamp places tasks in different buckets based on their clamp values for performance reasons.
    However, the size of buckets is currently computed using a rounding division, which can lead to an off-by-     one error in some configurations. For instance, with 20 buckets, the bucket size will be 1024/20=51. A     task with a clamp of 1024 will be mapped to bucket id 1024/51=20. Sadly, correct indexes are in range     [0,19], hence leading to an out of bound memory access. Clamp the bucket id to fix the issue.
    (CVE-2021-46993)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
160440	Amazon Linux 2核心 --advisory ALAS2KERNEL-5。4-2022-004 (ALASKERNEL-5.4-2022-004)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
160459	Amazon Linux 2核心 --advisory ALAS2KERNEL-5。10-2022-002 (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
160440	Amazon Linux 2 内核 --advisory ALAS2KERNEL-5。4-2022-004 (ALASKERNEL-5.4-2022-004)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
160459	Amazon Linux 2 内核 --advisory ALAS2KERNEL-5。10-2022-002 (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
246304	Linux Distros 未修補的弱點：CVE-2021-46993	Nessus	Misc.	2025/8/8	2025/11/25	high
246304	Linux Distros 未修补的漏洞：CVE-2021-46993	Nessus	Misc.	2025/8/8	2025/11/25	high
160440	Amazon Linux 2kernel、 --advisory ALAS2KERNEL-5。4-2022-004 ALASKERNEL-5.4-2022-004	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
160459	Amazon Linux 2kernel、 --advisory ALAS2KERNEL-5。10-2022-002 ALASKERNEL-5.10-2022-002	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
246304	Linux Distros のパッチ未適用の脆弱性: CVE-2021-46993	Nessus	Misc.	2025/8/8	2025/11/25	high
275982	TencentOS Server 2: kernel (TSSA-2025:0436)	Nessus	Tencent Local Security Checks	2025/11/20	2025/11/20	high
160440	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2022-004 (ALASKERNEL-5.4-2022-004)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
160459	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2022-002 (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	2022/5/2	2026/2/9	high
276021	TencentOS Server 3: kernel (TSSA-2025:0434)	Nessus	Tencent Local Security Checks	2025/11/20	2025/11/20	high
246304	Linux Distros Unpatched Vulnerability : CVE-2021-46993	Nessus	Misc.	2025/8/8	2025/11/25	high

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high

high

high

high