AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / etc 多個弱點 （ALMALINUX9.2：CLSA-2026：1781347338）
high Nessus Plugin ID 360826
語言:
概要
AlmaLinux 主機缺少一或多個安全性更新。說明
AlmaLinux 9.2 主機已安裝的套件會受到 TuxCare ALMALINUX9.2：CLSA-2026：1781347338 公告中提及的多個弱點影響。- 已解決 Linux 核心中的下列弱點：net: mdio: unexport __init-annotated mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean) (CVE-2022-49350)
- 已解決 Linux 核心中的下列弱點：selinux: fix memleak in security_read_state_kernel() In this function, it directly returns the result of __security_read_policy without freeing the allocated memory in *data, cause memory leak issue, so free the memory if
__security_read_policy failed. [PM: subject line tweak] (CVE-2022-50201)
- 已解決 Linux 核心中的下列弱點：usb: typec: tcpci: fix of node refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /i2c/pmic@34/tcpc/connector The 'fwnode' set in tcpci_parse_config() which is called in tcpci_register_port(), its node refcount is increased in device_get_named_child_node(). It needs be put while exiting, so call fwnode_handle_put() in the error path of tcpci_register_port() and in tcpci_unregister_port() to avoid leak. (CVE-2022-50246)
- 已解決 Linux 核心中的下列弱點：drivers: serial: jsm: fix some leaks in probe This error path needs to unwind instead of just returning directly. (CVE-2022-50312)
- 已解決 Linux 核心中的下列弱點：thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash When CPU 0 is offline and intel_powerclamp is used to inject idle, it generates kernel BUG: BUG: using smp_processor_id() in preemptible [00000000] code:
bash/15687 caller is debug_smp_processor_id+0x17/0x20 CPU: 4 PID: 15687 Comm: bash Not tainted 5.19.0-rc7+ #57 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 check_preemption_disabled+0xdd/0xe0 debug_smp_processor_id+0x17/0x20 powerclamp_set_cur_state+0x7f/0xf9 [intel_powerclamp] ... ... Here CPU 0 is the control CPU by default and changed to the current CPU, if CPU 0 offlined. This check has to be performed under cpus_read_lock(), hence the above warning. Use get_cpu() instead of smp_processor_id() to avoid this BUG. [ rjw: Subject edits ] (CVE-2022-50494)
請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。
解決方案
根據 TuxCare 公告 ALMALINUX9.2：CLSA-2026：1781347338 中的指引更新受影響的套件。另請參閱
Plugin 詳細資訊
嚴重性: High
ID: 360826
檔案名稱: tuxcare_alma_linux_9.2_CLSA-2026-1781347338.nasl
版本: 1.1
類型: Local
已發布: 2026/10/1
已更新: 2026/10/1
支援的感應器: Continuous Assessment, Nessus Agent, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus
風險資訊
VPR
風險因素: High
分數: 7.9
百分位數: 99.36
Vendor
Vendor Severity: Important
CVSS v2
風險因素: Medium
基本分數: 6.8
時間性分數: 5.3
媒介: CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C
CVSS 評分資料來源: CVE-2026-43128
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/OS/extended-third-party, Host/local_checks_enabled, Host/AlmaLinux/release, Host/AlmaLinux/rpm-list, Host/cpu
可被惡意程式利用: true
可輕鬆利用: Exploits are available
修補程式發佈日期: 2026/6/13
弱點發布日期: 2021/7/21
參考資訊
CVE: CVE-2022-49350, CVE-2022-50201, CVE-2022-50246, CVE-2022-50312, CVE-2022-50494, CVE-2022-50510, CVE-2022-50578, CVE-2022-50883, CVE-2023-52703, CVE-2023-52795, CVE-2023-52798, CVE-2023-52814, CVE-2023-52851, CVE-2023-52942, CVE-2023-52974, CVE-2023-52996, CVE-2023-53051, CVE-2023-53058, CVE-2023-53073, CVE-2023-53078, CVE-2023-53095, CVE-2023-53102, CVE-2023-53120, CVE-2023-53275, CVE-2023-53334, CVE-2023-53335, CVE-2023-53408, CVE-2023-53546, CVE-2023-53549, CVE-2023-53598, CVE-2023-53605, CVE-2023-53612, CVE-2023-54106, CVE-2023-54322, CVE-2024-26742, CVE-2024-26843, CVE-2024-27012, CVE-2024-27013, CVE-2024-27436, CVE-2024-36920, CVE-2024-41098, CVE-2024-43879, CVE-2024-46783, CVE-2024-46830, CVE-2024-47696, CVE-2024-50003, CVE-2024-56679, CVE-2024-56726, CVE-2024-57897, CVE-2025-21758, CVE-2025-21759, CVE-2025-21763, CVE-2025-21764, CVE-2025-21765, CVE-2025-21766, CVE-2025-21975, CVE-2025-22008, CVE-2025-37852, CVE-2025-37949, CVE-2025-38512, CVE-2026-23111, CVE-2026-23286, CVE-2026-23304, CVE-2026-23307, CVE-2026-31408, CVE-2026-31590, CVE-2026-43026, CVE-2026-43035, CVE-2026-43036, CVE-2026-43043, CVE-2026-43068, CVE-2026-43079, CVE-2026-43080, CVE-2026-43085, CVE-2026-43107, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128, CVE-2026-43132, CVE-2026-43167, CVE-2026-43216, CVE-2026-43251, CVE-2026-43303, CVE-2026-43315, CVE-2026-43381, CVE-2026-43411, CVE-2026-43425, CVE-2026-43453
CLSA: 2026:1781347338