AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / etc 多個弱點 （ALMALINUX9.2：CLSA-2026：1783791447）
medium Nessus Plugin ID 352871
語言:
概要
AlmaLinux 主機缺少一或多個安全性更新。說明
AlmaLinux 9.2 主機安裝的套件會受到 TuxCare ALMALINUX9.2：CLSA-2026：1783791447 公告中提及的多個弱點影響。- 已解決 Linux 核心中的下列弱點：phy: mdio: fix memory leak Syzbot reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but device_register() was called In case of device_register() has been called we should call put_device() to correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_ calling device_register(), because put_device() should be called even in case of device_register() failure. (CVE-2021-47416)
- 在 Linux 核心的 TeleTYpe 子系統中發現超出邊界讀取缺陷。由於 flush_to_ldisc 函式中存在記憶體洩漏弱點，使用者利用 ioctls 的 TIOCSPTLCK、TIOCGPTPEER、TIOCSTI 和 TCXONC 觸發爭用情形時會發生此問題。本機使用者可利用此缺陷造成系統當機，或從記憶體讀取未經授權的隨機資料。(CVE-2022-1462)
- 已解決 Linux 核心中的下列弱點：can: isotp: sanitize CAN ID checks in isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached with a compliant CAN ID address configuration. The provided address information consisted of CAN ID 0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)
- 已解決 Linux 核心中的下列弱點：tty: fix deadlock caused by calling printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2 ----
---- ---- lock(console_owner); lock(&port_lock_key); lock(&port->lock); lock(&port_lock_key);
lock(&port->lock); lock(console_owner); As commit dbdda842fe96 (printk: Add console owner and waiter logic to load balance console writes) said, such deadlock can be prevented by using printk_deferred() in kmalloc() (which is invoked in the section guarded by the port->lock). But there are too many printk() on the kmalloc() path, and kmalloc() can be called from anywhere, so changing printk() to printk_deferred() is too complicated and inelegant. Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so that printk() will not be called, and this deadlock problem can be avoided. Syzbot reported the following lockdep error: ====================================================== WARNING: possible circular locking dependency detected 5.4.143-00237-g08ccc19a-dirty #10 Not tainted
------------------------------------------------------ syz-executor.4/29420 is trying to acquire lock:
ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752 [inline] ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470 kernel/printk/printk.c:2023 but task is already holding lock: ffff8880119c9158 (&port->lock){-.-.}-{2:2}, at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&port->lock){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159 tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock);
tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x530/0xa80 drivers/tty/serial/8250/8250_port.c:1767 serial8250_handle_irq.part.0+0x31f/0x3d0 drivers/tty/serial/8250/8250_port.c:1854 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827 [inline] <-- lock(&port_lock_key); serial8250_default_handle_irq+0xb2/0x220 drivers/tty/serial/8250/8250_port.c:1870 serial8250_interrupt+0xfd/0x200 drivers/tty/serial/8250/8250_core.c:126 __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156 [...] -> #1 (&port_lock_key){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159 serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 <-- lock(&port_lock_key);
call_console_drivers kernel/printk/printk.c:1819 [inline] console_unlock+0x8cb/0xd00 kernel/printk/printk.c:2504 vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner);
vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 printk+0xba/0xed kernel/printk/printk.c:2084 register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 univ8250_console_init+0x3a/0x46 drivers/tty/serial/8250/8250_core.c:681 console_init+0x49d/0x6d3 kernel/printk/printk.c:2915 start_kernel+0x5e9/0x879 init/main.c:713 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 -> #0 (console_owner){....}-{0:0}: [...] lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734 console_trylock_spinning kernel/printk/printk.c:1773 ---truncated--- (CVE-2022-49441)
- 已解決 Linux 核心中的下列弱點：list: fix a data-race around ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait()) made some ep_events_available() calls lockless and added single call under a lock, finally commit e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available() lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40 fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281 [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80 fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40 fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281 [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80 fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 -> 0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 (CVE-2022-49443)
請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。
解決方案
根據 TuxCare 公告 ALMALINUX9.2：CLSA-2026：1783791447 中的指引更新受影響的套件。另請參閱
Plugin 詳細資訊
嚴重性: Medium
ID: 352871
檔案名稱: tuxcare_alma_linux_9.2_CLSA-2026-1783791447.nasl
版本: 1.2
類型: Local
已發布: 2026/9/30
已更新: 2026/10/1
支援的感應器: Continuous Assessment, Nessus Agent, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus
風險資訊
VPR
風險因素: Critical
分數: 9.5
百分位數: 99.87
Vendor
Vendor Severity: Important
CVSS v2
風險因素: Low
基本分數: 3.3
時間性分數: 2.9
媒介: CVSS2#AV:L/AC:M/Au:N/C:P/I:N/A:P
CVSS 評分資料來源: CVE-2022-1462
CVSS v3
風險因素: Medium
基本分數: 6.3
時間性分數: 6
媒介: CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
時間媒介: CVSS:3.0/E:H/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/7/11
弱點發布日期: 2021/7/21
參考資訊
CVE: CVE-2021-4454, CVE-2021-47416, CVE-2022-1462, CVE-2022-48660, CVE-2022-48961, CVE-2022-48971, CVE-2022-48975, CVE-2022-49269, CVE-2022-49390, CVE-2022-49441, CVE-2022-49443, CVE-2022-49728, CVE-2022-49749, CVE-2022-49764, CVE-2022-49766, CVE-2022-49796, CVE-2022-49797, CVE-2022-49824, CVE-2022-49825, CVE-2022-49873, CVE-2022-49891, CVE-2022-50498, CVE-2023-52523, CVE-2023-52582, CVE-2023-52672, CVE-2023-52738, CVE-2023-52786, CVE-2023-52845, CVE-2023-52877, CVE-2023-52898, CVE-2023-52932, CVE-2023-52937, CVE-2023-52977, CVE-2023-52981, CVE-2023-52991, CVE-2023-53002, CVE-2023-53013, CVE-2023-53015, CVE-2023-53018, CVE-2023-53026, CVE-2023-53093, CVE-2023-53109, CVE-2023-53240, CVE-2023-53245, CVE-2023-53291, CVE-2023-53332, CVE-2023-53438, CVE-2023-53475, CVE-2023-53491, CVE-2023-53499, CVE-2023-53517, CVE-2023-53548, CVE-2023-53635, CVE-2023-53667, CVE-2023-53685, CVE-2023-53792, CVE-2023-53852, CVE-2023-53857, CVE-2023-53999, CVE-2023-54019, CVE-2023-54057, CVE-2023-54160, CVE-2023-54254, CVE-2023-54271, CVE-2023-54276, CVE-2023-54323, CVE-2024-26631, CVE-2024-26645, CVE-2024-26663, CVE-2024-26671, CVE-2024-26675, CVE-2024-26698, CVE-2024-26719, CVE-2024-26733, CVE-2024-26760, CVE-2024-26837, CVE-2024-26840, CVE-2024-26851, CVE-2024-26861, CVE-2024-26862, CVE-2024-26878, CVE-2024-26906, CVE-2024-26953, CVE-2024-26987, CVE-2024-35904, CVE-2024-35922, CVE-2024-36008, CVE-2024-36478, CVE-2024-36882, CVE-2024-36975, CVE-2024-38598, CVE-2024-38600, CVE-2024-38612, CVE-2024-40904, CVE-2024-40924, CVE-2024-40980, CVE-2024-41009, CVE-2024-41027, CVE-2024-41038, CVE-2024-41063, CVE-2024-41088, CVE-2024-41089, CVE-2024-42107, CVE-2024-42114, CVE-2024-42129, CVE-2024-42241, CVE-2024-42244, CVE-2024-42246, CVE-2024-42259, CVE-2024-42286, CVE-2024-43834, CVE-2024-43835, CVE-2024-43908, CVE-2024-44958, CVE-2024-45000, CVE-2024-45009, CVE-2024-45010, CVE-2024-45016, CVE-2024-46715, CVE-2024-46755, CVE-2024-46770, CVE-2024-46787, CVE-2024-47660, CVE-2024-47679, CVE-2024-47693, CVE-2024-47703, CVE-2024-47705, CVE-2024-47720, CVE-2024-47739, CVE-2024-47809, CVE-2024-49934, CVE-2024-49935, CVE-2024-49955, CVE-2024-49968, CVE-2024-50000, CVE-2024-50014, CVE-2024-50028, CVE-2024-50041, CVE-2024-50045, CVE-2024-50046, CVE-2024-50058, CVE-2024-50077, CVE-2024-50110, CVE-2024-50160, CVE-2024-50185, CVE-2024-50251, CVE-2024-50256, CVE-2024-50271, CVE-2024-53051, CVE-2024-53055, CVE-2024-53091, CVE-2024-53119, CVE-2024-53125, CVE-2024-53224, CVE-2024-53680, CVE-2024-56544, CVE-2024-56569, CVE-2024-56611, CVE-2024-56657, CVE-2024-56712, CVE-2024-57948, CVE-2024-57974, CVE-2024-57981, CVE-2024-57993, CVE-2024-57996, CVE-2024-58005, CVE-2024-58012, CVE-2024-58079, CVE-2025-21638, CVE-2025-21640, CVE-2025-21649, CVE-2025-21681, CVE-2025-21682, CVE-2025-21683, CVE-2025-21694, CVE-2025-21731, CVE-2025-21732, CVE-2025-21806, CVE-2025-21831, CVE-2025-21838, CVE-2025-21846, CVE-2025-21853, CVE-2025-21861, CVE-2025-21877, CVE-2025-21881, CVE-2025-21888, CVE-2025-21891, CVE-2025-21931, CVE-2025-21959, CVE-2025-21961, CVE-2025-22025, CVE-2025-22057, CVE-2025-22089, CVE-2025-22090, CVE-2025-22111, CVE-2025-23131, CVE-2025-23143, CVE-2025-23144, CVE-2025-23145, CVE-2025-37800, CVE-2025-37807, CVE-2025-37808, CVE-2025-37834, CVE-2025-37853, CVE-2025-37867, CVE-2025-37884, CVE-2025-37920, CVE-2025-37938, CVE-2025-37959, CVE-2025-37961, CVE-2025-37967, CVE-2025-37980, CVE-2025-38039, CVE-2025-38040, CVE-2025-38064, CVE-2025-38067, CVE-2025-38097, CVE-2025-38148, CVE-2025-38162, CVE-2025-38192, CVE-2025-38193, CVE-2025-38232, CVE-2025-38234, CVE-2025-38426, CVE-2025-38436, CVE-2025-38524, CVE-2025-38591, CVE-2025-38643, CVE-2025-38659, CVE-2025-38665, CVE-2025-38709, CVE-2025-38710, CVE-2025-39705, CVE-2025-39754, CVE-2025-39843, CVE-2025-39851, CVE-2025-39927, CVE-2025-39937, CVE-2025-39940, CVE-2025-39947, CVE-2025-39961, CVE-2025-40121, CVE-2025-40167, CVE-2025-40194, CVE-2025-40321, CVE-2025-40331, CVE-2025-68211, CVE-2025-68223, CVE-2025-68813, CVE-2025-68820, CVE-2025-71087, CVE-2025-71094, CVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71127, CVE-2025-71147, CVE-2025-71160, CVE-2025-71161, CVE-2025-71225, CVE-2025-71227, CVE-2025-71297, CVE-2026-22979, CVE-2026-22994, CVE-2026-22997, CVE-2026-23000, CVE-2026-23004, CVE-2026-23038, CVE-2026-23066, CVE-2026-23069, CVE-2026-23086, CVE-2026-23103, CVE-2026-23138, CVE-2026-23154, CVE-2026-23169, CVE-2026-23210, CVE-2026-23247, CVE-2026-23255, CVE-2026-23302, CVE-2026-23374, CVE-2026-23401, CVE-2026-23468, CVE-2026-23472, CVE-2026-31480, CVE-2026-31495, CVE-2026-31518, CVE-2026-31531, CVE-2026-31546, CVE-2026-31551, CVE-2026-31555, CVE-2026-31628, CVE-2026-31677, CVE-2026-31692, CVE-2026-31752, CVE-2026-31777, CVE-2026-43038, CVE-2026-43053, CVE-2026-43234, CVE-2026-43266, CVE-2026-43273, CVE-2026-43277, CVE-2026-43329, CVE-2026-43439, CVE-2026-43493, CVE-2026-43499
CLSA: 2026:1783791447