AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個弱點 （ALMALINUX9.2：CLSA-2026：1792751700）
high Nessus Plugin ID 371223
語言:
概要
AlmaLinux 主機缺少一個或多個安全性更新。說明
AlmaLinux 9.2 主機已安裝的套件會受到 TuxCare ALMALINUX9.2：CLSA-2026：1792751700 公告中提及的多個弱點影響。- 已解決 Linux 核心中的下列弱點：ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg When len >= INT_MAX - transhdrlen, ulen = len + transhdrlen will be overflow. To fix, we can follow what udpv6 does and subtract the transhdrlen from the max. (CVE-2022-49727)
- 已解決 Linux 核心中的下列弱點：bpf: Fix accesses to uninit stack slots Privileged programs are supposed to be able to read uninitialized stack memory (ever since 6715df8d5) but, before this patch, these accesses were permitted inconsistently. In particular, accesses were permitted above state->allocated_stack, but not below it. In other words, if the stack was already large enough, the access was permitted, but otherwise the access was rejected instead of being allowed to grow the stack. This undesired rejection was happening in two places: - in check_stack_slot_within_bounds() - in check_stack_range_initialized() This patch arranges for these accesses to be permitted. A bunch of tests that were relying on the old rejection had to change; all of them were changed to add also run unprivileged, in which case the old behavior persists. One tests couldn't be updated - global_func16 - because it can't run unprivileged for other reasons. This patch also fixes the tracking of the stack size for variable-offset reads. This second fix is bundled in the same commit as the first one because they're inter-related. Before this patch, writes to the stack using registers containing a variable offset (as opposed to registers with fixed, known values) were not properly contributing to the function's needed stack size. As a result, it was possible for a program to verify, but then to attempt to read out-of-bounds data at runtime because a too small stack had been allocated for it. Each function tracks the size of the stack it needs in bpf_subprog_info.stack_depth, which is maintained by update_stack_depth(). For regular memory accesses, check_mem_access() was calling update_state_depth() but it was passing in only the fixed part of the offset register, ignoring the variable offset. This was incorrect; the minimum possible value of that register should be used instead.
This tracking is now fixed by centralizing the tracking of stack size in grow_stack_state(), and by lifting the calls to grow_stack_state() to check_stack_access_within_bounds() as suggested by Andrii. The code is now simpler and more convincingly tracks the correct maximum stack size.
check_stack_range_initialized() can now rely on enough stack having been allocated for the access; this helps with the fix for the first issue. A few tests were changed to also check the stack depth computation. The one that fails without this patch is verifier_var_off:stack_write_priv_vs_unpriv.
(CVE-2023-52452)
- 已解決 Linux 核心中的下列弱點：qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info We have to make sure that the info returned by the helper is valid before using it. Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.
(CVE-2023-53066)
- 已解決 Linux 核心中的下列弱點：SUNRPC: Fix a server shutdown leak Fix a race where kthread_stop() may prevent the threadfn from ever getting called. If that happens the svc_rqst will not be cleaned up. (CVE-2023-53131)
- 已解決 Linux 核心中的下列弱點：pstore/ram: Add check for kstrdup Add check for the return value of kstrdup() and return the error if it fails in order to avoid NULL pointer dereference. (CVE-2023-54189)
請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。
解決方案
根據 TuxCare 公告 ALMALINUX9.2：CLSA-2026：1792751700 中的指引更新受影響的套件。另請參閱
Plugin 詳細資訊
嚴重性: High
ID: 371223
檔案名稱: tuxcare_alma_linux_9.2_CLSA-2026-1792751700.nasl
版本: 1.1
類型: Local
已發布: 2026/10/23
已更新: 2026/10/23
支援的感應器: Nessus Agent, Continuous Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus
風險資訊
VPR
風險因素: High
分數: 7.7
百分位數: 98.94
Vendor
Vendor Severity: Important
CVSS v2
風險因素: Medium
基本分數: 6.8
時間性分數: 5
媒介: CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C
CVSS 評分資料來源: CVE-2026-64362
CVSS v3
風險因素: High
基本分數: 7.8
時間性分數: 6.8
媒介: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
時間媒介: CVSS:3.0/E:U/RL:O/RC:C
弱點資訊
必要的 KB 項目: Host/local_checks_enabled, Host/cpu, Host/AlmaLinux/release, Host/AlmaLinux/rpm-list, Host/OS/extended-third-party
可輕鬆利用: No known exploits are available
修補程式發佈日期: 2026/10/23
弱點發布日期: 2021/7/21
參考資訊
CVE: CVE-2022-49727, CVE-2023-52452, CVE-2023-53066, CVE-2023-53131, CVE-2023-54189, CVE-2023-54193, CVE-2024-26881, CVE-2024-35999, CVE-2024-50017, CVE-2024-53185, CVE-2025-40187, CVE-2026-31447, CVE-2026-31511, CVE-2026-43042, CVE-2026-45984, CVE-2026-46033, CVE-2026-46116, CVE-2026-46120, CVE-2026-46150, CVE-2026-46209, CVE-2026-46227, CVE-2026-46266, CVE-2026-46324, CVE-2026-52923, CVE-2026-52956, CVE-2026-52986, CVE-2026-53004, CVE-2026-53006, CVE-2026-53059, CVE-2026-53078, CVE-2026-53089, CVE-2026-53129, CVE-2026-53131, CVE-2026-53275, CVE-2026-63794, CVE-2026-63808, CVE-2026-63922, CVE-2026-63927, CVE-2026-63993, CVE-2026-64002, CVE-2026-64007, CVE-2026-64009, CVE-2026-64015, CVE-2026-64018, CVE-2026-64047, CVE-2026-64113, CVE-2026-64114, CVE-2026-64189, CVE-2026-64191, CVE-2026-64276, CVE-2026-64277, CVE-2026-64351, CVE-2026-64362, CVE-2026-64378, CVE-2026-64546, CVE-2026-64556, CVE-2026-72476, CVE-2026-74255, CVE-2026-74282, CVE-2026-74283, CVE-2026-74289, CVE-2026-74394, CVE-2026-74408, CVE-2026-74444, CVE-2026-74465, CVE-2026-74505, CVE-2026-74510, CVE-2026-74540, CVE-2026-74569, CVE-2026-74581, CVE-2026-74753, CVE-2026-80590, CVE-2026-80613, CVE-2026-80994, CVE-2026-89508, CVE-2026-89559, CVE-2026-89575, CVE-2026-89699, CVE-2026-89729, CVE-2026-89786, CVE-2026-89847, CVE-2026-89932, CVE-2026-89965, CVE-2026-90033, CVE-2026-93288, CVE-2026-93822, CVE-2026-93830, CVE-2026-97427, CVE-2026-97448, CVE-2026-97509, CVE-2026-97539, CVE-2026-97540, CVE-2026-97596, CVE-2026-97608, CVE-2026-97611, CVE-2026-97612, CVE-2026-97940, CVE-2026-98015, CVE-2026-98025, CVE-2026-98077, CVE-2026-98130, CVE-2026-98185, CVE-2026-98196, CVE-2026-98264, CVE-2026-98276, CVE-2026-98364
CLSA: 2026:1792751700