In the Linux kernel, the following vulnerability has been resolved: md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync - recovery_active' to show user a progress bar like following: [============>........] resync = 61.4% 'curr_resync' and 'recovery_active' is updated in md_do_sync(), and status_resync() can read them concurrently, hence it's possible that 'curr_resync - recovery_active' can overflow to a huge number. In this case status_resync() will be stuck in the loop to print a large amount of '=', which will end up soft lockup. Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case, this way resync in progress will be reported to user.

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.

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

    In the Linux kernel, the following vulnerability has been resolved:

    md: fix soft lockup in status_resync

    status_resync() will calculate 'curr_resync - recovery_active' to show     user a progress bar like following:

    [============>........]  resync = 61.4%

    'curr_resync' and 'recovery_active' is updated in md_do_sync(), and     status_resync() can read them concurrently, hence it's possible that     'curr_resync - recovery_active' can overflow to a huge number. In this     case status_resync() will be stuck in the loop to print a large amount     of '=', which will end up soft lockup.

    Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case,     this way resync in progress will be reported to user.

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-010921 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    md: fix soft lockup in status_resync

    status_resync() will calculate 'curr_resync - recovery_active' to show     user a progress bar like following:

    [============>........]  resync = 61.4%

    'curr_resync' and 'recovery_active' is updated in md_do_sync(), and     status_resync() can read them concurrently, hence it's possible that     'curr_resync - recovery_active' can overflow to a huge number. In this     case status_resync() will be stuck in the loop to print a large amount     of '=', which will end up soft lockup.

    Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case,     this way resync in progress will be reported to user.

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-013155 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    md: fix soft lockup in status_resync

    status_resync() will calculate 'curr_resync - recovery_active' to show     user a progress bar like following:

    [============>........]  resync = 61.4%

    'curr_resync' and 'recovery_active' is updated in md_do_sync(), and     status_resync() can read them concurrently, hence it's possible that     'curr_resync - recovery_active' can overflow to a huge number. In this     case status_resync() will be stuck in the loop to print a large amount     of '=', which will end up soft lockup.

    Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case,     this way resync in progress will be reported to user.

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 remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4189-1 advisory.

    The SUSE Linux Enterprise 12 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2021-4460: drm/amdkfd: Fix UBSAN shift-out-of-bounds warning (bsc#1250764).
    - CVE-2022-48631: ext4: fix bug in extents parsing when eh_entries == 0 and eh_depth > 0 (bsc#1223475).
    - CVE-2022-50236: iommu/mediatek: Fix crash on isr after kexec() (bsc#1249702).
    - CVE-2022-50249: memory: of: Fix refcount leak bug in of_get_ddr_timings() (bsc#1249747).
    - CVE-2022-50280: pnode: terminate at peers of source (bsc#1249806).
    - CVE-2022-50293: btrfs: do not BUG_ON() on ENOMEM when dropping extent items for a range (bsc#1249752).
    - CVE-2022-50327: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value (bsc#1249859).
    - CVE-2022-50350: scsi: target: iscsi: Fix a race condition between login_work and the login thread     (bsc#1250261).
    - CVE-2022-50356: net: sched: sfb: fix null pointer access issue when sfb_init() fails (bsc#1250040).
    - CVE-2022-50367: fs: fix UAF/GPF bug in nilfs_mdt_destroy (bsc#1250277).
    - CVE-2022-50394: i2c: ismt: Fix an out-of-bounds bug in ismt_access() (bsc#1250107).
    - CVE-2022-50395: integrity: Fix memory leakage in keyring allocation error path (bsc#1250211).
    - CVE-2022-50423: ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage() (bsc#1250784).
    - CVE-2022-50443: drm/rockchip: lvds: fix PM usage counter unbalance in poweron (bsc#1250768).
    - CVE-2022-50459: scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername() (bsc#1250850).
    - CVE-2022-50481: cxl: fix possible null-ptr-deref in cxl_guest_init_afu|adapter() (bsc#1251051).
    - CVE-2022-50485: ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode (bsc#1251197).
    - CVE-2022-50505: iommu/amd: Fix pci device refcount leak in ppr_notifier() (bsc#1251086).
    - CVE-2022-50516: fs: dlm: fix invalid derefence of sb_lvbptr (bsc#1251741).
    - CVE-2022-50542: media: si470x: Fix use-after-free in si470x_int_in_callback() (bsc#1251330).
    - CVE-2022-50571: btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure (bsc#1252487).
    - CVE-2023-53183: btrfs: exit gracefully if reloc roots don't match (bsc#1249863).
    - CVE-2023-53185: wifi: ath9k: don't allow to overwrite ENDPOINT0 attributes (bsc#1249820).
    - CVE-2023-53188: net: openvswitch: fix race on port output (bsc#1249854).
    - CVE-2023-53191: irqchip/alpine-msi: Fix refcount leak in alpine_msix_init_domains (bsc#1249721).
    - CVE-2023-53204: af_unix: Fix data-races around user->unix_inflight (bsc#1249682).
    - CVE-2023-53271: ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume() (bsc#1249916).
    - CVE-2023-53282: scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write     (bsc#1250311).
    - CVE-2023-53289: media: bdisp: Add missing check for create_workqueue (bsc#1249941).
    - CVE-2023-53292: blk-mq: protect q->elevator by ->sysfs_lock in blk_mq_elv_switch_none (bsc#1250163).
    - CVE-2023-53338: lwt: Fix return values of BPF xmit ops (bsc#1250074).
    - CVE-2023-53339: btrfs: fix BUG_ON condition in btrfs_cancel_balance (bsc#1250329).
    - CVE-2023-53373: crypto: seqiv - Handle EBUSY correctly (bsc#1250137).
    - CVE-2023-53433: net: add vlan_get_protocol_and_depth() helper (bsc#1250164).
    - CVE-2023-53476: iw_cxgb4: Fix potential NULL dereference in c4iw_fill_res_cm_id_entry() (bsc#1250839).
    - CVE-2023-53477: ipv6: Add lwtunnel encap size of all siblings in nexthop calculation (bsc#1250840).
    - CVE-2023-53484: lib: cpu_rmap: Avoid use after free on rmap->obj array entries (bsc#1250895).
    - CVE-2023-53517: tipc: do not update mtu if msg_max is too small in mtu negotiation (bsc#1250919).
    - CVE-2023-53519: media: v4l2-mem2mem: add lock to protect parameter num_rdy (bsc#1250964).
    - CVE-2023-53540: wifi: cfg80211: reject auth/assoc to AP with our address (bsc#1251053).
    - CVE-2023-53548: net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb (bsc#1251066).
    - CVE-2023-53556: iavf: Fix use-after-free in free_netdev (bsc#1251059).
    - CVE-2023-53559: ip_vti: fix potential slab-use-after-free in decode_session6 (bsc#1251052).
    - CVE-2023-53582: wifi: brcmfmac: ensure CLM version is null-terminated to prevent stack-out-of-bounds     (bsc#1251061).
    - CVE-2023-53589: wifi: iwlwifi: mvm: don't trust firmware n_channels (bsc#1251129).
    - CVE-2023-53593: cifs: Release folio lock on fscache read hit (bsc#1251132).
    - CVE-2023-53594: driver core: fix resource leak in device_add() (bsc#1251166).
    - CVE-2023-53596: drivers: base: Free devm resources when unregistering a device (bsc#1251161).
    - CVE-2023-53619: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free (bsc#1251743).
    - CVE-2023-53620: md: fix soft lockup in status_resync.
    - CVE-2023-53624: net/sched: sch_fq: fix integer overflow of 'credit' (bsc#1251333).
    - CVE-2023-53635: netfilter: conntrack: fix wrong ct->timeout value (bsc#1251524).
    - CVE-2023-53648: ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer (bsc#1251750).
    - CVE-2023-53687: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating     clk (bsc#1251772).
    - CVE-2023-53695: udf: Detect system inodes linked into directory hierarchy (bsc#1252539).
    - CVE-2023-53705: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (bsc#1252554).
    - CVE-2023-53707: drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1 (bsc#1252632).
    - CVE-2023-53715: wifi: brcmfmac: cfg80211: Pass the PMK in binary instead of hex (bsc#1252545).
    - CVE-2023-53717: wifi: ath9k: Fix potential stack-out-of-bounds write in ath9k_wmi_rsp_callback()     (bsc#1252560).
    - CVE-2023-53733: net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode (bsc#1252685).
    - CVE-2025-38539: trace/fgraph: Fix the warning caused by missing unregister notifier (bsc#1248211).
    - CVE-2025-38680: media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (bsc#1249203).
    - CVE-2025-38691: pNFS: Fix uninited ptr deref in block/scsi layout (bsc#1249215).
    - CVE-2025-38695: scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1249285).
    - CVE-2025-38699: scsi: bfa: Double-free fix (bsc#1249224).
    - CVE-2025-38700: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated     (bsc#1249182).
    - CVE-2025-38714: hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() (bsc#1249260).
    - CVE-2025-38718: sctp: linearize cloned gso packets in sctp_rcv (bsc#1249161).
    - CVE-2025-38724: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (bsc#1249169).
    - CVE-2025-39676: scsi: qla4xxx: Prevent a potential error pointer dereference (bsc#1249302).
    - CVE-2025-39702: ipv6: sr: Fix MAC comparison to be constant-time (bsc#1249317).
    - CVE-2025-39724: serial: 8250: fix panic due to PSLVERR (bsc#1249265).
    - CVE-2025-39756: fs: Prevent file descriptor table allocations exceeding INT_MAX (bsc#1249512).
    - CVE-2025-39772: drm/hisilicon/hibmc: fix the hibmc loaded failed bug (bsc#1249506).
    - CVE-2025-39812: sctp: initialize more fields in sctp_v6_from_sk() (bsc#1250202).
    - CVE-2025-39813: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump (bsc#1250032).
    - CVE-2025-39841: scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250274).
    - CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty() (bsc#1250455).
    - CVE-2025-39876: net: fec: Fix possible NPD in fec_enet_phy_reset_after_clk_enable() (bsc#1250400).
    - CVE-2025-39911: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path (bsc#1250704).
    - CVE-2025-39923: dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (bsc#1250741).
    - CVE-2025-39929: smb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path (bsc#1251036).
    - CVE-2025-39931: crypto: af_alg - Set merge to zero early in af_alg_sendmsg (bsc#1251100).
    - CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).
    - CVE-2025-39949: qed: Don't collect too many protection override GRC elements (bsc#1251177).
    - CVE-2025-39955: tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect() (bsc#1251804).
    - CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).
    - CVE-2025-39970: i40e: Fix filter input checks to prevent config with invalid values (bsc#1252051).
    - CVE-2025-39971: i40e: Add bounds check for ch[] array (bsc#1252052).
    - CVE-2025-39972: i40e: fix idx validation in i40e_validate_queue_map (bsc#1252039).
    - CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).
    - CVE-2025-39997: ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (bsc#1252056).
    - CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).
    - CVE-2025-40044: fs: udf: fix OOB read in lengthAllocDescs handling (bsc#1252785).
    - CVE-2025-40049: Squashfs: fix uninit-value in squashfs_get_parent (bsc#1252822).
    - CVE-2025-40078: bpf: Explicitly check accesses to bpf_sock_addr (bsc#1252789).
    - CVE-2025-40082: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1252775).
    - CVE-2025-40088: hfsplus: fix slab-out-of-bounds read in hfsplus_strcasecmp() (bsc#1252904).

    The following non security issues were fixed:

    - NFSv4.1: fix backchannel max_resp_sz verification check (bsc#1247518).
    - net: hv_netvsc: fix loss of early receive events from host during channel open (bsc#1252265).
    - openvswitch: fix lockup on tx to unregistering netdev with carrier (bsc#1249854)

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

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.

  - md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync - recovery_active' to     show user a progress bar like following: [============>........] resync = 61.4% 'curr_resync' and     'recovery_active' is updated in md_do_sync(), and status_resync() can read them concurrently, hence it's     possible that 'curr_resync - recovery_active' can overflow to a huge number. In this case status_resync()     will be stuck in the loop to print a large amount of '=', which will end up soft lockup. Fix the problem     by setting 'resync' to MD_RESYNC_ACTIVE in this case, this way resync in progress will be reported to     user. (CVE-2023-53620)

Note that Nessus relies on the presence of the package as reported by the vendor.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-228 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    binder: fix UAF of alloc->vma in race with munmap() (CVE-2022-50240)

    In the Linux kernel, the following vulnerability has been resolved:

    binder: fix UAF of alloc->vma in race with munmap() (CVE-2022-50338)

    A flaw was found in the Linux kernel's networking subsystem within the RPL protocol's handling. This issue     results from the improper handling of user-supplied data, which can lead to an assertion failure. This     flaw allows an unauthenticated, remote attacker to create a denial of service condition on the system.
    (CVE-2023-2156)

    A heap out-of-bounds write vulnerability in the Linux Kernel ipvlan network driver can be exploited to     achieve local privilege escalation.

    The out-of-bounds write is caused by missing skb->cb  initialization in the ipvlan network driver. The     vulnerability is reachable if CONFIG_IPVLAN is enabled.

    We recommend upgrading past commit 90cbed5247439a966b645b34eb0a2e037836ea8e. (CVE-2023-3090)

    A use-after-free flaw was found in vcs_read in drivers/tty/vt/vc_screen.c in vc_screen in the Linux     Kernel. In this flaw an attacker with local user access may lead to a system crash or a leak of internal     kernel information. (CVE-2023-3567)

    An issue was discovered in fl_set_geneve_opt in net/sched/cls_flower.c in the Linux kernel before 6.3.7.
    It allows an out-of-bounds write in the flower classifier code via TCA_FLOWER_KEY_ENC_OPTS_GENEVE packets.
    This may result in denial of service or privilege escalation. (CVE-2023-35788)

    In the Linux kernel, the following vulnerability has been resolved:

    serial: 8250: Reinit port->pm on port specific driver unbind (CVE-2023-53176)

    In the Linux kernel, the following vulnerability has been resolved:

    mm: fix zswap writeback race condition (CVE-2023-53178)

    In the Linux kernel, the following vulnerability has been resolved:

    ACPICA: Avoid undefined behavior: applying zero offset to null pointer (CVE-2023-53182)

    In the Linux kernel, the following vulnerability has been resolved:

    irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4 (CVE-2023-53383)

    In the Linux kernel, the following vulnerability has been resolved:

    rcu: Protect rcu_print_task_exp_stall() ->exp_tasks access (CVE-2023-53419)

    In the Linux kernel, the following vulnerability has been resolved:

    net: add vlan_get_protocol_and_depth() helper (CVE-2023-53433)

    In the Linux kernel, the following vulnerability has been resolved:

    net: skb_partial_csum_set() fix against transport header magic value (CVE-2023-53439)

    In the Linux kernel, the following vulnerability has been resolved:

    ACPI: processor: Check for null return of devm_kzalloc() in fch_misc_setup() (CVE-2023-53483)

    In the Linux kernel, the following vulnerability has been resolved:

    lib: cpu_rmap: Avoid use after free on rmap->obj array entries (CVE-2023-53484)

    In the Linux kernel, the following vulnerability has been resolved:

    virtio_net: Fix error unwinding of XDP initialization (CVE-2023-53499)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: allow ext4_get_group_info() to fail (CVE-2023-53503)

    In the Linux kernel, the following vulnerability has been resolved:

    nbd: fix incomplete validation of ioctl arg (CVE-2023-53513)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nft_set_rbtree: fix null deref on element insertion (CVE-2023-53566)

    In the Linux kernel, the following vulnerability has been resolved:

    null_blk: Always check queue mode setting from configfs (CVE-2023-53576)

    In the Linux kernel, the following vulnerability has been resolved:

    md: fix soft lockup in status_resync (CVE-2023-53620)

    In the Linux kernel, the following vulnerability has been resolved:

    tun: Fix memory leak for detached NAPI queue. (CVE-2023-53685)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv6: Fix out-of-bounds access in ipv6_find_tlv() (CVE-2023-53705)

    In the Linux kernel, the following vulnerability has been resolved:

    net: fix skb leak in __skb_tstamp_tx() (CVE-2023-53716)

    In the Linux kernel, the following vulnerability has been resolved:

    vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF (CVE-2023-53747)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/i915: Fix NULL ptr deref by checking new_crtc_state (CVE-2023-53833)

    In the Linux kernel, the following vulnerability has been resolved:

    netlink: annotate accesses to nlk->cb_running (CVE-2023-53853)

    In the Linux kernel, the following vulnerability has been resolved:

    udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated(). (CVE-2023-54004)

    In the Linux kernel, the following vulnerability has been resolved:

    net: fix stack overflow when LRO is disabled for virtual interfaces (CVE-2023-54012)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: set goal start correctly in ext4_mb_normalize_request (CVE-2023-54021)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps (CVE-2023-54033)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Add preempt_count_{sub,add} into btf id deny list (CVE-2023-54086)

    In the Linux kernel, the following vulnerability has been resolved:

    net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (CVE-2023-54114)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/fbdev-generic: prohibit potential out-of-bounds access (CVE-2023-54116)

    In the Linux kernel, the following vulnerability has been resolved:

    binder: fix UAF of alloc->vma in race with munmap() (CVE-2023-54157)

    In the Linux kernel, the following vulnerability has been resolved:

    firmware: arm_sdei: Fix sleep from invalid context BUG (CVE-2023-54160)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: target: iscsit: Free cmds before session free (CVE-2023-54184)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nf_tables: always release netdev hooks from notifier (CVE-2023-54200)

    In the Linux kernel, the following vulnerability has been resolved:

    net: Fix load-tearing on sk->sk_stamp in sock_recv_cmsgs(). (CVE-2023-54218)

    In the Linux kernel, the following vulnerability has been resolved:

    af_unix: Fix data races around sk->sk_shutdown. (CVE-2023-54226)

    In the Linux kernel, the following vulnerability has been resolved:

    block, bfq: Fix division by zero error on zero wsum (CVE-2023-54242)

    In the Linux kernel, the following vulnerability has been resolved:

    ACPI: EC: Fix oops when removing custom query handlers (CVE-2023-54244)

    In the Linux kernel, the following vulnerability has been resolved:

    debugobjects: Don't wake up kswapd from fill_pool() (CVE-2023-54268)

    In the Linux kernel, the following vulnerability has been resolved:

    SUNRPC: double free xprt_ctxt while still in use (CVE-2023-54269)

Tenable has extracted the preceding description block directly from the tested product security advisory.

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	Type	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	Local	high
309387	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-013851)	Nessus	Unity Linux Local Security Checks	Local	medium
308404	Unity Linux 20.1070e Security Update: kernel (UTSA-2026-010921)	Nessus	Unity Linux Local Security Checks	Local	medium
308032	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-013155)	Nessus	Unity Linux Local Security Checks	Local	medium
302981	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2026-1637)	Nessus	Huawei Local Security Checks	Local	high
302971	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2026-1629)	Nessus	Huawei Local Security Checks	Local	high
297598	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1212)	Nessus	Huawei Local Security Checks	Local	high
297592	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1224)	Nessus	Huawei Local Security Checks	Local	high
276910	SUSE SLES12: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:4189-1)	Nessus	SuSE Local Security Checks	Local	high
270164	Linux Distros Unpatched Vulnerability : CVE-2023-53620	Nessus	Misc.	Local	medium
177674	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2023-228)	Nessus	Amazon Linux Local Security Checks	Local	high

Detections

Analytics

CVE-2023-53620

medium

Tenable Plugins

high

medium

medium

medium

high

high

high

high

high

medium

high