AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1795270985)

high Nessus Plugin ID 385035

Synopsis

The AlmaLinux host is missing one or more security updates.

Description

The AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1795270985 advisory.

- In the Linux kernel, the following vulnerability has been resolved: ipmi:si: Return state to normal if message allocation fails There were places where nothing would get started if a message allocation failed, so the driver needs to return to normal state. (CVE-2026-46108)

- In the Linux kernel, the following vulnerability has been resolved: driver core: Avoid warning when removing a device while its supplier is unbinding During driver removal, the following warning can appear:
WARNING: CPU: 1 PID: 139 at drivers/base/core.c:1497 __device_links_no_driver+0xcc/0xfc ... Call trace:
__device_links_no_driver+0xcc/0xfc (P) device_links_driver_cleanup+0xa8/0xf0 device_release_driver_internal+0x208/0x23c device_links_unbind_consumers+0xe0/0x108 device_release_driver_internal+0xec/0x23c device_links_unbind_consumers+0xe0/0x108 device_release_driver_internal+0xec/0x23c device_links_unbind_consumers+0xe0/0x108 device_release_driver_internal+0xec/0x23c driver_detach+0xa0/0x12c bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 pci_unregister_driver+0x20/0x9c lan966x_pci_driver_exit+0x18/0xa90 [lan966x_pci] This warning is triggered when a consumer is removed because the links status of its supplier is not DL_DEV_DRIVER_BOUND and the link flag DL_FLAG_SYNC_STATE_ONLY is not set. The topology in terms of consumers/suppliers used was the following (consumer ---> supplier): i2c -----------> OIC ----> PCI device | ^ | | +---> pinctrl ---+ When the PCI device is removed, the OIC (interrupt controller) has to be removed. In order to remove the OIC, pinctrl and i2c need to be removed and to remove pinctrl, i2c need to be removed. The removal order is: 1) i2c 2) pinctrl 3) OIC 4) PCI device In details, the removal sequence is the following (with 0000:01:00.0 the PCI device): driver_detach: call device_release_driver_internal(0000:01:00.0)... device_links_busy(0000:01:00.0): links->status = DL_DEV_UNBINDING device_links_unbind_consumers(0000:01:00.0): 0000:01:00.0--oic link->status = DL_STATE_SUPPLIER_UNBIND call device_release_driver_internal(oic)... device_links_busy(oic): links->status = DL_DEV_UNBINDING device_links_unbind_consumers(oic): oic--pinctrl link->status = DL_STATE_SUPPLIER_UNBIND call device_release_driver_internal(pinctrl)... device_links_busy(pinctrl):
links->status = DL_DEV_UNBINDING device_links_unbind_consumers(pinctrl): pinctrl--i2c link->status = DL_STATE_SUPPLIER_UNBIND call device_release_driver_internal(i2c)... device_links_busy(i2c): links->status = DL_DEV_UNBINDING __device_links_no_driver(i2c)... pinctrl--i2c link->status is DL_STATE_SUPPLIER_UNBIND oic--i2c link->status is DL_STATE_ACTIVE oic--i2c link->supplier->links.status is DL_DEV_UNBINDING The warning is triggered by the i2c removal because the OIC (supplier) links status is not DL_DEV_DRIVER_BOUND. Its links status is indeed set to DL_DEV_UNBINDING. It is perfectly legit to have the links status set to DL_DEV_UNBINDING in that case. Indeed we had started to unbind the OIC which triggered the consumer unbinding and didn't finish yet when the i2c is unbound. Avoid the warning when the supplier links status is set to DL_DEV_UNBINDING and thus support this removal sequence without any warnings.
(CVE-2026-97479)

- In the Linux kernel, the following vulnerability has been resolved: net: bridge: arp/nd proxy: fix reading neigh ha Currently neigh ha address is read directly, but that can result in torn/partial reads if the neigh is being updated. Use neigh_ha_snapshot to take a stable snapshot of the address. (CVE-2026-90106)

- In the Linux kernel, the following vulnerability has been resolved: selinux: allow multiple opens of /sys/fs/selinux/policy Currently there can only be a single open of /sys/fs/selinux/policy at any time.
This allows any process to block any other process from reading the kernel policy. The original motivation seems to have been a mix of preventing an inconsistent view of the policy size and preventing userspace from allocating kernel memory without bound, but this is arguably equally bad. Eliminate the policy_opened flag and shrink the critical section that the policy mutex is held. While we are making changes here, drop a couple of extraneous BUG_ONs. (CVE-2026-46302)

- In the Linux kernel, the following vulnerability has been resolved: dmaengine: Fix possible use after free In dma_release_channel(), check chan->device->privatecnt after call dma_chan_put(). However, dma_chan_put() call dma_device_put() which could release the last reference of the device if the DMA provider is already gone and hence free it. Fixes it by moving dma_chan_put() after the check.
(CVE-2026-72476)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Solution

Update the affected packages based on the guidance in TuxCare advisory ALMALINUX9.6:CLSA-2026:1795270985.

See Also

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

http://www.nessus.org/u?e084006f

Plugin Details

Severity: High

ID: 385035

File Name: tuxcare_alma_linux_9.6_CLSA-2026-1795270985.nasl

Version: 1.1

Type: Local

Published: 11/21/2026

Updated: 11/21/2026

Supported Sensors: Nessus Agent, Continuous Assessment, Nessus

Risk Information

VPR

Risk Factor: High

Score: 8

Percentile: 99.7

Vendor

Vendor Severity: Important

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5

Vector: CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C

CVSS Score Source: CVE-2025-38338

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.8

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

Required KB Items: Host/local_checks_enabled, Host/cpu, Host/AlmaLinux/release, Host/AlmaLinux/rpm-list, Host/OS/extended-third-party

Exploit Ease: No known exploits are available

Patch Publication Date: 11/21/2026

Vulnerability Publication Date: 7/21/2021

Reference Information

CVE: CVE-2022-50174, CVE-2022-50566, CVE-2022-50575, CVE-2022-50577, CVE-2022-50655, CVE-2022-50749, CVE-2022-50751, CVE-2022-50764, CVE-2022-50827, CVE-2022-50849, CVE-2022-50850, CVE-2022-50868, CVE-2023-53728, CVE-2023-53754, CVE-2023-53826, CVE-2023-53830, CVE-2023-53831, CVE-2023-54056, CVE-2023-54171, CVE-2024-46692, CVE-2024-53230, CVE-2024-53231, CVE-2025-21995, CVE-2025-37846, CVE-2025-37888, CVE-2025-37960, CVE-2025-38168, CVE-2025-38186, CVE-2025-38210, CVE-2025-38278, CVE-2025-38302, CVE-2025-38338, CVE-2025-38353, CVE-2025-38509, CVE-2025-40071, CVE-2025-40102, CVE-2025-40111, CVE-2025-40157, CVE-2025-40159, CVE-2025-40206, CVE-2025-40268, CVE-2025-40329, CVE-2025-40337, CVE-2025-40340, CVE-2025-40341, CVE-2025-68191, CVE-2025-68282, CVE-2025-68306, CVE-2025-68380, CVE-2025-68780, CVE-2025-68802, CVE-2025-71148, CVE-2026-23047, CVE-2026-23050, CVE-2026-23053, CVE-2026-23179, CVE-2026-31528, CVE-2026-31542, CVE-2026-31668, CVE-2026-31739, CVE-2026-43013, CVE-2026-43017, CVE-2026-43018, CVE-2026-43073, CVE-2026-43139, CVE-2026-43157, CVE-2026-43169, CVE-2026-43191, CVE-2026-43199, CVE-2026-43211, CVE-2026-43238, CVE-2026-43265, CVE-2026-43374, CVE-2026-43483, CVE-2026-45917, CVE-2026-46043, CVE-2026-46086, CVE-2026-46108, CVE-2026-46117, CVE-2026-46133, CVE-2026-46168, CVE-2026-46193, CVE-2026-46302, CVE-2026-52918, CVE-2026-52925, CVE-2026-52929, CVE-2026-52982, CVE-2026-53001, CVE-2026-53074, CVE-2026-53111, CVE-2026-53349, CVE-2026-63803, CVE-2026-63867, CVE-2026-63937, CVE-2026-63973, CVE-2026-64206, CVE-2026-64222, CVE-2026-64277, CVE-2026-64299, CVE-2026-64388, CVE-2026-64403, CVE-2026-64450, CVE-2026-64465, CVE-2026-64508, CVE-2026-64545, CVE-2026-68139, CVE-2026-68164, CVE-2026-68180, CVE-2026-68217, CVE-2026-68241, CVE-2026-68242, CVE-2026-68244, CVE-2026-68247, CVE-2026-68291, CVE-2026-68299, CVE-2026-68326, CVE-2026-68399, CVE-2026-68425, CVE-2026-72005, CVE-2026-72010, CVE-2026-72015, CVE-2026-72030, CVE-2026-72039, CVE-2026-72050, CVE-2026-72056, CVE-2026-72087, CVE-2026-72088, CVE-2026-72096, CVE-2026-72113, CVE-2026-72130, CVE-2026-72144, CVE-2026-72155, CVE-2026-72219, CVE-2026-72223, CVE-2026-72224, CVE-2026-72240, CVE-2026-72305, CVE-2026-72321, CVE-2026-72341, CVE-2026-72342, CVE-2026-72343, CVE-2026-72375, CVE-2026-72416, CVE-2026-72423, CVE-2026-72430, CVE-2026-72433, CVE-2026-72466, CVE-2026-72476, CVE-2026-74261, CVE-2026-74265, CVE-2026-74290, CVE-2026-74317, CVE-2026-74329, CVE-2026-74346, CVE-2026-74356, CVE-2026-74368, CVE-2026-74385, CVE-2026-74391, CVE-2026-74395, CVE-2026-74407, CVE-2026-74427, CVE-2026-74449, CVE-2026-74460, CVE-2026-74461, CVE-2026-74481, CVE-2026-74485, CVE-2026-74508, CVE-2026-74523, CVE-2026-74538, CVE-2026-74622, CVE-2026-74623, CVE-2026-74624, CVE-2026-74626, CVE-2026-74657, CVE-2026-74664, CVE-2026-74675, CVE-2026-74677, CVE-2026-74684, CVE-2026-74691, CVE-2026-74696, CVE-2026-74717, CVE-2026-80541, CVE-2026-80561, CVE-2026-80589, CVE-2026-80611, CVE-2026-80616, CVE-2026-80618, CVE-2026-80634, CVE-2026-80653, CVE-2026-80671, CVE-2026-80704, CVE-2026-80733, CVE-2026-80744, CVE-2026-80757, CVE-2026-80764, CVE-2026-80781, CVE-2026-80783, CVE-2026-80788, CVE-2026-80790, CVE-2026-80792, CVE-2026-80793, CVE-2026-80805, CVE-2026-80806, CVE-2026-80819, CVE-2026-80828, CVE-2026-80843, CVE-2026-80846, CVE-2026-80847, CVE-2026-80852, CVE-2026-80861, CVE-2026-80875, CVE-2026-80880, CVE-2026-80887, CVE-2026-80890, CVE-2026-80913, CVE-2026-80939, CVE-2026-80940, CVE-2026-80948, CVE-2026-80949, CVE-2026-80974, CVE-2026-89485, CVE-2026-89510, CVE-2026-89540, CVE-2026-89547, CVE-2026-89576, CVE-2026-89586, CVE-2026-89604, CVE-2026-89627, CVE-2026-89657, CVE-2026-89698, CVE-2026-89740, CVE-2026-89757, CVE-2026-89759, CVE-2026-89823, CVE-2026-89856, CVE-2026-89859, CVE-2026-90002, CVE-2026-90015, CVE-2026-90062, CVE-2026-90106, CVE-2026-90115, CVE-2026-90126, CVE-2026-90138, CVE-2026-90148, CVE-2026-90150, CVE-2026-90194, CVE-2026-90219, CVE-2026-90235, CVE-2026-90254, CVE-2026-90255, CVE-2026-90274, CVE-2026-90289, CVE-2026-90330, CVE-2026-90346, CVE-2026-90375, CVE-2026-90407, CVE-2026-90415, CVE-2026-92499, CVE-2026-92500, CVE-2026-92504, CVE-2026-92524, CVE-2026-92525, CVE-2026-93130, CVE-2026-93140, CVE-2026-93172, CVE-2026-93228, CVE-2026-93271, CVE-2026-93793, CVE-2026-93794, CVE-2026-93801, CVE-2026-93806, CVE-2026-97432, CVE-2026-97442, CVE-2026-97472, CVE-2026-97473, CVE-2026-97477, CVE-2026-97479, CVE-2026-97527, CVE-2026-97536, CVE-2026-97556, CVE-2026-97558, CVE-2026-97566, CVE-2026-97567, CVE-2026-97603, CVE-2026-97607, CVE-2026-97901, CVE-2026-97925, CVE-2026-97978, CVE-2026-97988, CVE-2026-98003, CVE-2026-98007, CVE-2026-98014, CVE-2026-98053, CVE-2026-98055, CVE-2026-98073, CVE-2026-98101, CVE-2026-98102, CVE-2026-98104, CVE-2026-98123, CVE-2026-98125, CVE-2026-98159, CVE-2026-98170, CVE-2026-98177, CVE-2026-98184, CVE-2026-98284, CVE-2026-98285, CVE-2026-98286, CVE-2026-98304, CVE-2026-98319, CVE-2026-98321, CVE-2026-98325, CVE-2026-98329, CVE-2026-98332, CVE-2026-98338, CVE-2026-98363, CVE-2026-98369, CVE-2026-98379, CVE-2026-98384, CVE-2026-98421, CVE-2026-98423, CVE-2026-98425, CVE-2026-98449, CVE-2026-98459, CVE-2026-98468, CVE-2026-98485, CVE-2026-98486, CVE-2026-98498, CVE-2026-98502, CVE-2026-98505, CVE-2026-98509, CVE-2026-98513, CVE-2026-98514, CVE-2026-98516, CVE-2026-98519, CVE-2026-98521, CVE-2026-98542, CVE-2026-98556, CVE-2026-98586, CVE-2026-98598, CVE-2026-98607, CVE-2026-98609, CVE-2026-98610, CVE-2026-98613, CVE-2026-98626, CVE-2026-98643, CVE-2026-98686, CVE-2026-98695, CVE-2026-98696, CVE-2026-98697, CVE-2026-98700, CVE-2026-98751, CVE-2026-98771, CVE-2026-98779, CVE-2026-98810, CVE-2026-98829, CVE-2026-98873, CVE-2026-98885, CVE-2026-98899, CVE-2026-98903, CVE-2026-98950, CVE-2026-98975, CVE-2026-98977, CVE-2026-98989, CVE-2026-98990, CVE-2026-98992, CVE-2026-99002, CVE-2026-99019, CVE-2026-99025, CVE-2026-99031, CVE-2026-99038, CVE-2026-99040, CVE-2026-99052, CVE-2026-99054, CVE-2026-99059, CVE-2026-99070, CVE-2026-99071, CVE-2026-99072, CVE-2026-99076, CVE-2026-99077, CVE-2026-99080, CVE-2026-99087, CVE-2026-99098, CVE-2026-99130, CVE-2026-99140, CVE-2026-99147, CVE-2026-99150, CVE-2026-99165, CVE-2026-99175, CVE-2026-99178, CVE-2026-99179, CVE-2026-99181, CVE-2026-99201, CVE-2026-99206, CVE-2026-99209, CVE-2026-99211, CVE-2026-99221, CVE-2026-99245, CVE-2026-99249, CVE-2026-99254, CVE-2026-99256, CVE-2026-99271, CVE-2026-99274, CVE-2026-99312

CLSA: 2026:1795270985