Detections
Analytics

Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1780052998)

high Nessus Plugin ID 351610

Synopsis

The Rocky Linux host is missing one or more security updates.

Description

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

 - In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix potential CAN frame reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID:
 19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline] skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline] isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline] can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665 can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465
 __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes the issue reported by syzkaller but does not affect real world operation. (CVE-2022-48830)

 - In the Linux kernel, the following vulnerability has been resolved: ceph: fix deadlock or deadcode of misusing dget() The lock order is incorrect between denty and its parent, we should always make sure that the parent get the lock first. But since this deadcode is never used and the parent dir will always be set from the callers, let's just remove it. (CVE-2023-52583)

 - In the Linux kernel, the following vulnerability has been resolved: trace_events_hist: add check for return value of 'create_hist_field' Function 'create_hist_field' is called recursively at trace_events_hist.c:1954 and can return NULL-value that's why we have to check it to avoid null pointer dereference. Found by Linux Verification Center (linuxtesting.org) with SVACE. (CVE-2023-53005)

 - In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: fix percpu counter block leak on error path when creating new netns Here is the stack where we allocate percpu counter block: +-< __alloc_percpu +-< xt_percpu_counter_alloc +-< find_check_entry # {arp,ip,ip6}_tables.c +-< translate_table And it can be leaked on this code path: +-> ip6t_register_table +-> translate_table # allocates percpu counter block +-> xt_register_table # fails there is no freeing of the counter block on xt_register_table fail. Note: xt_percpu_counter_free should be called to free it like we do in do_replace through cleanup_entry helper (or in __ip6t_unregister_table). Probability of hitting this error path is low AFAICS (xt_register_table can only return ENOMEM here, as it is not replacing anything, as we are creating new netns, and it is hard to imagine that all previous allocations succeeded and after that one in xt_register_table failed). But it's worth fixing even the rare leak. (CVE-2023-53200)

 - In the Linux kernel, the following vulnerability has been resolved: spi: imx: Don't skip cleanup in remove's error path Returning early in a platform driver's remove callback is wrong. In this case the dma resources are not released in the error path. this is never retried later and so this is a permanent leak.
 To fix this, only skip hardware disabling if waking the device fails. (CVE-2023-53225)

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

See Also

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

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

Plugin Details

Severity: High

ID: 351610

File Name: tuxcare_rocky_linux_9.6_CLSA-2026-1780052998.nasl

Version: 1.1

Type: Local

Published: 9/30/2026

Updated: 9/30/2026

Supported Sensors: Nessus Agent, Continuous Assessment, Nessus

Risk Information

VPR

Risk Factor: High

Score: 7.9

Percentile: 99.35

Vendor

Vendor Severity: Important

CVSS v2

Risk Factor: High

Base Score: 8.3

Temporal Score: 7.2

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

CVSS Score Source: CVE-2026-23395

CVSS v3

Risk Factor: High

Base Score: 8.8

Temporal Score: 8.4

Vector: CVSS:3.0/AV:A/AC:L/PR:N/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/RockyLinux/release, Host/RockyLinux/rpm-list, Host/OS/extended-third-party

Exploit Available: true

Exploit Ease: Exploits are available

Patch Publication Date: 5/29/2026

Vulnerability Publication Date: 7/21/2021

Reference Information

CVE: CVE-2022-48830, CVE-2023-52583, CVE-2023-53005, CVE-2023-53200, CVE-2023-53225, CVE-2023-53234, CVE-2023-53279, CVE-2023-53295, CVE-2023-53344, CVE-2023-53368, CVE-2023-53375, CVE-2023-53411, CVE-2023-53423, CVE-2023-53450, CVE-2023-53480, CVE-2023-53481, CVE-2023-53535, CVE-2023-53667, CVE-2024-38601, CVE-2024-43098, CVE-2024-45003, CVE-2024-46715, CVE-2024-46791, CVE-2024-56569, CVE-2024-56584, CVE-2024-56587, CVE-2024-56709, CVE-2024-56720, CVE-2024-56756, CVE-2024-57977, CVE-2025-21638, CVE-2025-21639, CVE-2025-21640, CVE-2025-21653, CVE-2025-21707, CVE-2025-21732, CVE-2025-21992, CVE-2025-22062, CVE-2025-23141, CVE-2025-23155, CVE-2025-23161, CVE-2025-37788, CVE-2025-37807, CVE-2025-37836, CVE-2025-37878, CVE-2025-37884, CVE-2025-37954, CVE-2025-37961, CVE-2025-37989, CVE-2025-38039, CVE-2025-38057, CVE-2025-38097, CVE-2025-38147, CVE-2025-38192, CVE-2025-38321, CVE-2025-38335, CVE-2025-38393, CVE-2025-38412, CVE-2025-38438, CVE-2025-38466, CVE-2025-38544, CVE-2025-38565, CVE-2025-38709, CVE-2025-39673, CVE-2025-39681, CVE-2025-39748, CVE-2025-39754, CVE-2025-39763, CVE-2025-39764, CVE-2025-39850, CVE-2025-39931, CVE-2025-40040, CVE-2025-40149, CVE-2025-71094, CVE-2025-71098, CVE-2025-71111, CVE-2025-71131, CVE-2025-71151, CVE-2025-71161, CVE-2026-22997, CVE-2026-23011, CVE-2026-23071, CVE-2026-23101, CVE-2026-23108, CVE-2026-23119, CVE-2026-23120, CVE-2026-23136, CVE-2026-23164, CVE-2026-23171, CVE-2026-23270, CVE-2026-23318, CVE-2026-23374, CVE-2026-23395, CVE-2026-31402, CVE-2026-31485, CVE-2026-31492, CVE-2026-31495, CVE-2026-31555, CVE-2026-31575, CVE-2026-31759, CVE-2026-31778, CVE-2026-46243

CLSA: 2026:1780052998