AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個弱點 （ALMALINUX9.2：CLSA-2025：1747725447）
high Nessus Plugin ID 351518
語言:
概要
AlmaLinux 主機缺少一個或多個安全性更新。說明
AlmaLinux 9.2 主機已安裝的套件會受到 TuxCare ALMALINUX9.2：CLSA-2025：1747725447 公告中提及的多個弱點影響。- 已解決 Linux 核心中的下列弱點：hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations Commit b50aa49638c7 (hwmon: (lm90) Prevent integer underflows of temperature calculations) addressed a number of underflow situations when writing temperature limits. However, it missed one situation, seen when an attempt is made to set the hysteresis value to MAX_LONG and the critical temperature limit is negative. Use clamp_val() when setting the hysteresis temperature to ensure that the provided value can never overflow or underflow. (CVE-2021-47098)
- 已解決 Linux 核心中的下列弱點：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 <[email protected]> (https://lore.kernel.org/r/[email protected]) 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-47505)
- 啟用 SMT 時，某些 AMD 處理器可能會在 SMT 模式切換後使用同級執行緒的目標推測執行指令，這可能會導致資訊洩漏。(CVE-2022-27672)
- 已解決 Linux 核心中的下列弱點：watch_queue: Actually free the watch free_watch() does everything barring actually freeing the watch object. Fix this by adding the missing kfree. kmemleak produces a report something like the following. Note that as an address can be seen in the first word, the watch would appear to have gone through call_rcu(). BUG: memory leak unreferenced object 0xffff88810ce4a200 (size 96): comm syz-executor352, pid 3605, jiffies 4294947473 (age 13.720s) hex dump (first 32 bytes): e0 82 48 0d 81 88 ff ff 00 00 00 00 00 00 00 00 ..H............. 80 a2 e4 0c 81 88 ff ff 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff8214e6cc>] kmalloc include/linux/slab.h:581 [inline] [<ffffffff8214e6cc>] kzalloc include/linux/slab.h:714 [inline] [<ffffffff8214e6cc>] keyctl_watch_key+0xec/0x2e0 security/keys/keyctl.c:1800 [<ffffffff8214ec84>] __do_sys_keyctl+0x3c4/0x490 security/keys/keyctl.c:2016 [<ffffffff84493a25>] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [<ffffffff84493a25>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [<ffffffff84600068>] entry_SYSCALL_64_after_hwframe+0x44/0xae (CVE-2022-49256)
- Linux 核心的 netfilter: nf_tables 元件中有一個釋放後使用弱點，可遭惡意利用來提升本機權限。邊界鏈結的錯誤處理中存在瑕疵，可導致 NFT_MSG_NEWRULE 的中止路徑發生釋放後使用。利用此弱點需要觸發 CAP_NET_ADMIN。建議升級至前一個 Commit 4bedf9eee016286c835e3d8fa981ddece5338795。(CVE-2023-3610)
請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。
解決方案
根據 TuxCare 公告 ALMALINUX9.2：CLSA-2025：1747725447 中的指引更新受影響的套件。另請參閱
Plugin 詳細資訊
嚴重性: High
ID: 351518
檔案名稱: tuxcare_alma_linux_9.2_CLSA-2025-1747725447.nasl
版本: 1.2
類型: Local
已發布: 2026/9/30
已更新: 2026/10/21
支援的感應器: Nessus Agent, Continuous Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus
風險資訊
VPR
風險因素: Medium
分數: 6.9
百分位數: 97.35
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-2025-21969
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
修補程式發佈日期: 2025/5/20
弱點發布日期: 2021/7/21
參考資訊
CVE: CVE-2021-47098, CVE-2021-47505, CVE-2022-27672, CVE-2022-49256, CVE-2023-3610, CVE-2023-52454, CVE-2023-52518, CVE-2023-52572, CVE-2023-52664, CVE-2023-52757, CVE-2023-52922, CVE-2023-52988, CVE-2023-53107, CVE-2024-26736, CVE-2024-26892, CVE-2024-26928, CVE-2024-27008, CVE-2024-50275, CVE-2024-53068, CVE-2024-53099, CVE-2024-53168, CVE-2024-57947, CVE-2024-57980, CVE-2024-58002, CVE-2024-58069, CVE-2025-21702, CVE-2025-21718, CVE-2025-21780, CVE-2025-21785, CVE-2025-21791, CVE-2025-21858, CVE-2025-21905, CVE-2025-21920, CVE-2025-21927, CVE-2025-21928, CVE-2025-21969, CVE-2025-21993, CVE-2025-37785
CLSA: 2025:1747725447