CentOS Linux 8 [TuxCare] セキュリティ更新プログラム:bpftool/kernel/kernel-core/kernel-cross-headers/etcの複数の脆弱性(CENTOS-STREAM8:CLSA-2026:1791780738)
high Nessus プラグイン ID 364675
Language:
概要
CentOS Linux ホストに 1 つ以上のセキュリティ更新プログラムが欠落しています。説明
CentOS Linux 8ホストには、TuxCare CENTOS-STREAM8:CLSA-2026:1791780738アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。- Linux カーネルでは、以下の脆弱性が解決されています: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths Any codepath that zaps page table entries must invoke MMU notifiers to ensure that secondary MMUs (like KVM) don't keep accessing pages which aren't mapped anymore. Secondary MMUs don't hold their own references to pages that are mirrored over, so failing to notify them can lead to page use-after-free. I'm marking this as addressing an issue introduced in commit f3f0e1d2150b (khugepaged: add support of collapse for tmpfs/shmem pages), but most of the security impact of this only came in commit 27e1f8273113 (khugepaged: enable collapse pmd for pte-mapped THP), which actually omitted flushes for the removal of present PTEs, not just for the removal of empty page tables.
(CVE-2022-48991)
- Linux カーネルでは、以下の脆弱性が解決されています: virtio_net: fix xdp_rxq_info bug after suspend/resume The following sequence currently causes a driver bug warning when using virtio_net: # ip link set eth0 up # echo mem > /sys/power/state (or e.g. # rtcwake -s 10 -m mem) <resume> # ip link set eth0 down Missing register, driver bug WARNING: CPU: 0 PID: 375 at net/core/xdp.c:138 xdp_rxq_info_unreg+0x58/0x60 Call trace: xdp_rxq_info_unreg+0x58/0x60 virtnet_close+0x58/0xac
__dev_close_many+0xac/0x140 __dev_change_flags+0xd8/0x210 dev_change_flags+0x24/0x64 do_setlink+0x230/0xdd0 ... This happens because virtnet_freeze() frees the receive_queue completely (including struct xdp_rxq_info) but does not call xdp_rxq_info_unreg(). Similarly, virtnet_restore() sets up the receive_queue again but does not call xdp_rxq_info_reg(). Actually, parts of virtnet_freeze_down() and virtnet_restore_up() are almost identical to virtnet_close() and virtnet_open(): only the calls to xdp_rxq_info_(un)reg() are missing. This means that we can fix this easily and avoid such problems in the future by just calling virtnet_close()/open() from the freeze/restore handlers. Aside from adding the missing xdp_rxq_info calls the only difference is that the refill work is only cancelled if netif_running(). However, this should not make any functional difference since the refill work should only be active if the network interface is actually up. (CVE-2022-49687)
- Linux カーネルでは、以下の脆弱性が解決されています: bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data In tcp_bpf_send_verdict() redirection, the eval variable is assigned to
__SK_REDIRECT after the apply_bytes data is sent, if msg has more_data, sock_put() will be called multiple times. We should reset the eval variable to __SK_NONE every time more_data starts. This causes: IPv4:
Attempt to release TCP socket in state 1 00000000b4c925d7 ------------[ cut here ]------------ refcount_t:
addition on 0; use-after-free. WARNING: CPU: 5 PID: 4482 at lib/refcount.c:25 refcount_warn_saturate+0x7d/0x110 Modules linked in: CPU: 5 PID: 4482 Comm: sockhash_bypass Kdump: loaded Not tainted 6.0.0 #1 Hardware name: Red Hat KVM, BIOS 1.11.0-2.el7 04/01/2014 Call Trace: <TASK>
__tcp_transmit_skb+0xa1b/0xb90 ? __alloc_skb+0x8c/0x1a0 ? __kmalloc_node_track_caller+0x184/0x320 tcp_write_xmit+0x22a/0x1110 __tcp_push_pending_frames+0x32/0xf0 do_tcp_sendpages+0x62d/0x640 tcp_bpf_push+0xae/0x2c0 tcp_bpf_sendmsg_redir+0x260/0x410 ? preempt_count_add+0x70/0xa0 tcp_bpf_send_verdict+0x386/0x4b0 tcp_bpf_sendmsg+0x21b/0x3b0 sock_sendmsg+0x58/0x70
__sys_sendto+0xfa/0x170 ? xfd_validate_state+0x1d/0x80 ? switch_fpu_return+0x59/0xe0
__x64_sys_sendto+0x24/0x30 do_syscall_64+0x37/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd (CVE-2022-50536)
- Linux カーネルでは、以下の脆弱性が解決されています: crypto: scomp - fix req->dst buffer overflow The req->dst buffer size should be checked before copying from the scomp_scratch->dst to avoid req->dst buffer overflow problem. (CVE-2023-52612)
- Linux カーネルでは、以下の脆弱性が解決されています: net: atlantic: eliminate double free in error handling logic Driver has a logic leak in ring data allocation/free, where aq_ring_free could be called multiple times on same ring, if system is under stress and got memory allocation error. Ring pointer was used as an indicator of failure, but this is not correct since only ring data is allocated/deallocated. Ring itself is an array member. Changing ring allocation functions to return error code directly. This simplifies error handling and eliminates aq_ring_free on higher layer.
(CVE-2023-52664)
Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。
ソリューション
TuxCareアドバイザリCENTOS-STREAM8:CLSA-2026:1791780738のガイダンスに基づいて、影響を受けるパッケージを更新してください。参考資料
プラグインの詳細
深刻度: High
ID: 364675
ファイル名: tuxcare_centos_8_CLSA-2026-1791780738.nasl
バージョン: 1.1
タイプ: Local
エージェント: unix
ファミリー: CentOS Local Security Checks
公開日: 2026/10/12
更新日: 2026/10/12
サポートされているセンサー: Nessus Agent, Continuous Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus
リスク情報
VPR
リスクファクター: Critical
スコア: 9.3
パーセンタイル: 99.82
Vendor
Vendor Severity: Important
CVSS v2
リスクファクター: Medium
基本値: 6.8
現状値: 5.6
ベクトル: CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C
CVSS スコアのソース: CVE-2025-71238
CVSS v3
リスクファクター: High
基本値: 7.8
現状値: 7.2
ベクトル: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
現状ベクトル: CVSS:3.0/E:F/RL:O/RC:C
脆弱性情報
必要な KB アイテム: Host/local_checks_enabled, Host/CentOS/release, Host/CentOS/rpm-list, Host/OS/extended-third-party
エクスプロイトが利用可能: true
エクスプロイトの容易さ: Exploits are available
パッチ公開日: 2026/10/12
脆弱性公開日: 2021/7/21
CISA の既知の悪用された脆弱性の期限日: 2026/9/21
参照情報
CVE: CVE-2022-48991, CVE-2022-49687, CVE-2022-50536, CVE-2023-52612, CVE-2023-52664, CVE-2023-52760, CVE-2023-53109, CVE-2023-53432, CVE-2023-53596, CVE-2023-53751, CVE-2024-35791, CVE-2024-36013, CVE-2025-38022, CVE-2025-39964, CVE-2025-40149, CVE-2025-68724, CVE-2025-71238, CVE-2026-100075, CVE-2026-53266, CVE-2026-63971, CVE-2026-64471, CVE-2026-64483, CVE-2026-64563, CVE-2026-68108, CVE-2026-68236, CVE-2026-68289, CVE-2026-68365, CVE-2026-68398, CVE-2026-72129, CVE-2026-72261, CVE-2026-72389, CVE-2026-74444, CVE-2026-74505, CVE-2026-74510, CVE-2026-74556, CVE-2026-74569, CVE-2026-74580, CVE-2026-74582, CVE-2026-74583, CVE-2026-74621, CVE-2026-74637, CVE-2026-74689, CVE-2026-74725, CVE-2026-74730, CVE-2026-74746, CVE-2026-74752, CVE-2026-80536, CVE-2026-80576, CVE-2026-80590, CVE-2026-80844, CVE-2026-80971, CVE-2026-80994, CVE-2026-81000, CVE-2026-89477, CVE-2026-89481, CVE-2026-89487, CVE-2026-89542, CVE-2026-89548, CVE-2026-89555, CVE-2026-89559, CVE-2026-97408, CVE-2026-97417, CVE-2026-97427, CVE-2026-97448, CVE-2026-97455, CVE-2026-97509, CVE-2026-97539, CVE-2026-97608, CVE-2026-97612, CVE-2026-97940, CVE-2026-98077, CVE-2026-98096
CLSA: 2026:1791780738