AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / etc 多個弱點 （ALMALINUX9.2：CLSA-2026：1786350974）
high Nessus Plugin ID 360716
語言:
概要
AlmaLinux 主機缺少一或多個安全性更新。說明
AlmaLinux 9.2 主機已安裝的套件會受到 TuxCare ALMALINUX9.2：CLSA-2026：1786350974 公告中提及的多個弱點影響。- 已解決 Linux 核心中的下列弱點：isofs: Fix out of bound access for corrupted isofs image When isofs image is suitably corrupted isofs_read_inode() can read data beyond the end of buffer. Sanity-check the directory entry length before using it. (CVE-2021-47478)
- 已解決 Linux 核心中的下列弱點：ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl Hulk Robot reported a KASAN report about use-after-free:
================================================================== BUG: KASAN: use-after-free in
__list_del_entry_valid+0x13d/0x160 Read of size 8 at addr ffff888035e37d98 by task ubiattach/1385 [...] Call Trace: klist_dec_and_del+0xa7/0x4a0 klist_put+0xc7/0x1a0 device_del+0x4d4/0xed0 cdev_device_del+0x1a/0x80 ubi_attach_mtd_dev+0x2951/0x34b0 [ubi] ctrl_cdev_ioctl+0x286/0x2f0 [ubi] Allocated by task 1414: device_add+0x60a/0x18b0 cdev_device_add+0x103/0x170 ubi_create_volume+0x1118/0x1a10 [ubi] ubi_cdev_ioctl+0xb7f/0x1ba0 [ubi] Freed by task 1385:
cdev_device_del+0x1a/0x80 ubi_remove_volume+0x438/0x6c0 [ubi] ubi_cdev_ioctl+0xbf4/0x1ba0 [ubi] [...] ================================================================== The lock held by ctrl_cdev_ioctl is ubi_devices_mutex, but the lock held by ubi_cdev_ioctl is ubi->device_mutex. Therefore, the two locks can be concurrent. ctrl_cdev_ioctl contains two operations: ubi_attach and ubi_detach. ubi_detach is bug-free because it uses reference counting to prevent concurrency. However, uif_init and uif_close in ubi_attach may race with ubi_cdev_ioctl. uif_init will race with ubi_cdev_ioctl as in the following stack. cpu1 cpu2 cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_add_volume // sysfs exist kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // first free ubi_free_volume cdev_del // double free cdev_device_del And uif_close will race with ubi_cdev_ioctl as in the following stack. cpu1 cpu2 cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_debugfs_init_dev //error goto out_uif; uif_close kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // first free ubi_free_volume // double free The cause of this problem is that commit 714fb87e8bc0 make device available before it becomes accessible via sysfs. Therefore, we roll back the modification. We will fix the race condition between ubi device creation and udev by removing ubi_get_device in vol_attribute_show and dev_attribute_show.This avoids accessing uninitialized ubi_devices[ubi_num]. ubi_get_device is used to prevent devices from being deleted during sysfs execution. However, now kernfs ensures that devices will not be deleted before all reference counting are released. The key process is shown in the following stack. device_del device_remove_attrs device_remove_groups sysfs_remove_groups sysfs_remove_group remove_files kernfs_remove_by_name kernfs_remove_by_name_ns __kernfs_remove kernfs_drain (CVE-2021-47634)
- 已解決 Linux 核心中的下列弱點：scsi: qla2xxx: Fix memory leak in
__qlt_24xx_handle_abts() Commit 8f394da36a36 (scsi: qla2xxx: Drop TARGET_SCF_LOOKUP_LUN_FROM_TAG) made the __qlt_24xx_handle_abts() function return early if tcm_qla2xxx_find_cmd_by_tag() didn't find a command, but it missed to clean up the allocated memory for the management command. (CVE-2022-48650)
- 已解決 Linux 核心中的下列弱點：ubi: ubi_create_volume: Fix use-after-free when volume creation failed There is an use-after-free problem for 'eba_tbl' in ubi_create_volume()'s error handling path: ubi_eba_replace_table(vol, eba_tbl) vol->eba_tbl = tbl out_mapping:
ubi_eba_destroy_table(eba_tbl) // Free 'eba_tbl' out_unlock: put_device(&vol->dev) vol_release kfree(tbl->entries) // UAF Fix it by removing redundant 'eba_tbl' releasing. Fetch a reproducer in [Link].
(CVE-2022-49388)
- 已解決 Linux 核心中的下列弱點：irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. When kcalloc fails, it missing of_node_put() and results in refcount leak. Fix this by goto out_put_node label. (CVE-2022-49716)
請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。
解決方案
根據 TuxCare 公告 ALMALINUX9.2：CLSA-2026：1786350974 中的指引更新受影響的套件。另請參閱
Plugin 詳細資訊
嚴重性: High
ID: 360716
檔案名稱: tuxcare_alma_linux_9.2_CLSA-2026-1786350974.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
分數: 8
百分位數: 99.68
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-53120
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/8/10
弱點發布日期: 2021/7/21
參考資訊
CVE: CVE-2021-47478, CVE-2021-47634, CVE-2022-48650, CVE-2022-48657, CVE-2022-49388, CVE-2022-49716, CVE-2022-49740, CVE-2022-50406, CVE-2022-50628, CVE-2023-52456, CVE-2023-52849, CVE-2023-52855, CVE-2023-53250, CVE-2023-53452, CVE-2023-53543, CVE-2023-53603, CVE-2023-53659, CVE-2023-53698, CVE-2023-53798, CVE-2023-54108, CVE-2024-39480, CVE-2024-40908, CVE-2024-42109, CVE-2024-42138, CVE-2024-42162, CVE-2024-47734, CVE-2024-56625, CVE-2024-56745, CVE-2024-57917, CVE-2024-58061, CVE-2025-21700, CVE-2025-21701, CVE-2025-21916, CVE-2025-21936, CVE-2025-21937, CVE-2025-38113, CVE-2025-38239, CVE-2025-38593, CVE-2025-39701, CVE-2025-39776, CVE-2025-39860, CVE-2025-39861, CVE-2025-39877, CVE-2025-39894, CVE-2025-40030, CVE-2025-40035, CVE-2025-40044, CVE-2025-40211, CVE-2025-40264, CVE-2025-40275, CVE-2025-40280, CVE-2025-40324, CVE-2025-68185, CVE-2025-68288, CVE-2025-68372, CVE-2025-71064, CVE-2025-71224, CVE-2026-23058, CVE-2026-23242, CVE-2026-23262, CVE-2026-23340, CVE-2026-23343, CVE-2026-23359, CVE-2026-23454, CVE-2026-23456, CVE-2026-31469, CVE-2026-31487, CVE-2026-31504, CVE-2026-31520, CVE-2026-31522, CVE-2026-31527, CVE-2026-31638, CVE-2026-31639, CVE-2026-31649, CVE-2026-31667, CVE-2026-31688, CVE-2026-31697, CVE-2026-31758, CVE-2026-31773, CVE-2026-43047, CVE-2026-43059, CVE-2026-43111, CVE-2026-43114, CVE-2026-43133, CVE-2026-43180, CVE-2026-43233, CVE-2026-43304, CVE-2026-43334, CVE-2026-43339, CVE-2026-43432, CVE-2026-43466, CVE-2026-43473, CVE-2026-45982, CVE-2026-45996, CVE-2026-45997, CVE-2026-46006, CVE-2026-46024, CVE-2026-46070, CVE-2026-46079, CVE-2026-46092, CVE-2026-46094, CVE-2026-46107, CVE-2026-46178, CVE-2026-46304, CVE-2026-46320, CVE-2026-52954, CVE-2026-52958, CVE-2026-53003, CVE-2026-53088, CVE-2026-53112, CVE-2026-53118, CVE-2026-53120, CVE-2026-53146, CVE-2026-53147, CVE-2026-53252, CVE-2026-53253, CVE-2026-53350, CVE-2026-64561
CLSA: 2026:1786350974