Rocky Linux 9.6 [TuxCare] セキュリティ更新プログラム:kernel/kernel-abi-stablelists/kernel-core/etcの複数の脆弱性(ALMALINUX9.6:CLSA-2026:1786352940)

high Nessus プラグイン ID 360569

概要

Rocky Linuxホストに1つ以上のセキュリティ更新プログラムがありません。

説明

Rocky Linuxの 9.6 ホストには、TuxCare ALMALINUX9.6:CLSA-2026:1786352940アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。

- Linux カーネルでは、以下の脆弱性が解決されています: serial: imx: fix tx statemachine deadlock When using the serial port as RS485 port, the tx statemachine is used to control the RTS pin to drive the RS485 transceiver TX_EN pin. When the TTY port is closed in the middle of a transmission (for instance during userland application crash), imx_uart_shutdown disables the interface and disables the Transmission Complete interrupt. afer that, imx_uart_stop_tx bails on an incomplete transmission, to be retriggered by the TC interrupt. This interrupt is disabled and therefore the tx statemachine never transitions out of SEND. The statemachine is in deadlock now, and the TX_EN remains low, making the interface useless. imx_uart_stop_tx now checks for incomplete transmission AND whether TC interrupts are enabled before bailing to be retriggered. This makes sure the state machine handling is reached, and is properly set to WAIT_AFTER_SEND. (CVE-2023-52456)

- Linux カーネルでは、以下の脆弱性が解決されています: kdb: Fix buffer overflow during tab-complete Currently, when the user attempts symbol completion with the Tab key, kdb will use strncpy() to insert the completed symbol into the command buffer. Unfortunately it passes the size of the source buffer rather than the destination to strncpy() with predictably horrible results. Most obviously if the command buffer is already full but cp, the cursor position, is in the middle of the buffer, then we will write past the end of the supplied buffer. Fix this by replacing the dubious strncpy() calls with memmove()/memcpy() calls plus explicit boundary checks to make sure we have enough space before we start moving characters around. (CVE-2024-39480)

- Linux カーネルでは、以下の脆弱性が解決されています: Fix userfaultfd_api to return EINVAL as expected Currently if we request a feature that is not set in the Kernel config we fail silently and return all the available features. However, the man page indicates we should return an EINVAL. We need to fix this issue since we can end up with a Kernel warning should a program request the feature UFFD_FEATURE_WP_UNPOPULATED on a kernel with the config not set with this feature. [ 200.812896] WARNING:
CPU: 91 PID: 13634 at mm/memory.c:1660 zap_pte_range+0x43d/0x660 [ 200.820738] Modules linked in: [200.869387] CPU: 91 PID: 13634 Comm: userfaultfd Kdump: loaded Not tainted 6.9.0-rc5+ #8 [ 200.877477] Hardware name: Dell Inc. PowerEdge R6525/0N7YGH, BIOS 2.7.3 03/30/2022 [ 200.885052] RIP:
0010:zap_pte_range+0x43d/0x660 (CVE-2024-41027)

- Linux カーネルでは、以下の脆弱性が解決されています: mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file In case of invalid INI file mlxsw_linecard_types_init() deallocates memory but doesn't reset pointer to NULL and returns 0. In case of any error occurred after mlxsw_linecard_types_init() call, mlxsw_linecards_init() calls mlxsw_linecard_types_fini() which performs memory deallocation again. Add pointer reset to NULL. Found by Linux Verification Center (linuxtesting.org) with SVACE. (CVE-2024-42138)

- Linux カーネルでは、以下の脆弱性が解決されています: x86/tdx: Fix data leak in mmio_read() The mmio_read() function makes a TDVMCALL to retrieve MMIO data for an address from the VMM. Sean noticed that mmio_read() unintentionally exposes the value of an initialized variable (val) on the stack to the VMM. This variable is only needed as an output value. It did not need to be passed to the VMM in the first place. Do not send the original value of *val to the VMM. [ dhansen: clarify what 'val' is used for. ] (CVE-2024-46794)

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

ソリューション

TuxCareアドバイザリALMALINUX9.6:CLSA-2026:1786352940のガイダンスに基づいて、影響を受けるパッケージを更新してください。

参考資料

https://cve.tuxcare.com/els/releases/CLSA-2026:1786352940

http://www.nessus.org/u?3535afaf

プラグインの詳細

深刻度: High

ID: 360569

ファイル名: tuxcare_rocky_linux_9.6_CLSA-2026-1786352940.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-53112

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/RockyLinux/release, Host/RockyLinux/rpm-list, Host/cpu

エクスプロイトが利用可能: true

エクスプロイトの容易さ: Exploits are available

パッチ公開日: 2026/8/10

脆弱性公開日: 2021/7/21

参照情報

CVE: CVE-2022-49388, CVE-2023-52456, CVE-2023-53271, CVE-2024-39480, CVE-2024-41027, CVE-2024-42138, CVE-2024-46794, CVE-2024-53202, CVE-2024-56372, CVE-2024-56625, CVE-2024-56632, CVE-2024-56745, CVE-2024-57917, CVE-2024-58093, CVE-2025-21645, CVE-2025-21716, CVE-2025-21770, CVE-2025-21783, CVE-2025-21810, CVE-2025-21874, CVE-2025-21890, CVE-2025-21906, CVE-2025-21916, CVE-2025-21970, CVE-2025-21973, CVE-2025-21978, CVE-2025-22016, CVE-2025-22050, CVE-2025-22117, CVE-2025-22128, CVE-2025-23134, CVE-2025-23151, CVE-2025-37793, CVE-2025-37912, CVE-2025-37957, CVE-2025-38020, CVE-2025-38113, CVE-2025-38239, CVE-2025-38543, CVE-2025-38557, CVE-2025-38632, CVE-2025-38676, CVE-2025-39701, CVE-2025-39811, CVE-2025-39860, CVE-2025-39861, CVE-2025-39877, CVE-2025-39922, CVE-2025-39944, CVE-2025-39957, CVE-2025-39963, CVE-2025-40030, CVE-2025-40035, CVE-2025-40070, CVE-2025-40085, CVE-2025-40115, CVE-2025-40171, CVE-2025-40211, CVE-2025-40264, CVE-2025-40275, CVE-2025-40325, CVE-2025-68229, CVE-2025-68288, CVE-2025-68372, CVE-2025-68782, CVE-2025-71064, CVE-2025-71229, CVE-2025-71231, CVE-2025-71234, CVE-2025-71305, CVE-2026-23129, CVE-2026-23135, CVE-2026-23148, CVE-2026-23160, CVE-2026-23173, CVE-2026-23187, CVE-2026-23242, CVE-2026-23260, CVE-2026-23317, CVE-2026-23359, CVE-2026-23363, CVE-2026-23412, CVE-2026-23413, CVE-2026-23418, CVE-2026-31430, CVE-2026-31469, CVE-2026-31520, CVE-2026-31522, CVE-2026-31604, CVE-2026-31614, CVE-2026-31649, CVE-2026-31655, CVE-2026-31697, CVE-2026-31758, CVE-2026-43047, CVE-2026-43056, CVE-2026-43111, CVE-2026-43114, CVE-2026-43120, CVE-2026-43133, CVE-2026-43180, CVE-2026-43233, CVE-2026-43260, CVE-2026-43304, CVE-2026-43329, CVE-2026-43334, CVE-2026-43339, CVE-2026-43346, CVE-2026-43370, CVE-2026-43432, CVE-2026-43459, CVE-2026-43466, CVE-2026-43473, CVE-2026-43488, CVE-2026-45851, CVE-2026-45872, CVE-2026-45922, CVE-2026-45982, CVE-2026-45997, CVE-2026-46006, CVE-2026-46070, CVE-2026-46079, CVE-2026-46089, CVE-2026-46092, CVE-2026-46094, CVE-2026-46107, CVE-2026-46136, CVE-2026-46140, CVE-2026-46146, CVE-2026-46320, CVE-2026-52964, CVE-2026-53088, CVE-2026-53093, CVE-2026-53102, CVE-2026-53105, CVE-2026-53112, CVE-2026-53113, CVE-2026-53146, CVE-2026-53147, CVE-2026-53190, CVE-2026-53229, CVE-2026-53241, CVE-2026-53318, CVE-2026-53337, CVE-2026-53347, CVE-2026-64561

CLSA: 2026:1786352940