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

  - In the Linux kernel, the following vulnerability has been resolved: of: fdt: fix off-by-one error in     unflatten_dt_nodes() Commit 78c44d910d3e (drivers/of: Fix depth when unflattening devicetree) forgot to     fix up the depth check in the loop body in unflatten_dt_nodes() which makes it possible to overflow the     nps[] buffer... Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.
    (CVE-2022-48672)

  - In the Linux kernel, the following vulnerability has been resolved: net: sched: sch_multiq: fix possible     OOB write in multiq_tune() q->bands will be assigned to qopt->bands to execute subsequent code logic after     kmalloc. So the old q->bands should not be used in kmalloc. Otherwise, an out-of-bounds write will occur.
    (CVE-2024-36978)

  - In the Linux kernel, the following vulnerability has been resolved: net: do not leave a dangling sk     pointer, when socket creation fails It is possible to trigger a use-after-free by: * attaching an fentry     probe to __sock_release() and the probe calling the bpf_get_socket_cookie() helper * running traceroute -I     1.1.1.1 on a freshly booted VM A KASAN enabled kernel will log something like below (decoded and     stripped): ================================================================== BUG: KASAN: slab-use-after-     free in __sock_gen_cookie (./arch/x86/include/asm/atomic64_64.h:15 ./include/linux/atomic/atomic-arch-     fallback.h:2583 ./include/linux/atomic/atomic-instrumented.h:1611 net/core/sock_diag.c:29) Read of size 8     at addr ffff888007110dd8 by task traceroute/299 CPU: 2 PID: 299 Comm: traceroute Tainted: G E 6.10.0-rc2+     #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Call     Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:117 (discriminator 1)) print_report (mm/kasan/report.c:378     mm/kasan/report.c:488) ? __sock_gen_cookie (./arch/x86/include/asm/atomic64_64.h:15     ./include/linux/atomic/atomic-arch-fallback.h:2583 ./include/linux/atomic/atomic-instrumented.h:1611     net/core/sock_diag.c:29) kasan_report (mm/kasan/report.c:603) ? __sock_gen_cookie     (./arch/x86/include/asm/atomic64_64.h:15 ./include/linux/atomic/atomic-arch-fallback.h:2583     ./include/linux/atomic/atomic-instrumented.h:1611 net/core/sock_diag.c:29) kasan_check_range     (mm/kasan/generic.c:183 mm/kasan/generic.c:189) __sock_gen_cookie (./arch/x86/include/asm/atomic64_64.h:15     ./include/linux/atomic/atomic-arch-fallback.h:2583 ./include/linux/atomic/atomic-instrumented.h:1611     net/core/sock_diag.c:29) bpf_get_socket_ptr_cookie (./arch/x86/include/asm/preempt.h:94     ./include/linux/sock_diag.h:42 net/core/filter.c:5094 net/core/filter.c:5092)     bpf_prog_875642cf11f1d139___sock_release+0x6e/0x8e bpf_trampoline_6442506592+0x47/0xaf __sock_release     (net/socket.c:652) __sock_create (net/socket.c:1601) ... Allocated by task 299 on cpu 2 at 78.328492s:
    kasan_save_stack (mm/kasan/common.c:48) kasan_save_track (mm/kasan/common.c:68) __kasan_slab_alloc     (mm/kasan/common.c:312 mm/kasan/common.c:338) kmem_cache_alloc_noprof (mm/slub.c:3941 mm/slub.c:4000     mm/slub.c:4007) sk_prot_alloc (net/core/sock.c:2075) sk_alloc (net/core/sock.c:2134) inet_create     (net/ipv4/af_inet.c:327 net/ipv4/af_inet.c:252) __sock_create (net/socket.c:1572) __sys_socket     (net/socket.c:1660 net/socket.c:1644 net/socket.c:1706) __x64_sys_socket (net/socket.c:1718) do_syscall_64     (arch/x86/entry/common.c:52 arch/x86/entry/common.c:83) entry_SYSCALL_64_after_hwframe     (arch/x86/entry/entry_64.S:130) Freed by task 299 on cpu 2 at 78.328502s: kasan_save_stack     (mm/kasan/common.c:48) kasan_save_track (mm/kasan/common.c:68) kasan_save_free_info     (mm/kasan/generic.c:582) poison_slab_object (mm/kasan/common.c:242) __kasan_slab_free     (mm/kasan/common.c:256) kmem_cache_free (mm/slub.c:4437 mm/slub.c:4511) __sk_destruct     (net/core/sock.c:2117 net/core/sock.c:2208) inet_create (net/ipv4/af_inet.c:397 net/ipv4/af_inet.c:252)
    __sock_create (net/socket.c:1572) __sys_socket (net/socket.c:1660 net/socket.c:1644 net/socket.c:1706)
    __x64_sys_socket (net/socket.c:1718) do_syscall_64 (arch/x86/entry/common.c:52 arch/x86/entry/common.c:83)     entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Fix this by clearing the struct socket     reference in sk_common_release() to cover all protocol families create functions, which may already     attached the reference to the sk object with sock_init_data(). (CVE-2024-40954)

  - In the Linux kernel, the following vulnerability has been resolved: filelock: fix potential use-after-free     in posix_lock_inode Light Hsieh reported a KASAN UAF warning in trace_posix_lock_inode(). The request     pointer had been changed earlier to point to a lock entry that was added to the inode's list. However,     before the tracepoint could fire, another task raced in and freed that lock. Fix this by moving the     tracepoint inside the spinlock, which should ensure that this doesn't happen. (CVE-2024-41049)

  - In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Fix potential UAF by     revoke of fence registers CI has been sporadically reporting the following issue triggered by     igt@i915_selftest@live@hangcheck on ADL-P and similar machines: <6> [414.049203] i915: Running     intel_hangcheck_live_selftests/igt_reset_evict_fence ... <6> [414.068804] i915 0000:00:02.0: [drm] GT0:
    GUC: submission enabled <6> [414.068812] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled <3> [414.070354]     Unable to pin Y-tiled fence; err:-4 <3> [414.071282] i915_vma_revoke_fence:301     GEM_BUG_ON(!i915_active_is_idle(&fence->active)) ... <4>[ 609.603992] ------------[ cut here ]------------     <2>[ 609.603995] kernel BUG at drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c:301! <4>[ 609.604003] invalid     opcode: 0000 [#1] PREEMPT SMP NOPTI <4>[ 609.604006] CPU: 0 PID: 268 Comm: kworker/u64:3 Tainted: G U W     6.9.0-CI_DRM_14785-g1ba62f8cea9c+ #1 <4>[ 609.604008] Hardware name: Intel Corporation Alder Lake Client     Platform/AlderLake-P DDR4 RVP, BIOS RPLPFWI1.R00.4035.A00.2301200723 01/20/2023 <4>[ 609.604010]     Workqueue: i915 __i915_gem_free_work [i915] <4>[ 609.604149] RIP: 0010:i915_vma_revoke_fence+0x187/0x1f0     [i915] ... <4>[ 609.604271] Call Trace: <4>[ 609.604273] <TASK> ... <4>[ 609.604716]
    __i915_vma_evict+0x2e9/0x550 [i915] <4>[ 609.604852] __i915_vma_unbind+0x7c/0x160 [i915] <4>[ 609.604977]     force_unbind+0x24/0xa0 [i915] <4>[ 609.605098] i915_vma_destroy+0x2f/0xa0 [i915] <4>[ 609.605210]
    __i915_gem_object_pages_fini+0x51/0x2f0 [i915] <4>[ 609.605330] __i915_gem_free_objects.isra.0+0x6a/0xc0     [i915] <4>[ 609.605440] process_scheduled_works+0x351/0x690 ... In the past, there were similar failures     reported by CI from other IGT tests, observed on other platforms. Before commit 63baf4f3d587     (drm/i915/gt: Only wait for GPU activity before unbinding a GGTT fence), i915_vma_revoke_fence() was     waiting for idleness of vma->active via fence_update(). That commit introduced vma->fence->active in order     for the fence_update() to be able to wait selectively on that one instead of vma->active since only     idleness of fence registers was needed. But then, another commit 0d86ee35097a (drm/i915/gt: Make fence     revocation unequivocal) replaced the call to fence_update() in i915_vma_revoke_fence() with only     fence_write(), and also added that GEM_BUG_ON(!i915_active_is_idle(&fence->active)) in front. No     justification was provided on why we might then expect idleness of vma->fence->active without first     waiting on it. The issue can be potentially caused by a race among revocation of fence registers on one     side and sequential execution of signal callbacks invoked on completion of a request that was using them     on the other, still processed in parallel to revocation of those fence registers. Fix it by waiting for     idleness of vma->fence->active in i915_vma_revoke_fence(). (cherry picked from commit     24bb052d3dd499c5956abad5f7d8e4fd07da7fb1) (CVE-2024-41092)

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

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

  - In the Linux kernel, the following vulnerability has been resolved: asix: fix uninit-value in     asix_mdio_read() asix_read_cmd() may read less than sizeof(smsr) bytes and in this case smsr will be     uninitialized. Fail log: BUG: KMSAN: uninit-value in asix_check_host_enable     drivers/net/usb/asix_common.c:82 [inline] BUG: KMSAN: uninit-value in asix_check_host_enable     drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497 BUG: KMSAN: uninit-value in     asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497     asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] asix_check_host_enable     drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497 asix_mdio_read+0x3c1/0xb00     drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497 (CVE-2021-47101)

  - A flaw was found in the filelock_init in fs/locks.c function in the Linux kernel. This issue can lead to     host memory exhaustion due to memcg not limiting the number of Portable Operating System Interface (POSIX)     file locks. (CVE-2022-0480)

  - A vulnerability was found in Linux Kernel. It has been declared as problematic. Affected by this     vulnerability is the function intr_callback of the file drivers/net/usb/r8152.c of the component BPF. The     manipulation leads to logging of excessive data. The attack can be launched remotely. It is recommended to     apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-211363.
    (CVE-2022-3594)

  - In the Linux kernel, the following vulnerability has been resolved: vt_ioctl: fix array_index_nospec in     vt_setactivate array_index_nospec ensures that an out-of-bounds value is set to zero on the transient     path. Decreasing the value by one afterwards causes a transient integer underflow. vsa.console should be     decreased first and then sanitized with array_index_nospec. Kasper Acknowledgements: Jakob Koschel, Brian     Johannesmeyer, Kaveh Razavi, Herbert Bos, Cristiano Giuffrida from the VUSec group at VU Amsterdam.
    (CVE-2022-48804)

  - A flaw was found in the Linux Kernel. The tls_is_tx_ready() incorrectly checks for list emptiness,     potentially accessing a type confused entry to the list_head, leaking the last byte of the confused field     that overlaps with rec->tx_ready. (CVE-2023-1075)

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
361222	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2024:1731933167)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	critical
361440	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2025:1743193221)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/2	medium

偵測

搜尋 Plugin

critical

medium