AlmaLinux 9.2 [TuxCare] セキュリティ更新プログラム:bpftool/kernel/kernel-abi-stablelists/kernel-core/etcの複数の脆弱性(ALMALINUX9.2:CLSA-2026:1777616064)
high Nessus プラグイン ID 353159
Language:
概要
AlmaLinuxホストに1つ以上のセキュリティ更新プログラムがありません。説明
AlmaLinux 9.2 ホストには、TuxCare ALMALINUX9.2:CLSA-2026:1777616064アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。- Linux カーネルでは、以下の脆弱性が解決されています: tracing: Fix potential double free in create_var_ref() In create_var_ref(), init_var_ref() is called to initialize the fields of variable ref_field, which is allocated in the previous function call to create_hist_field(). Function init_var_ref() allocates the corresponding fields such as ref_field->system, but frees these fields when the function encounters an error. The caller later calls destroy_hist_field() to conduct error handling, which frees the fields and the variable itself. This results in double free of the fields which are already freed in the previous function. Fix this by storing NULL to the corresponding fields when they are freed in init_var_ref(). (CVE-2022-49410)
- Linux カーネルでは、以下の脆弱性が解決されています: net: mdio: fix undefined behavior in bit shift for __mdiobus_register Shifting signed 32-bit value by 31 bits is undefined, so changing significant bit to unsigned. The UBSAN warning calltrace like below: UBSAN: shift-out-of-bounds in drivers/net/phy/mdio_bus.c:586:27 left shift of 1 by 31 places cannot be represented in type 'int' Call Trace: <TASK> dump_stack_lvl+0x7d/0xa5 dump_stack+0x15/0x1b ubsan_epilogue+0xe/0x4e
__ubsan_handle_shift_out_of_bounds+0x1e7/0x20c __mdiobus_register+0x49d/0x4e0 fixed_mdio_bus_init+0xd8/0x12d do_one_initcall+0x76/0x430 kernel_init_freeable+0x3b3/0x422 kernel_init+0x24/0x1e0 ret_from_fork+0x1f/0x30 </TASK> (CVE-2022-49907)
- Linux カーネルでは、以下の脆弱性が解決されています: vt: Clear selection before changing the font When changing the console font with ioctl(KDFONTOP) the new font size can be bigger than the previous font. A previous selection may thus now be outside of the new screen size and thus trigger out-of-bounds accesses to graphics memory if the selection is removed in vc_do_resize(). Prevent such out-of-memory accesses by dropping the selection before the various con_font_set() console handlers are called.
(CVE-2022-49948)
- Linux カーネルでは、以下の脆弱性が解決されています: wifi: iwlwifi: mvm: fix double free on tx path. We see kernel crashes and lockups and KASAN errors related to ax210 firmware crashes. One of the KASAN dumps pointed at the tx path, and it appears there is indeed a way to double-free an skb. If iwl_mvm_tx_skb_sta returns non-zero, then the 'skb' sent into the method will be freed. But, in case where we build TSO skb buffer, the skb may also be freed in error case. So, return 0 in that particular error case and do cleanup manually. BUG: KASAN: use-after-free in __list_del_entry_valid+0x12/0x90 iwlwifi 0000:06:00.0: 0x00000000 | tsf hi Read of size 8 at addr ffff88813cfa4ba0 by task btserver/9650 CPU: 4 PID: 9650 Comm: btserver Tainted: G W 5.19.8+ #5 iwlwifi 0000:06:00.0: 0x00000000 | time gp1 Hardware name: Default string Default string/SKYBAY, BIOS 5.12 02/19/2019 Call Trace: <TASK> dump_stack_lvl+0x55/0x6d print_report.cold.12+0xf2/0x684 iwlwifi 0000:06:00.0: 0x1D0915A8 | time gp2 ?
__list_del_entry_valid+0x12/0x90 kasan_report+0x8b/0x180 iwlwifi 0000:06:00.0: 0x00000001 | uCode revision type ? __list_del_entry_valid+0x12/0x90 __list_del_entry_valid+0x12/0x90 iwlwifi 0000:06:00.0: 0x00000048 | uCode version major tcp_update_skb_after_send+0x5d/0x170 __tcp_transmit_skb+0xb61/0x15c0 iwlwifi 0000:06:00.0: 0xDAA05125 | uCode version minor ? __tcp_select_window+0x490/0x490 iwlwifi 0000:06:00.0:
0x00000420 | hw version ? trace_kmalloc_node+0x29/0xd0 ? __kmalloc_node_track_caller+0x12a/0x260 ? memset+0x1f/0x40 ? __build_skb_around+0x125/0x150 ? __alloc_skb+0x1d4/0x220 ? skb_zerocopy_clone+0x55/0x230 iwlwifi 0000:06:00.0: 0x00489002 | board version ? kmalloc_reserve+0x80/0x80 ? rcu_read_lock_bh_held+0x60/0xb0 tcp_write_xmit+0x3f1/0x24d0 iwlwifi 0000:06:00.0: 0x034E001C | hcmd ?
__check_object_size+0x180/0x350 iwlwifi 0000:06:00.0: 0x24020000 | isr0 tcp_sendmsg_locked+0x8a9/0x1520 iwlwifi 0000:06:00.0: 0x01400000 | isr1 ? tcp_sendpage+0x50/0x50 iwlwifi 0000:06:00.0: 0x48F0000A | isr2 ? lock_release+0xb9/0x400 ? tcp_sendmsg+0x14/0x40 iwlwifi 0000:06:00.0: 0x00C3080C | isr3 ? lock_downgrade+0x390/0x390 ? do_raw_spin_lock+0x114/0x1d0 iwlwifi 0000:06:00.0: 0x00200000 | isr4 ? rwlock_bug.part.2+0x50/0x50 iwlwifi 0000:06:00.0: 0x034A001C | last cmd Id ? rwlock_bug.part.2+0x50/0x50 ? lockdep_hardirqs_on_prepare+0xe/0x200 iwlwifi 0000:06:00.0: 0x0000C2F0 | wait_event ?
__local_bh_enable_ip+0x87/0xe0 ? inet_send_prepare+0x220/0x220 iwlwifi 0000:06:00.0: 0x000000C4 | l2p_control tcp_sendmsg+0x22/0x40 sock_sendmsg+0x5f/0x70 iwlwifi 0000:06:00.0: 0x00010034 | l2p_duration
__sys_sendto+0x19d/0x250 iwlwifi 0000:06:00.0: 0x00000007 | l2p_mhvalid ? __ia32_sys_getpeername+0x40/0x40 iwlwifi 0000:06:00.0: 0x00000000 | l2p_addr_match ? rcu_read_lock_held_common+0x12/0x50 ? rcu_read_lock_sched_held+0x5a/0xd0 ? rcu_read_lock_bh_held+0xb0/0xb0 ? rcu_read_lock_sched_held+0x5a/0xd0 ? rcu_read_lock_sched_held+0x5a/0xd0 ? lock_release+0xb9/0x400 ? lock_downgrade+0x390/0x390 ? ktime_get+0x64/0x130 ? ktime_get+0x8d/0x130 ? rcu_read_lock_held_common+0x12/0x50 ? rcu_read_lock_sched_held+0x5a/0xd0 ? rcu_read_lock_held_common+0x12/0x50 ? rcu_read_lock_sched_held+0x5a/0xd0 ? rcu_read_lock_bh_held+0xb0/0xb0 ? rcu_read_lock_bh_held+0xb0/0xb0
__x64_sys_sendto+0x6f/0x80 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP:
0033:0x7f1d126e4531 Code: 00 00 00 00 0f 1f 44 00 00 f3 0f 1e fa 48 8d 05 35 80 0c 00 41 89 ca 8b 00 85 c0 75 1c 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 67 c3 66 0f 1f 44 00 00 55 48 83 ec 20 48 89 RSP: 002b:00007ffe21a679d8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX:
000000000000ffdc RCX: 00007f1d126e4531 RDX: 0000000000010000 RSI: 000000000374acf0 RDI: 0000000000000014 RBP: 00007ffe21a67ac0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11:
0000000000000246 R ---truncated--- (CVE-2022-50248)
- Linux カーネルでは、以下の脆弱性が解決されています: mmc: rtsx_usb_sdmmc: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, the memory that allocated in mmc_alloc_host() will be leaked and it will lead a kernel crash because of deleting not added device in the remove path. So fix this by checking the return value and calling mmc_free_host() in the error path, besides, led_classdev_unregister() and pm_runtime_disable() also need be called.
(CVE-2022-50347)
Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。
ソリューション
TuxCareアドバイザリALMALINUX9.2:CLSA-2026:1777616064のガイダンスに基づいて、影響を受けるパッケージを更新してください。参考資料
プラグインの詳細
深刻度: High
ID: 353159
ファイル名: tuxcare_alma_linux_9.2_CLSA-2026-1777616064.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
リスクファクター: Medium
基本値: 6.8
現状値: 5.9
ベクトル: CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C
CVSS スコアのソース: CVE-2026-23216
CVSS v3
リスクファクター: High
基本値: 7.8
現状値: 7.5
ベクトル: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
現状ベクトル: CVSS:3.0/E:H/RL:O/RC:C
CVSS v4
リスクファクター: High
Base Score: 8.6
Threat Score: 8.6
Threat Vector: CVSS:4.0/E:A
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS スコアのソース: CVE-2026-31431
脆弱性情報
必要な KB アイテム: Host/OS/extended-third-party, Host/local_checks_enabled, Host/AlmaLinux/release, Host/AlmaLinux/rpm-list, Host/cpu
エクスプロイトが利用可能: true
エクスプロイトの容易さ: Exploits are available
パッチ公開日: 2026/5/1
脆弱性公開日: 2021/7/21
CISA の既知の悪用された脆弱性の期限日: 2026/5/15
エクスプロイト可能
Core Impact
Metasploit (Copy Fail AF_ALG + authencesn Page-Cache Write)
参照情報
CVE: CVE-2022-49410, CVE-2022-49444, CVE-2022-49770, CVE-2022-49870, CVE-2022-49892, CVE-2022-49900, CVE-2022-49907, CVE-2022-49917, CVE-2022-49948, CVE-2022-50142, CVE-2022-50220, CVE-2022-50248, CVE-2022-50286, CVE-2022-50315, CVE-2022-50347, CVE-2022-50351, CVE-2022-50366, CVE-2022-50384, CVE-2022-50411, CVE-2022-50419, CVE-2022-50423, CVE-2022-50460, CVE-2022-50490, CVE-2022-50497, CVE-2022-50551, CVE-2022-50699, CVE-2022-50712, CVE-2022-50720, CVE-2022-50733, CVE-2022-50736, CVE-2022-50740, CVE-2022-50761, CVE-2022-50771, CVE-2022-50777, CVE-2022-50809, CVE-2022-50822, CVE-2022-50829, CVE-2022-50845, CVE-2022-50862, CVE-2023-52693, CVE-2023-53150, CVE-2023-53167, CVE-2023-53176, CVE-2023-53181, CVE-2023-53188, CVE-2023-53189, CVE-2023-53193, CVE-2023-53199, CVE-2023-53200, CVE-2023-53201, CVE-2023-53208, CVE-2023-53211, CVE-2023-53234, CVE-2023-53246, CVE-2023-53251, CVE-2023-53271, CVE-2023-53279, CVE-2023-53295, CVE-2023-53309, CVE-2023-53315, CVE-2023-53320, CVE-2023-53344, CVE-2023-53368, CVE-2023-53369, CVE-2023-53375, CVE-2023-53391, CVE-2023-53400, CVE-2023-53411, CVE-2023-53419, CVE-2023-53426, CVE-2023-53431, CVE-2023-53445, CVE-2023-53450, CVE-2023-53456, CVE-2023-53474, CVE-2023-53479, CVE-2023-53480, CVE-2023-53481, CVE-2023-53482, CVE-2023-53488, CVE-2023-53498, CVE-2023-53509, CVE-2023-53520, CVE-2023-53631, CVE-2023-53648, CVE-2023-53684, CVE-2023-53709, CVE-2023-53719, CVE-2023-53731, CVE-2023-53747, CVE-2023-53806, CVE-2023-53814, CVE-2023-53867, CVE-2023-54006, CVE-2023-54011, CVE-2023-54014, CVE-2023-54021, CVE-2023-54024, CVE-2023-54029, CVE-2023-54031, CVE-2023-54040, CVE-2023-54048, CVE-2023-54053, CVE-2023-54055, CVE-2023-54064, CVE-2023-54090, CVE-2023-54091, CVE-2023-54096, CVE-2023-54100, CVE-2023-54120, CVE-2023-54123, CVE-2023-54131, CVE-2023-54137, CVE-2023-54146, CVE-2023-54156, CVE-2023-54166, CVE-2023-54169, CVE-2023-54170, CVE-2023-54176, CVE-2023-54179, CVE-2023-54197, CVE-2023-54200, CVE-2023-54207, CVE-2023-54214, CVE-2023-54229, CVE-2023-54259, CVE-2023-54263, CVE-2023-54275, CVE-2023-54317, CVE-2023-54325, CVE-2025-23155, CVE-2025-37767, CVE-2025-37940, CVE-2025-37985, CVE-2025-37990, CVE-2025-37992, CVE-2025-37997, CVE-2025-37998, CVE-2025-38009, CVE-2025-38023, CVE-2025-38035, CVE-2025-38037, CVE-2025-38048, CVE-2025-38061, CVE-2025-38063, CVE-2025-38066, CVE-2025-38071, CVE-2025-38072, CVE-2025-38095, CVE-2025-38100, CVE-2025-38112, CVE-2025-38115, CVE-2025-38122, CVE-2025-38126, CVE-2025-38161, CVE-2025-38166, CVE-2025-38174, CVE-2025-38181, CVE-2025-38184, CVE-2025-38190, CVE-2025-38197, CVE-2025-38214, CVE-2025-38222, CVE-2025-38231, CVE-2025-38251, CVE-2025-38285, CVE-2025-38293, CVE-2025-38305, CVE-2025-38312, CVE-2025-38319, CVE-2025-38324, CVE-2025-38334, CVE-2025-38337, CVE-2025-38344, CVE-2025-38345, CVE-2025-38386, CVE-2025-38387, CVE-2025-38391, CVE-2025-38412, CVE-2025-38430, CVE-2025-38439, CVE-2025-38457, CVE-2025-38460, CVE-2025-38466, CVE-2025-38468, CVE-2025-38470, CVE-2025-38474, CVE-2025-38502, CVE-2025-38514, CVE-2025-38528, CVE-2025-38540, CVE-2025-38581, CVE-2025-38601, CVE-2025-38602, CVE-2025-38608, CVE-2025-38617, CVE-2025-38622, CVE-2025-38644, CVE-2025-38695, CVE-2025-38700, CVE-2025-38701, CVE-2025-38706, CVE-2025-38721, CVE-2025-39673, CVE-2025-39676, CVE-2025-39677, CVE-2025-39713, CVE-2025-39736, CVE-2025-39737, CVE-2025-39742, CVE-2025-39756, CVE-2025-39764, CVE-2025-39773, CVE-2025-39782, CVE-2025-39795, CVE-2025-39798, CVE-2025-39808, CVE-2025-39812, CVE-2025-39813, CVE-2025-39844, CVE-2025-39845, CVE-2025-39847, CVE-2025-39889, CVE-2025-39953, CVE-2025-39967, CVE-2025-40096, CVE-2025-68301, CVE-2025-68725, CVE-2025-68800, CVE-2025-71068, CVE-2025-71082, CVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71112, CVE-2025-71116, CVE-2025-71133, CVE-2025-71154, CVE-2025-71238, CVE-2026-22977, CVE-2026-22980, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992, CVE-2026-23001, CVE-2026-23060, CVE-2026-23076, CVE-2026-23084, CVE-2026-23089, CVE-2026-23097, CVE-2026-23099, CVE-2026-23133, CVE-2026-23144, CVE-2026-23171, CVE-2026-23191, CVE-2026-23193, CVE-2026-23204, CVE-2026-23209, CVE-2026-23216, CVE-2026-31431, CVE-2026-43078
CLSA: 2026:1777616064