Rocky Linux 9.6 [TuxCare] 安全更新：kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / 等多个漏洞 （ALMALINUX9.6：CLSA-2026：1793100968）
high Nessus 插件 ID 373068
语言：
简介
Rocky Linux 主机缺少一个或多个安全更新。描述
如 TuxCare ALMALINUX9.6：CLSA-2026：1793100968公告所述，Rocky Linux 9.6 主机上安装的程序包受到多个漏洞的影响。- 已修复 Linux 内核中的下列漏洞：udf: Avoid double brelse() in udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING:
CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace: <TASK> invalidate_bh_lru+0x99/0x150 smp_call_function_many_cond+0xe2a/0x10c0 ? generic_remap_file_range_prep+0x50/0x50 ? __brelse+0xa0/0xa0 ? __mutex_lock+0x21c/0x12d0 ? smp_call_on_cpu+0x250/0x250 ? rcu_read_lock_sched_held+0xb/0x60 ? lock_release+0x587/0x810 ?
__brelse+0xa0/0xa0 ? generic_remap_file_range_prep+0x50/0x50 on_each_cpu_cond_mask+0x3c/0x80 blkdev_flush_mapping+0x13a/0x2f0 blkdev_put_whole+0xd3/0xf0 blkdev_put+0x222/0x760 deactivate_locked_super+0x96/0x160 deactivate_super+0xda/0x100 cleanup_mnt+0x222/0x3d0 task_work_run+0x149/0x240 ? task_work_cancel+0x30/0x30 do_exit+0xb29/0x2a40 ? reacquire_held_locks+0x4a0/0x4a0 ? do_raw_spin_lock+0x12a/0x2b0 ? mm_update_next_owner+0x7c0/0x7c0 ? rwlock_bug.part.0+0x90/0x90 ? zap_other_threads+0x234/0x2d0 do_group_exit+0xd0/0x2a0
__x64_sys_exit_group+0x3a/0x50 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd The cause of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it returns NULL. However, brelse() is called by udf_rename(), too. So, b_count on buffer_head becomes unbalanced. This patch fixes the issue by not calling brelse() by udf_rename() when udf_find_entry() returns NULL. (CVE-2022-50755)
- 已修复 Linux 内核中的下列漏洞：soc: qcom: qmi_encdec: Restrict string length in decode The QMI TLV value for strings in a lot of qmi element info structures account for null terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of bounds access when the NULL character is appended in decoding. (CVE-2023-53729)
- 已修复 Linux 内核中的下列漏洞：can: isotp: check CAN address family in isotp_bind() Add missing check to block non-AF_CAN binds. Syzbot created some code which matched the right sockaddr struct size but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family field:
bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10) ^^^^ This has no funtional impact but the userspace should be notified about the wrong address family field content. (CVE-2023-54105)
- 已修复 Linux 内核中的下列漏洞：usb: rndis_host: Secure rndis_query check against int overflow Variables off and len typed as uint32 in rndis_query function are controlled by incoming RNDIS response message thus their value may be manipulated. Setting off to a unexpectetly large value will cause the sum with len and 8 to overflow and pass the implemented validation step. Consequently the response pointer will be referring to a location past the expected buffer boundaries allowing information leakage e.g. via RNDIS_OID_802_3_PERMANENT_ADDRESS OID. (CVE-2023-54110)
- 已修复 Linux 内核中的下列漏洞：mtd: spi-nor: Fix shift-out-of-bounds in spi_nor_set_erase_type spi_nor_set_erase_type() was used either to set or to mask out an erase type.
When we used it to mask out an erase type a shift-out-of-bounds was hit: UBSAN: shift-out-of-bounds in drivers/mtd/spi-nor/core.c:2237:24 shift exponent 4294967295 is too large for 32-bit type 'int' The setting of the size_{shift, mask} and of the opcode are unnecessary when the erase size is zero, as throughout the code just the erase size is considered to determine whether an erase type is supported or not. Setting the opcode to 0xFF was wrong too as nobody guarantees that 0xFF is an unused opcode. Thus when masking out an erase type, just set the erase size to zero. This will fix the shift-out-of-bounds.
[ta: refine changes, new commit message, fix compilation error] (CVE-2023-54295)
请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。
解决方案
根据 TuxCare 公告 ALMALINUX9.6：CLSA-2026：1793100968 中的指南更新受影响的程序包。另见
插件详情
严重性: High
ID: 373068
文件名: tuxcare_rocky_linux_9.6_CLSA-2026-1793100968.nasl
版本: 1.1
类型: Local
发布时间: 2026/10/28
最近更新时间: 2026/10/28
支持的传感器: Nessus Agent, Continuous Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus
风险信息
VPR
风险因素: High
分数: 7.6
百分位: 98.14
Vendor
Vendor Severity: Critical
CVSS v2
风险因素: Medium
基本分数: 6.8
时间分数: 5
矢量: CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C
CVSS 分数来源: CVE-2026-64363
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/RockyLinux/release, Host/RockyLinux/rpm-list, Host/OS/extended-third-party
易利用性: No known exploits are available
补丁发布日期: 2026/10/27
漏洞发布日期: 2021/7/21
参考资料信息
CVE: CVE-2022-50755, CVE-2023-53631, CVE-2023-53729, CVE-2023-54046, CVE-2023-54099, CVE-2023-54105, CVE-2023-54110, CVE-2023-54295, CVE-2024-53114, CVE-2025-21921, CVE-2025-23138, CVE-2025-23149, CVE-2025-37820, CVE-2025-37889, CVE-2025-37895, CVE-2025-37921, CVE-2025-38270, CVE-2025-38290, CVE-2025-38318, CVE-2025-38414, CVE-2025-38586, CVE-2025-38605, CVE-2025-39678, CVE-2025-39732, CVE-2025-39765, CVE-2025-39968, CVE-2025-39970, CVE-2025-39972, CVE-2025-39998, CVE-2025-40006, CVE-2025-40020, CVE-2025-40026, CVE-2025-40049, CVE-2025-40053, CVE-2025-40057, CVE-2025-40081, CVE-2025-40110, CVE-2025-40121, CVE-2025-40125, CVE-2025-40140, CVE-2025-40319, CVE-2025-40338, CVE-2025-40339, CVE-2025-40342, CVE-2025-40343, CVE-2025-40346, CVE-2025-68190, CVE-2025-68239, CVE-2025-68286, CVE-2025-68308, CVE-2025-68354, CVE-2025-68379, CVE-2025-68732, CVE-2025-68783, CVE-2025-68798, CVE-2025-71130, CVE-2025-71294, CVE-2026-100075, CVE-2026-23116, CVE-2026-23163, CVE-2026-23172, CVE-2026-23264, CVE-2026-23292, CVE-2026-23475, CVE-2026-31454, CVE-2026-31470, CVE-2026-31647, CVE-2026-31699, CVE-2026-31767, CVE-2026-43041, CVE-2026-43153, CVE-2026-43213, CVE-2026-43248, CVE-2026-43261, CVE-2026-43298, CVE-2026-43395, CVE-2026-43443, CVE-2026-43444, CVE-2026-43463, CVE-2026-43491, CVE-2026-45853, CVE-2026-45859, CVE-2026-45891, CVE-2026-45920, CVE-2026-45932, CVE-2026-45940, CVE-2026-45947, CVE-2026-45970, CVE-2026-45976, CVE-2026-46052, CVE-2026-46076, CVE-2026-46083, CVE-2026-46126, CVE-2026-46135, CVE-2026-46176, CVE-2026-52912, CVE-2026-52936, CVE-2026-52937, CVE-2026-52976, CVE-2026-53002, CVE-2026-53009, CVE-2026-53022, CVE-2026-53036, CVE-2026-53053, CVE-2026-53081, CVE-2026-53092, CVE-2026-53137, CVE-2026-53149, CVE-2026-53167, CVE-2026-53168, CVE-2026-53184, CVE-2026-53189, CVE-2026-53293, CVE-2026-53296, CVE-2026-53297, CVE-2026-53369, CVE-2026-53375, CVE-2026-53376, CVE-2026-53392, CVE-2026-63804, CVE-2026-63806, CVE-2026-63810, CVE-2026-63842, CVE-2026-63843, CVE-2026-63844, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63850, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856, CVE-2026-63860, CVE-2026-63865, CVE-2026-63868, CVE-2026-63892, CVE-2026-63916, CVE-2026-63923, CVE-2026-63962, CVE-2026-63985, CVE-2026-63995, CVE-2026-63997, CVE-2026-63998, CVE-2026-64000, CVE-2026-64025, CVE-2026-64105, CVE-2026-64106, CVE-2026-64123, CVE-2026-64133, CVE-2026-64170, CVE-2026-64182, CVE-2026-64185, CVE-2026-64244, CVE-2026-64256, CVE-2026-64276, CVE-2026-64286, CVE-2026-64306, CVE-2026-64313, CVE-2026-64317, CVE-2026-64326, CVE-2026-64351, CVE-2026-64363, CVE-2026-64373, CVE-2026-64376, CVE-2026-64475, CVE-2026-64476, CVE-2026-64477, CVE-2026-64480, CVE-2026-64486, CVE-2026-64487, CVE-2026-64496, CVE-2026-64534, CVE-2026-64535, CVE-2026-64544, CVE-2026-64562, CVE-2026-68184, CVE-2026-68279, CVE-2026-68470, CVE-2026-72031, CVE-2026-72083, CVE-2026-72105, CVE-2026-72111, CVE-2026-72165, CVE-2026-72218, CVE-2026-72225, CVE-2026-72237, CVE-2026-72242, CVE-2026-72255, CVE-2026-72262, CVE-2026-72280, CVE-2026-72284, CVE-2026-72286, CVE-2026-72301, CVE-2026-72304, CVE-2026-72322, CVE-2026-72325, CVE-2026-72371, CVE-2026-72374, CVE-2026-72488, CVE-2026-72494, CVE-2026-72496, CVE-2026-72497, CVE-2026-72499, CVE-2026-72500, CVE-2026-74257, CVE-2026-74271, CVE-2026-74295, CVE-2026-74296, CVE-2026-74297, CVE-2026-74305, CVE-2026-74310, CVE-2026-74313, CVE-2026-74330, CVE-2026-74331, CVE-2026-74332, CVE-2026-74365, CVE-2026-74379, CVE-2026-74401, CVE-2026-74405, CVE-2026-74416, CVE-2026-74417, CVE-2026-74426, CVE-2026-74497, CVE-2026-74500, CVE-2026-74505, CVE-2026-74516, CVE-2026-74519, CVE-2026-74547, CVE-2026-74553, CVE-2026-74566, CVE-2026-74567, CVE-2026-74578, CVE-2026-74584, CVE-2026-74666, CVE-2026-74671, CVE-2026-74689, CVE-2026-74733, CVE-2026-74743, CVE-2026-80534, CVE-2026-80590, CVE-2026-80593, CVE-2026-80602, CVE-2026-80622, CVE-2026-80646, CVE-2026-80649, CVE-2026-80659, CVE-2026-80669, CVE-2026-80677, CVE-2026-80681, CVE-2026-80731, CVE-2026-80884, CVE-2026-80952, CVE-2026-80964, CVE-2026-80967, CVE-2026-80969, CVE-2026-80971, CVE-2026-80972, CVE-2026-81001, CVE-2026-81008, CVE-2026-89439, CVE-2026-89443, CVE-2026-89444, CVE-2026-89477, CVE-2026-89480, CVE-2026-89481, CVE-2026-89482, CVE-2026-89530, CVE-2026-89532, CVE-2026-89537, CVE-2026-89549, CVE-2026-89566, CVE-2026-89567, CVE-2026-89636, CVE-2026-89656, CVE-2026-89694, CVE-2026-89726, CVE-2026-89751, CVE-2026-89854, CVE-2026-89861, CVE-2026-89878, CVE-2026-89894, CVE-2026-89897, CVE-2026-89899, CVE-2026-89912, CVE-2026-89913, CVE-2026-89930, CVE-2026-89952, CVE-2026-89969, CVE-2026-89973, CVE-2026-89975, CVE-2026-89984, CVE-2026-89988, CVE-2026-90011, CVE-2026-90037, CVE-2026-90057, CVE-2026-90060, CVE-2026-90063, CVE-2026-90128, CVE-2026-90157, CVE-2026-90177, CVE-2026-90182, CVE-2026-90196, CVE-2026-90227, CVE-2026-90250, CVE-2026-90284, CVE-2026-90290, CVE-2026-90300, CVE-2026-90326, CVE-2026-90391, CVE-2026-90392, CVE-2026-90398, CVE-2026-90416, CVE-2026-90417, CVE-2026-90435, CVE-2026-92509, CVE-2026-93037, CVE-2026-93048, CVE-2026-93055, CVE-2026-93100, CVE-2026-93104, CVE-2026-93108, CVE-2026-93109, CVE-2026-93110, CVE-2026-93115, CVE-2026-93125, CVE-2026-93131, CVE-2026-93138, CVE-2026-93144, CVE-2026-93163, CVE-2026-93175, CVE-2026-93185, CVE-2026-93186, CVE-2026-93210, CVE-2026-93239, CVE-2026-93256, CVE-2026-93288, CVE-2026-93785, CVE-2026-93795, CVE-2026-93824, CVE-2026-93828, CVE-2026-97440, CVE-2026-97441, CVE-2026-97444, CVE-2026-97446, CVE-2026-97453, CVE-2026-97454, CVE-2026-97495, CVE-2026-97497, CVE-2026-97505, CVE-2026-97521, CVE-2026-97540, CVE-2026-97597, CVE-2026-97601, CVE-2026-97608, CVE-2026-97616, CVE-2026-97904, CVE-2026-97905, CVE-2026-97930, CVE-2026-97957, CVE-2026-97958, CVE-2026-97965, CVE-2026-97987, CVE-2026-97989, CVE-2026-97994, CVE-2026-97995, CVE-2026-98033, CVE-2026-98034, CVE-2026-98038, CVE-2026-98043, CVE-2026-98046, CVE-2026-98047, CVE-2026-98054, CVE-2026-98056, CVE-2026-98063, CVE-2026-98064, CVE-2026-98075, CVE-2026-98088, CVE-2026-98096, CVE-2026-98116, CVE-2026-98154, CVE-2026-98157, CVE-2026-98164, CVE-2026-98171, CVE-2026-98197, CVE-2026-98198, CVE-2026-98211, CVE-2026-98252, CVE-2026-98253, CVE-2026-98262, CVE-2026-98266, CVE-2026-98314, CVE-2026-98320, CVE-2026-98323, CVE-2026-98342, CVE-2026-98347, CVE-2026-98357, CVE-2026-98359, CVE-2026-98360, CVE-2026-98376, CVE-2026-98378, CVE-2026-98443, CVE-2026-98554, CVE-2026-98634, CVE-2026-98636, CVE-2026-98655, CVE-2026-98716, CVE-2026-98726, CVE-2026-98742, CVE-2026-98775, CVE-2026-98790, CVE-2026-98863
CLSA: 2026:1793100968