CentOS Linux 8.4 [TuxCare] セキュリティ更新プログラム:bpftool/kernel/kernel-core/kernel-cross-headers/etcの複数の脆弱性(CENTOS8.4:CLSA-2026:1777614651)
high Nessus プラグイン ID 352091
Language:
概要
CentOS Linuxホストに1つ以上のセキュリティ更新プログラムがありません。説明
CentOS Linux 8.4 ホストには、TuxCare CENTOS8.4:CLSA-2026:1777614651アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。- 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 カーネルでは、以下の脆弱性が解決されています: RDMA/srpt: Fix a use-after-free Change the LIO port members inside struct srpt_port from regular members into pointers. Allocate the LIO port data structures from inside srpt_make_tport() and free these from inside srpt_make_tport(). Keep struct srpt_device as long as either an RDMA port or a LIO target port is associated with it. This patch decouples the lifetime of struct srpt_port (controlled by the RDMA core) and struct srpt_port_id (controlled by LIO). This patch fixes the following KASAN complaint: BUG: KASAN: use-after-free in srpt_enable_tpg+0x31/0x70 [ib_srpt] Read of size 8 at addr ffff888141cc34b8 by task check/5093 Call Trace:
<TASK> show_stack+0x4e/0x53 dump_stack_lvl+0x51/0x66 print_address_description.constprop.0.cold+0xea/0x41e print_report.cold+0x90/0x205 kasan_report+0xb9/0xf0 __asan_load8+0x69/0x90 srpt_enable_tpg+0x31/0x70 [ib_srpt] target_fabric_tpg_base_enable_store+0xe2/0x140 [target_core_mod] configfs_write_iter+0x18b/0x210 new_sync_write+0x1f2/0x2f0 vfs_write+0x3e3/0x540 ksys_write+0xbb/0x140 __x64_sys_write+0x42/0x50 do_syscall_64+0x34/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> (CVE-2022-50129)
- Linux カーネルでは、以下の脆弱性が解決されています: drm/amdkfd: Fix double release compute pasid If kfd_process_device_init_vm returns failure after vm is converted to compute vm and vm->pasid set to compute pasid, KFD will not take pdd->drm_file reference. As a result, drm close file handler maybe called to release the compute pasid before KFD process destroy worker to release the same pasid and set vm->pasid to zero, this generates below WARNING backtrace and NULL pointer access. Add helper amdgpu_amdkfd_gpuvm_set_vm_pasid and call it at the last step of kfd_process_device_init_vm, to ensure vm pasid is the original pasid if acquiring vm failed or is the compute pasid with pdd->drm_file reference taken to avoid double release same pasid. amdgpu: Failed to create process VM object ida_free called for id=32770 which is not allocated. WARNING: CPU: 57 PID: 72542 at ../lib/idr.c:522 ida_free+0x96/0x140 RIP:
0010:ida_free+0x96/0x140 Call Trace: amdgpu_pasid_free_delayed+0xe1/0x2a0 [amdgpu] amdgpu_driver_postclose_kms+0x2d8/0x340 [amdgpu] drm_file_free.part.13+0x216/0x270 [drm] drm_close_helper.isra.14+0x60/0x70 [drm] drm_release+0x6e/0xf0 [drm] __fput+0xcc/0x280 ____fput+0xe/0x20 task_work_run+0x96/0xc0 do_exit+0x3d0/0xc10 BUG: kernel NULL pointer dereference, address:
0000000000000000 RIP: 0010:ida_free+0x76/0x140 Call Trace: amdgpu_pasid_free_delayed+0xe1/0x2a0 [amdgpu] amdgpu_driver_postclose_kms+0x2d8/0x340 [amdgpu] drm_file_free.part.13+0x216/0x270 [drm] drm_close_helper.isra.14+0x60/0x70 [drm] drm_release+0x6e/0xf0 [drm] __fput+0xcc/0x280 ____fput+0xe/0x20 task_work_run+0x96/0xc0 do_exit+0x3d0/0xc10 (CVE-2022-50303)
- Linux カーネルでは、以下の脆弱性が解決されています: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value The return value of acpi_fetch_acpi_dev() could be NULL, which would cause a NULL pointer dereference to occur in acpi_device_hid(). [ rjw: Subject and changelog edits, added empty line after if () ] (CVE-2022-50327)
- Linux カーネルでは、以下の脆弱性が解決されています: NFSD: Protect against send buffer overflow in NFSv2 READ Since before the git era, NFSD has conserved the number of pages held by each nfsd thread by combining the RPC receive and send buffers into a single array of pages. This works because there are no cases where an operation needs a large RPC Call message and a large RPC Reply at the same time. Once an RPC Call has been received, svc_process() updates svc_rqst::rq_res to describe the part of rq_pages that can be used for constructing the Reply. This means that the send buffer (rq_res) shrinks when the received RPC record containing the RPC Call is large. A client can force this shrinkage on TCP by sending a correctly- formed RPC Call header contained in an RPC record that is excessively large. The full maximum payload size cannot be constructed in that case. (CVE-2022-50410)
Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。
ソリューション
TuxCareアドバイザリCENTOS8.4:CLSA-2026:1777614651のガイダンスに基づいて、影響を受けるパッケージを更新してください。参考資料
プラグインの詳細
深刻度: High
ID: 352091
ファイル名: tuxcare_centos_8.4_CLSA-2026-1777614651.nasl
バージョン: 1.2
タイプ: Local
エージェント: unix
ファミリー: CentOS Local Security Checks
公開日: 2026/9/30
更新日: 2026/10/1
サポートされているセンサー: Nessus Agent, Continuous Assessment, 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-23193
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/local_checks_enabled, Host/CentOS/release, Host/CentOS/rpm-list, Host/OS/extended-third-party
エクスプロイトが利用可能: 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-49267, CVE-2022-49687, CVE-2022-50129, CVE-2022-50303, CVE-2022-50327, CVE-2022-50410, CVE-2022-50543, CVE-2022-50546, CVE-2022-50673, CVE-2022-50698, CVE-2022-50699, CVE-2022-50865, CVE-2022-50881, CVE-2023-3772, CVE-2023-52796, CVE-2023-53147, CVE-2023-53254, CVE-2023-53286, CVE-2023-53296, CVE-2023-53380, CVE-2023-53539, CVE-2023-53559, CVE-2023-53577, CVE-2023-53596, CVE-2023-54014, CVE-2023-54098, CVE-2023-54207, CVE-2023-54317, CVE-2024-38556, CVE-2024-41069, CVE-2024-46713, CVE-2025-37882, CVE-2025-37885, CVE-2025-38103, CVE-2025-38375, CVE-2025-38563, CVE-2025-38565, CVE-2025-38728, CVE-2025-39744, CVE-2025-39751, CVE-2025-39898, CVE-2025-39973, CVE-2025-40135, CVE-2025-40149, CVE-2025-40158, CVE-2025-40271, CVE-2025-71085, CVE-2026-22980, CVE-2026-22998, CVE-2026-23060, CVE-2026-23089, CVE-2026-23193, CVE-2026-23204, CVE-2026-31431, CVE-2026-43077
CLSA: 2026:1777614651