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

  - In the Linux kernel, the following vulnerability has been resolved: net: amd-xgbe: Fix skb data length     underflow There will be BUG_ON() triggered in include/linux/skbuff.h leading to intermittent kernel panic,     when the skb length underflow is detected. Fix this by dropping the packet if such length underflows are     seen because of inconsistencies in the hardware descriptors. (CVE-2022-48743)

  - In the Linux kernel, the following vulnerability has been resolved: net: bcmgenet: Use stronger register     read/writes to assure ordering GCC12 appears to be much smarter about its dependency tracking and is aware     that the relaxed variants are just normal loads and stores and this is causing problems like: [     210.074549] ------------[ cut here ]------------ [ 210.079223] NETDEV WATCHDOG: enabcm6e4ei0 (bcmgenet):
    transmit queue 1 timed out [ 210.086717] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:529     dev_watchdog+0x234/0x240 [ 210.095044] Modules linked in: genet(E) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6     nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat] [ 210.146561] ACPI     CPPC: PCC check channel failed for ss: 0. ret=-110 [ 210.146927] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G     E 5.17.0-rc7G12+ #58 [ 210.153226] CPPC Cpufreq:cppc_scale_freq_workfn: failed to read perf counters [     210.161349] Hardware name: Raspberry Pi Foundation Raspberry Pi 4 Model B/Raspberry Pi 4 Model B, BIOS     EDK2-DEV 02/08/2022 [ 210.161353] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [     210.161358] pc : dev_watchdog+0x234/0x240 [ 210.161364] lr : dev_watchdog+0x234/0x240 [ 210.161368] sp :
    ffff8000080a3a40 [ 210.161370] x29: ffff8000080a3a40 x28: ffffcd425af87000 x27: ffff8000080a3b20 [     210.205150] x26: ffffcd425aa00000 x25: 0000000000000001 x24: ffffcd425af8ec08 [ 210.212321] x23:
    0000000000000100 x22: ffffcd425af87000 x21: ffff55b142688000 [ 210.219491] x20: 0000000000000001 x19:
    ffff55b1426884c8 x18: ffffffffffffffff [ 210.226661] x17: 64656d6974203120 x16: 0000000000000001 x15:
    6d736e617274203a [ 210.233831] x14: 2974656e65676d63 x13: ffffcd4259c300d8 x12: ffffcd425b07d5f0 [     210.241001] x11: 00000000ffffffff x10: ffffcd425b07d5f0 x9 : ffffcd4258bdad9c [ 210.248171] x8 :
    00000000ffffdfff x7 : 000000000000003f x6 : 0000000000000000 [ 210.255341] x5 : 0000000000000000 x4 :
    0000000000000000 x3 : 0000000000001000 [ 210.262511] x2 : 0000000000001000 x1 : 0000000000000005 x0 :
    0000000000000044 [ 210.269682] Call trace: [ 210.272133] dev_watchdog+0x234/0x240 [ 210.275811]     call_timer_fn+0x3c/0x15c [ 210.279489] __run_timers.part.0+0x288/0x310 [ 210.283777]     run_timer_softirq+0x48/0x80 [ 210.287716] __do_softirq+0x128/0x360 [ 210.291392]
    __irq_exit_rcu+0x138/0x140 [ 210.295243] irq_exit_rcu+0x1c/0x30 [ 210.298745] el1_interrupt+0x38/0x54 [     210.302334] el1h_64_irq_handler+0x18/0x24 [ 210.306445] el1h_64_irq+0x7c/0x80 [ 210.309857]     arch_cpu_idle+0x18/0x2c [ 210.313445] default_idle_call+0x4c/0x140 [ 210.317470]     cpuidle_idle_call+0x14c/0x1a0 [ 210.321584] do_idle+0xb0/0x100 [ 210.324737] cpu_startup_entry+0x30/0x8c [     210.328675] secondary_start_kernel+0xe4/0x110 [ 210.333138] __secondary_switched+0x94/0x98 The assumption     when these were relaxed seems to be that device memory would be mapped non reordering, and that other     constructs (spinlocks/etc) would provide the barriers to assure that packet data and in memory     rings/queues were ordered with respect to device register reads/writes. This itself seems a bit sketchy,     but the real problem with GCC12 is that it is moving the actual reads/writes around at will as though they     were independent operations when in truth they are not, but the compiler can't know that. When looking at     the assembly dumps for many of these routines its possible to see very clean, but not strictly in program     order operations occurring as the compiler would be free to do if these weren't actually register     reads/write operations. Its possible to suppress the timeout with a liberal bit of dma_mb()'s sprinkled     around but the device still seems unable to reliably send/receive data. A better plan is to use the safer     readl/writel everywhere. Since this partially reverts an older commit, which notes the use of the relaxed     variants for performance reasons. I would suggest that any performance problems ---truncated---     (CVE-2022-49194)

  - In the Linux kernel, the following vulnerability has been resolved: ima: Fix a potential integer overflow     in ima_appraise_measurement When the ima-modsig is enabled, the rc passed to evm_verifyxattr() may be     negative, which may cause the integer overflow problem. (CVE-2022-49643)

  - In the Linux kernel, the following vulnerability has been resolved: ovl: Use buf flexible array for     memcpy() destination The buf flexible array needs to be the memcpy() destination to avoid false positive     run-time warning from the recent FORTIFY_SOURCE hardening: memcpy: detected field-spanning write (size 93)     of single field &fh->fb at fs/overlayfs/export.c:799 (size 21) (CVE-2022-49743)

  - In the Linux kernel, the following vulnerability has been resolved: kprobes: Skip clearing aggrprobe's     post_handler in kprobe-on-ftrace case In __unregister_kprobe_top(), if the currently unregistered probe     has post_handler but other child probes of the aggrprobe do not have post_handler, the post_handler of the     aggrprobe is cleared. If this is a ftrace-based probe, there is a problem. In later calls to     disarm_kprobe(), we will use kprobe_ftrace_ops because post_handler is NULL. But we're armed with     kprobe_ipmodify_ops. This triggers a WARN in __disarm_kprobe_ftrace() and may even cause use-after-free:
    Failed to disarm kprobe-ftrace at kernel_clone+0x0/0x3c0 (error -2) WARNING: CPU: 5 PID: 137 at     kernel/kprobes.c:1135 __disarm_kprobe_ftrace.isra.21+0xcf/0xe0 Modules linked in: testKprobe_007(-) CPU: 5     PID: 137 Comm: rmmod Not tainted 6.1.0-rc4-dirty #18 [...] Call Trace: <TASK> __disable_kprobe+0xcd/0xe0
    __unregister_kprobe_top+0x12/0x150 ? mutex_lock+0xe/0x30 unregister_kprobes.part.23+0x31/0xa0     unregister_kprobe+0x32/0x40 __x64_sys_delete_module+0x15e/0x260 ? do_user_addr_fault+0x2cd/0x6b0     do_syscall_64+0x3a/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] For the kprobe-on-ftrace case, we     keep the post_handler setting to identify this aggrprobe armed with kprobe_ipmodify_ops. This way we can     disarm it correctly. (CVE-2022-49779)

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

An update of the linux package has been released.

The AlmaLinux 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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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 relies on the presence of the package as reported by the vendor.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-011381 advisory.

    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.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-005770 advisory.

    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.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

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

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.

ID	Name	Product	Family	Published	Updated	Severity
353122	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1779375889)	Nessus	Alma Linux Local Security Checks	9/30/2026	10/1/2026	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	10/9/2026	high
351722	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1780052998)	Nessus	Alma Linux Local Security Checks	9/30/2026	10/5/2026	high
264926	Linux Distros Unpatched Vulnerability : CVE-2023-53225	Nessus	Misc.	9/16/2025	9/30/2026	medium
308790	Unity Linux 20.1050e / 20.1070e Security Update: kernel (UTSA-2026-011381)	Nessus	Unity Linux Local Security Checks	4/21/2026	4/22/2026	medium
300373	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-005770)	Nessus	Unity Linux Local Security Checks	3/3/2026	3/3/2026	medium
351610	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1780052998)	Nessus	Rocky Linux Local Security Checks	9/30/2026	10/5/2026	high

Detections

Analytics

Plugins Search

high

high

high

medium

medium

medium

high