AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1795237837)

high Nessus Plugin ID 384937

Synopsis

The AlmaLinux host is missing one or more security updates.

Description

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

- In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix use-after- free in nf_tables_addchain() nf_tables_addchain() publishes the chain to table->chains via list_add_tail_rcu() (in nft_chain_add()) before registering hooks. If nf_tables_register_hook() then fails, the error path calls nft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy() with no RCU grace period in between. This creates two use-after-free conditions: 1) Control-plane:
nf_tables_dump_chains() traverses table->chains under rcu_read_lock(). A concurrent dump can still be walking the chain when the error path frees it. 2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly installs the IPv4 hook before IPv6 registration fails. Packets entering nft_do_chain() via the transient IPv4 hook can still be dereferencing chain->blob_gen_X when the error path frees the chain. Add synchronize_rcu() between nft_chain_del() and the chain destroy so that all RCU readers -- both dump threads and in-flight packet evaluation -- have finished before the chain is freed. (CVE-2026-23231)

- In the Linux kernel, the following vulnerability has been resolved: fs: don't silently unmount busy mounts The propagate_mount_busy() helper exists to decide whether a synchronous can suceed. It does that by looking at the copies of the victims in the mounts its parent propagates to. One of those functions from propagation hell. It skips a copy that has child mounts except for the case of a single child mount covering the copy's root. That algorithm used to be exact. It isn't anymore. Originally only childless copies were unmounted during propagation. And 1064f874abc0 (mnt: Tuck mounts under others instead of creating shadow/side mounts.) ended up adding covered mounts to both sides in one go. Along came 99b19d16471e (mnt: In propgate_umount handle visiting mounts in any order) and that started to unmount more than before: [1]: A copy of a mount is unmounted when each of its children is either its overmount or a copy of the victim itself. In the former case the overmount gets reparented. In the latter case the copy of the victim will end up being unmounted. So propagate_umount() ended up being rewritten without adjusting propagate_mount_busy(). And currently propagate_mount_busy() doesn't look at copies of the victim that have two or more children nor a single child that is not the overmount. So any such copy in [1] is not checked for references. The result is that a synchronous unmount succeeds, pulling out a mount that is still in use. A container can run into this with its own mounts. The host shares a tree with the container and the host has a mount in that tree: mount -t tmpfs none /mnt mount --make-shared /mnt mount
-t tmpfs none /mnt/a The container's /mnt is a slave copy of the host mount. The container now takes a detached copy of the tree and mounts that copy beneath its propagated copy of /mnt/a and keeps the file descriptor to the tree open: unshare -m --propagation unchanged mount --make-rslave / fd = open_tree(AT_FDCWD, /mnt, OPEN_TREE_CLONE | AT_RECURSIVE) move_mount(fd, , AT_FDCWD, /mnt/a, MOVE_MOUNT_BENEATH) grep /mnt /proc/self/mountinfo 775 355 ... /mnt ... master:646 777 775 ... /mnt/a ...
master:646 776 777 ... /mnt/a ... master:647 778 777 ... /mnt/a/a ... master:647 The now attached tree (777) is now mounted beneath the container's copy of /mnt/a. That's also where the host mount sits (as seen from the host mount namespace). So the propagated copy (776) of the host's mount is on top of its root and the copy of that (778) is inside it. Now the host runs: umount /mnt/a and it succeeds. The moved tree tree and the copy inside of it are gone from the container. Now only the propagated copy is left and it got reparented to where it was before: grep /mnt /proc/self/mountinfo 775 355 ... /mnt ... master:646 776 775 ... /mnt/a ... But the file descriptor still refers to the moved tree. So a synchronous umount detached a mount that is still in use. Teach propagate_mount_busy() the same checks that propagate_umount() does. It now checks for a single victim mount without children for which it can assume that MNT_LOCKED is cleared on every copy like propagate_umount() does. The copies form chains. IOW, when a copy itself receives propagation from the victim's parent then the mount at the same mountpoint inside that copy is a copy as well. Whether a mount receives propagation from the victim's can simply be checked by walking its masters. Walk each chain once from its top so we are sure that nested copies stay linear.
Check every reference once of every copy that gets unmounted. (CVE-2026-98996)

- In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Do cache maintenance on the source VM during intra-host migration Manually perform cache maintenance on the source VM during intra- host migration to ensure no stale data is left in CPU caches after the VM is destroyed. Because the source VM is converted to a non-SEV VM, KVM's memory reclaim flows won't trigger cache maintenance, e.g. when all guest memory is reclaimed in response to detaching from the mmu_notifier. Note, relying on the destination VM to do cache maintenance isn't an option as KVM doesn't require identical guest memory configurations, i.e. the source VM may have access to memory that the destination VM does not. Enforcing equivalent memory configurations is infeasible, as it would require a *deep* comparison of memslots, e.g.
to verify that not only are the memslot identical, but what the memslots point at is also identical.
(CVE-2026-98471)

- In the Linux kernel, the following vulnerability has been resolved: l2tp: fix tunnel and session refcount leak on seq_file release In pppol2tp_proc_open() and l2tp_dfs_seq_open(), iteration state (pd->tunnel and pd->session) is kept in seq_file private data to allow iteration across multiple read() system calls.
However, if userspace closes /proc/net/pppol2tp or /sys/kernel/debug/l2tp/tunnels before reading to end- of-file (EOF), any tunnel or session reference stored in pd->tunnel / pd->session is left un-dropped when seq_file private data is freed. Fix this by dropping any remaining pd->tunnel and pd->session references in pppol2tp_proc_release() and l2tp_dfs_seq_release() when closing the file. (CVE-2026-74735)

- In the Linux kernel, the following vulnerability has been resolved: RDMA/cxgb4: Free debugfs on registration failure c4iw_alloc() creates the per-device debugfs tree (dev->debugfs_root via setup_debugfs()), but it is removed only in c4iw_remove(), not in c4iw_dealloc(). When RDMA device registration fails, the registration worker's err_dealloc_ctx path calls c4iw_dealloc() directly, bypassing c4iw_remove(), so the debugfs dentries leak and outlive the freed c4iw_dev. Move debugfs_remove_recursive() into c4iw_dealloc() so every path that frees ctx->dev also removes its debugfs tree. (CVE-2026-90219)

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.2:CLSA-2026:1795237837.

See Also

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

http://www.nessus.org/u?0d4d4f14

Plugin Details

Severity: High

ID: 384937

File Name: tuxcare_alma_linux_9.2_CLSA-2026-1795237837.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: Critical

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5.3

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

CVSS Score Source: CVE-2026-23231

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 7

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:P/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 Available: true

Exploit Ease: Exploits are available

Patch Publication Date: 11/21/2026

Vulnerability Publication Date: 7/21/2021

Reference Information

CVE: 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-50859, CVE-2022-50868, CVE-2023-52559, CVE-2023-52906, CVE-2023-53049, CVE-2023-53221, CVE-2023-53715, CVE-2023-53728, CVE-2023-53802, CVE-2023-53808, CVE-2023-53815, CVE-2023-53817, CVE-2023-53830, CVE-2023-54099, CVE-2023-54171, CVE-2023-54209, CVE-2023-54247, CVE-2024-26583, CVE-2024-26585, CVE-2024-26686, CVE-2024-26810, CVE-2024-26812, CVE-2024-27017, CVE-2024-35840, CVE-2024-35857, CVE-2024-38632, CVE-2024-40972, CVE-2024-43817, CVE-2024-43853, CVE-2024-46750, CVE-2024-46775, CVE-2024-46834, CVE-2024-49914, CVE-2024-49920, CVE-2024-49974, CVE-2024-50117, CVE-2024-50192, CVE-2024-50195, CVE-2024-53060, CVE-2024-53090, CVE-2024-53093, CVE-2024-53195, CVE-2024-54683, CVE-2024-57804, CVE-2024-58098, CVE-2024-58100, CVE-2024-58237, CVE-2024-58241, CVE-2025-21696, CVE-2025-38491, CVE-2025-38552, CVE-2025-39775, CVE-2025-40099, CVE-2025-40268, CVE-2025-68191, CVE-2025-68218, CVE-2025-68227, CVE-2025-68259, CVE-2025-68380, CVE-2025-71126, CVE-2026-23231, CVE-2026-23239, CVE-2026-23240, CVE-2026-43023, CVE-2026-43112, CVE-2026-43211, CVE-2026-46037, CVE-2026-46181, CVE-2026-52975, CVE-2026-53086, CVE-2026-53267, CVE-2026-53317, CVE-2026-53385, CVE-2026-53393, CVE-2026-63856, CVE-2026-63914, CVE-2026-64190, CVE-2026-64481, CVE-2026-64507, CVE-2026-64514, CVE-2026-64529, CVE-2026-68312, CVE-2026-68425, CVE-2026-68447, CVE-2026-72140, CVE-2026-72245, CVE-2026-72404, CVE-2026-72440, CVE-2026-74290, CVE-2026-74302, CVE-2026-74374, CVE-2026-74441, CVE-2026-74461, CVE-2026-74654, CVE-2026-74675, CVE-2026-74715, CVE-2026-74735, CVE-2026-80527, CVE-2026-80737, CVE-2026-80764, CVE-2026-80783, CVE-2026-80790, CVE-2026-80819, CVE-2026-80828, CVE-2026-80843, CVE-2026-80846, CVE-2026-80852, CVE-2026-81016, CVE-2026-89510, CVE-2026-89528, CVE-2026-89548, CVE-2026-89549, CVE-2026-89595, CVE-2026-89647, CVE-2026-89649, CVE-2026-89675, CVE-2026-89709, CVE-2026-89718, CVE-2026-89719, CVE-2026-89799, CVE-2026-89811, CVE-2026-89859, CVE-2026-90219, CVE-2026-90346, CVE-2026-90359, CVE-2026-93061, CVE-2026-97425, CVE-2026-97481, CVE-2026-97563, CVE-2026-98046, CVE-2026-98055, CVE-2026-98058, CVE-2026-98116, CVE-2026-98127, CVE-2026-98182, CVE-2026-98332, CVE-2026-98363, CVE-2026-98468, CVE-2026-98471, CVE-2026-98486, CVE-2026-98498, CVE-2026-98502, CVE-2026-98505, CVE-2026-98516, CVE-2026-98519, CVE-2026-98589, CVE-2026-98607, CVE-2026-98609, CVE-2026-98695, CVE-2026-98771, CVE-2026-98779, CVE-2026-98799, CVE-2026-98803, CVE-2026-98815, CVE-2026-98822, CVE-2026-98873, CVE-2026-98879, CVE-2026-98885, CVE-2026-98913, CVE-2026-98924, CVE-2026-98929, CVE-2026-98950, CVE-2026-98996, CVE-2026-99033, CVE-2026-99040, CVE-2026-99059, CVE-2026-99070, CVE-2026-99071, CVE-2026-99076, CVE-2026-99077, CVE-2026-99140, CVE-2026-99169, CVE-2026-99201, CVE-2026-99211, CVE-2026-99221, CVE-2026-99223, CVE-2026-99245, CVE-2026-99249, CVE-2026-99271, CVE-2026-99274, CVE-2026-99275, CVE-2026-99292, CVE-2026-99302, CVE-2026-99310, CVE-2026-99312

CLSA: 2026:1795237837