CentOS Linux 7 [TuxCare] 安全性更新：bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc 多個弱點 （CENTOS7：CLSA-2026：1792234299）
high Nessus Plugin ID 369489
語言:
概要
CentOS Linux 主機缺少一個或多個安全性更新。說明
CentOS Linux 7 主機已安裝的套件會受到 TuxCare CENTOS7：CLSA-2026：1792234299 公告中提及的多個弱點影響。- 在 Linux 核心 5.18.14 以及之前版本中，net/netfilter/nfnetlink_queue.c 中的 nfqnl_mangle 允許遠端攻擊者造成拒絕服務 (錯誤)，這是因爲當 nf_queue 判定包含一個位元組的 nfta_payload 屬性時，skb_pull 可能遇到負數 skb->len。(CVE-2022-36946)
- 已解決 Linux 核心中的下列弱點：wifi: iwlwifi: mvm: Fix a memory corruption issue A few lines above, space is kzalloc()'ed for: sizeof(struct iwl_nvm_data) + sizeof(struct ieee80211_channel) + sizeof(struct ieee80211_rate) 'mvm->nvm_data' is a 'struct iwl_nvm_data', so it is fine. At the end of this structure, there is the 'channels' flex array. Each element is of type 'struct ieee80211_channel'. So only 1 element is allocated in this array. When doing:
mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels; We point at the first element of the 'channels' flex array. So this is fine. However, when doing: mvm->nvm_data->bands[0].bitrates = (void
*)((u8 *)mvm->nvm_data->channels + 1); because of the (u8 *) cast, we add only 1 to the address of the beginning of the flex array. It is likely that we want point at the 'struct ieee80211_rate' allocated just after. Remove the spurious casting so that the pointer arithmetic works as expected. (CVE-2023-52531)
- 已解決 Linux 核心中的下列弱點：KVM: x86: Don't (re)check L1 intercepts when completing userspace I/O When completing emulation of instruction that generated a userspace exit for I/O, don't recheck L1 intercepts as KVM has already finished that phase of instruction execution, i.e. has already committed to allowing L2 to perform I/O. If L1 (or host userspace) modifies the I/O permission bitmaps during the exit to userspace, KVM will treat the access as being intercepted despite already having emulated the I/O access. Pivot on EMULTYPE_NO_DECODE to detect that KVM is completing emulation. Of the three users of EMULTYPE_NO_DECODE, only complete_emulated_io() (the intended recipient) can reach the code in question. gp_interception()'s use is mutually exclusive with is_guest_mode(), and complete_emulated_insn_gp() unconditionally pairs EMULTYPE_NO_DECODE with EMULTYPE_SKIP. The bad behavior was detected by a syzkaller program that toggles port I/O interception during the userspace I/O exit, ultimately resulting in a WARN on vcpu->arch.pio.count being non-zero due to KVM no completing emulation of the I/O instruction. WARNING: CPU: 23 PID: 1083 at arch/x86/kvm/x86.c:8039 emulator_pio_in_out+0x154/0x170 [kvm] Modules linked in: kvm_intel kvm irqbypass CPU: 23 UID: 1000 PID: 1083 Comm: repro Not tainted 6.16.0-rc5-c1610d2d66b1-next-vm #74 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:emulator_pio_in_out+0x154/0x170 [kvm] PKRU: 55555554 Call Trace: <TASK> kvm_fast_pio+0xd6/0x1d0 [kvm] vmx_handle_exit+0x149/0x610 [kvm_intel] kvm_arch_vcpu_ioctl_run+0xda8/0x1ac0 [kvm] kvm_vcpu_ioctl+0x244/0x8c0 [kvm]
__x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0x5d/0xc60 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> (CVE-2025-40026)
- 已解決 Linux 核心中的下列弱點：Bluetooth: btusb: fix use-after-free on registration failure Make sure to release the sibling interfaces in case controller registration fails to avoid use-after-free and double-free when they are eventually disconnected. This issue was reported by Sashiko while reviewing a fix for a wakeup source leak in the btusb probe errors paths. (CVE-2026-64471)
- 已解決 Linux 核心中的下列弱點：ALSA: firewire: isight: bound the sample count to the packet payload isight_packet() takes the frame count from the device iso packet and checks it only against the device claimed iso length. count = be32_to_cpu(payload->sample_count); if (likely(count <= (length - 16) / 4)) isight_samples(isight, payload->samples, count); length is the iso header data_length. It can be up to 0xffff. So the gate allows a count up to about 16379. isight_samples() then copies count frames out of payload->samples into the PCM DMA buffer. payload->samples holds only 2 * MAX_FRAMES_PER_PACKET values. The device multiplexes two samples per frame. A count past MAX_FRAMES_PER_PACKET reads past the payload. A count past the buffer size writes past runtime->dma_area.
The smallest PCM buffer is larger than MAX_FRAMES_PER_PACKET. Bounding the count to MAX_FRAMES_PER_PACKET keeps both the read and the write in range. A malicious or faulty Apple iSight on the FireWire bus reaches this during a normal capture. Add the MAX_FRAMES_PER_PACKET bound to the gate. (CVE-2026-64483)
請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。
解決方案
根據 TuxCare 公告 CENTOS7：CLSA-2026：1792234299 中的指引更新受影響的套件。另請參閱
Plugin 詳細資訊
嚴重性: High
ID: 369489
檔案名稱: tuxcare_centos_7_CLSA-2026-1792234299.nasl
版本: 1.1
類型: Local
代理程式: unix
已發布: 2026/10/21
已更新: 2026/10/21
支援的感應器: Nessus Agent, Continuous Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus
風險資訊
VPR
風險因素: High
分數: 8
百分位數: 99.69
Vendor
Vendor Severity: Critical
CVSS v2
風險因素: Medium
基本分數: 6.8
時間性分數: 5.3
媒介: CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C
CVSS 評分資料來源: CVE-2023-52531
CVSS v3
風險因素: High
基本分數: 7.8
時間性分數: 7
媒介: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
時間媒介: CVSS:3.0/E:P/RL:O/RC:C
弱點資訊
必要的 KB 項目: Host/local_checks_enabled, Host/CentOS/release, Host/CentOS/rpm-list, Host/OS/extended-third-party
可被惡意程式利用: true
可輕鬆利用: Exploits are available
修補程式發佈日期: 2026/10/17
弱點發布日期: 2021/7/21
參考資訊
CVE: CVE-2022-36946, CVE-2022-48702, CVE-2023-52531, CVE-2025-40026, CVE-2026-64471, CVE-2026-64483, CVE-2026-68329, CVE-2026-72129, CVE-2026-72323, CVE-2026-72383, CVE-2026-72413, CVE-2026-72476, CVE-2026-74287, CVE-2026-74359, CVE-2026-74408, CVE-2026-74444, CVE-2026-74479, CVE-2026-74498, CVE-2026-74505, CVE-2026-74550, CVE-2026-74556, CVE-2026-74569, CVE-2026-80536, CVE-2026-80584, CVE-2026-80622, CVE-2026-80681, CVE-2026-80829, CVE-2026-81001, CVE-2026-81003, CVE-2026-89448, CVE-2026-89542, CVE-2026-89548, CVE-2026-89549, CVE-2026-89550, CVE-2026-89553, CVE-2026-89574, CVE-2026-89575, CVE-2026-89633, CVE-2026-89637, CVE-2026-89699, CVE-2026-89778, CVE-2026-89786, CVE-2026-89893, CVE-2026-90011, CVE-2026-90033, CVE-2026-90057, CVE-2026-90116, CVE-2026-90203, CVE-2026-90329, CVE-2026-90413, CVE-2026-90414, CVE-2026-90421, CVE-2026-93117, CVE-2026-93189, CVE-2026-97408, CVE-2026-97445, CVE-2026-97455, CVE-2026-97536, CVE-2026-97539, CVE-2026-97564, CVE-2026-97608, CVE-2026-97931, CVE-2026-97949, CVE-2026-98077, CVE-2026-98185, CVE-2026-98186, CVE-2026-98196, CVE-2026-98217, CVE-2026-98222, CVE-2026-98266, CVE-2026-98269, CVE-2026-98312, CVE-2026-98342, CVE-2026-98354, CVE-2026-98375, CVE-2026-99999
CLSA: 2026:1792234299