Detections
Analytics

AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1782151303)

high Nessus Plugin ID 361823

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:1782151303 advisory.

 - In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: fix memory leak when blob is malformed The bug fix was incomplete, it replaced crash with a memory leak. The old code had an assignment to ret embedded into the conditional, restore this. (CVE-2022-48641)

 - In the Linux kernel, the following vulnerability has been resolved: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR In some case, the GDDV returns a package with a buffer which has zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10). Then the data_vault_read() got NULL point dereference problem when accessing the 0x10 value in data_vault. [ 71.024560] BUG: kernel NULL pointer dereference, address: 0000000000000010 This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or NULL value in data_vault. (CVE-2022-48703)

 - In the Linux kernel, the following vulnerability has been resolved: ice: switch: fix potential memleak in ice_add_adv_recipe() When ice_add_special_words() fails, the 'rm' is not released, which will lead to a memory leak. Fix this up by going to 'err_unroll' label. Compile tested only. (CVE-2022-48709)

 - In the Linux kernel, the following vulnerability has been resolved: xen-netfront: Fix NULL sring after live migration A NAPI is setup for each network sring to poll data to kernel The sring with source host is destroyed before live migration and new sring with target host is setup after live migration. The NAPI for the old sring is not deleted until setup new sring with target host after migration. With busy_poll/busy_read enabled, the NAPI can be polled before got deleted when resume VM. BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 IP: xennet_poll+0xae/0xd20 PGD 0 P4D 0 Oops:
 0000 [#1] SMP PTI Call Trace: finish_task_switch+0x71/0x230 timerqueue_del+0x1d/0x40 hrtimer_try_to_cancel+0xb5/0x110 xennet_alloc_rx_buffers+0x2a0/0x2a0 napi_busy_loop+0xdb/0x270 sock_poll+0x87/0x90 do_sys_poll+0x26f/0x580 tracing_map_insert+0x1d4/0x2f0 event_hist_trigger+0x14a/0x260 finish_task_switch+0x71/0x230 __schedule+0x256/0x890 recalc_sigpending+0x1b/0x50 xen_sched_clock+0x15/0x20
 __rb_reserve_next+0x12d/0x140 ring_buffer_lock_reserve+0x123/0x3d0 event_triggers_call+0x87/0xb0 trace_event_buffer_commit+0x1c4/0x210 xen_clocksource_get_cycles+0x15/0x20 ktime_get_ts64+0x51/0xf0 SyS_ppoll+0x160/0x1a0 SyS_ppoll+0x160/0x1a0 do_syscall_64+0x73/0x130 entry_SYSCALL_64_after_hwframe+0x41/0xa6 ... RIP: xennet_poll+0xae/0xd20 RSP: ffffb4f041933900 CR2:
 0000000000000008 ---[ end trace f8601785b354351c ]--- xen frontend should remove the NAPIs for the old srings before live migration as the bond srings are destroyed There is a tiny window between the srings are set to NULL and the NAPIs are disabled, It is safe as the NAPI threads are still frozen at that time (CVE-2022-48969)

 - In the Linux kernel, the following vulnerability has been resolved: cifs: fix small mempool leak in SMB2_negotiate() In some cases of failure (dialect mismatches) in SMB2_negotiate(), after the request is sent, the checks would return -EIO when they should be rather setting rc = -EIO and jumping to neg_exit to free the response buffer from mempool. (CVE-2022-49938)

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:1782151303.

See Also

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

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

Plugin Details

Severity: High

ID: 361823

File Name: tuxcare_alma_linux_9.2_CLSA-2026-1782151303.nasl

Version: 1.2

Type: Local

Published: 10/1/2026

Updated: 10/2/2026

Supported Sensors: Nessus Agent, Continuous Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus

Risk Information

VPR

Risk Factor: High

Score: 7.9

Percentile: 99.35

Vendor

Vendor Severity: Important

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5.9

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

CVSS Score Source: CVE-2026-31485

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 7.5

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:H/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: 6/22/2026

Vulnerability Publication Date: 7/21/2021

Reference Information

CVE: CVE-2022-48641, CVE-2022-48703, CVE-2022-48709, CVE-2022-48969, CVE-2022-49780, CVE-2022-49787, CVE-2022-49795, CVE-2022-49938, CVE-2022-50110, CVE-2022-50191, CVE-2022-50278, CVE-2022-50330, CVE-2022-50358, CVE-2022-50395, CVE-2022-50466, CVE-2022-50482, CVE-2022-50643, CVE-2022-50677, CVE-2022-50756, CVE-2022-50886, CVE-2023-52467, CVE-2023-52508, CVE-2023-52662, CVE-2023-52706, CVE-2023-52736, CVE-2023-52753, CVE-2023-52806, CVE-2023-52815, CVE-2023-52819, CVE-2023-52984, CVE-2023-53005, CVE-2023-53009, CVE-2023-53044, CVE-2023-53062, CVE-2023-53079, CVE-2023-53091, CVE-2023-53132, CVE-2023-53318, CVE-2023-53340, CVE-2023-53423, CVE-2023-53444, CVE-2023-53501, CVE-2023-53654, CVE-2023-53674, CVE-2023-53708, CVE-2023-53722, CVE-2023-53861, CVE-2023-54052, CVE-2023-54201, CVE-2023-54300, CVE-2024-26679, CVE-2024-27025, CVE-2024-35822, CVE-2024-35930, CVE-2024-35978, CVE-2024-40967, CVE-2024-41005, CVE-2024-41077, CVE-2024-42247, CVE-2024-43871, CVE-2024-43884, CVE-2024-43890, CVE-2024-43894, CVE-2024-43912, CVE-2024-44947, CVE-2024-44954, CVE-2024-44965, CVE-2024-44990, CVE-2024-45025, CVE-2024-46737, CVE-2024-46754, CVE-2024-46807, CVE-2024-46817, CVE-2024-46826, CVE-2024-46855, CVE-2024-47682, CVE-2024-49855, CVE-2024-49899, CVE-2024-49909, CVE-2024-49913, CVE-2024-49923, CVE-2024-49938, CVE-2024-49944, CVE-2024-50008, CVE-2024-50024, CVE-2024-50142, CVE-2024-50237, CVE-2024-50259, CVE-2024-50294, CVE-2024-53144, CVE-2024-53180, CVE-2024-56532, CVE-2024-56590, CVE-2024-56594, CVE-2024-56637, CVE-2024-56681, CVE-2024-56715, CVE-2024-57807, CVE-2024-57973, CVE-2024-58009, CVE-2024-58239, CVE-2025-21636, CVE-2025-21637, CVE-2025-21639, CVE-2025-21724, CVE-2025-21728, CVE-2025-21862, CVE-2025-21909, CVE-2025-21963, CVE-2025-21964, CVE-2025-21971, CVE-2025-37768, CVE-2025-37770, CVE-2025-37841, CVE-2025-38099, CVE-2025-38105, CVE-2025-38248, CVE-2025-38393, CVE-2025-38515, CVE-2025-38671, CVE-2025-38705, CVE-2025-38725, CVE-2025-39902, CVE-2025-39925, CVE-2025-40164, CVE-2025-40259, CVE-2025-68183, CVE-2025-71084, CVE-2026-23071, CVE-2026-23303, CVE-2026-23448, CVE-2026-31416, CVE-2026-31418, CVE-2026-31419, CVE-2026-31485, CVE-2026-31488, CVE-2026-31492, CVE-2026-31496, CVE-2026-31497, CVE-2026-31512, CVE-2026-31586, CVE-2026-31663, CVE-2026-31669, CVE-2026-31694, CVE-2026-31786, CVE-2026-43037, CVE-2026-43116, CVE-2026-43125, CVE-2026-43449, CVE-2026-43451, CVE-2026-46243

CLSA: 2026:1782151303