In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix sysfs interface lifetime The current nilfs2 sysfs support has issues with the timing of creation and deletion of sysfs entries, potentially leading to null pointer dereferences, use-after-free, and lockdep warnings. Some of the sysfs attributes for nilfs2 per-filesystem instance refer to metadata file "cpfile", "sufile", or "dat", but nilfs_sysfs_create_device_group that creates those attributes is executed before the inodes for these metadata files are loaded, and nilfs_sysfs_delete_device_group which deletes these sysfs entries is called after releasing their metadata file inodes. Therefore, access to some of these sysfs attributes may occur outside of the lifetime of these metadata files, resulting in inode NULL pointer dereferences or use-after-free. In addition, the call to nilfs_sysfs_create_device_group() is made during the locking period of the semaphore "ns_sem" of nilfs object, so the shrinker call caused by the memory allocation for the sysfs entries, may derive lock dependencies "ns_sem" -> (shrinker) -> "locks acquired in nilfs_evict_inode()". Since nilfs2 may acquire "ns_sem" deep in the call stack holding other locks via its error handler __nilfs_error(), this causes lockdep to report circular locking. This is a false positive and no circular locking actually occurs as no inodes exist yet when nilfs_sysfs_create_device_group() is called. Fortunately, the lockdep warnings can be resolved by simply moving the call to nilfs_sysfs_create_device_group() out of "ns_sem". This fixes these sysfs issues by revising where the device's sysfs interface is created/deleted and keeping its lifetime within the lifetime of the metadata files above.

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

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

    nilfs2: fix sysfs interface lifetime

    The current nilfs2 sysfs support has issues with the timing of creation     and deletion of sysfs entries, potentially leading to null pointer     dereferences, use-after-free, and lockdep warnings.

    Some of the sysfs attributes for nilfs2 per-filesystem instance refer to     metadata file cpfile, sufile, or dat, but     nilfs_sysfs_create_device_group that creates those attributes is executed     before the inodes for these metadata files are loaded, and     nilfs_sysfs_delete_device_group which deletes these sysfs entries is     called after releasing their metadata file inodes.

    Therefore, access to some of these sysfs attributes may occur outside of     the lifetime of these metadata files, resulting in inode NULL pointer     dereferences or use-after-free.

    In addition, the call to nilfs_sysfs_create_device_group() is made during     the locking period of the semaphore ns_sem of nilfs object, so the     shrinker call caused by the memory allocation for the sysfs entries, may     derive lock dependencies ns_sem -> (shrinker) -> locks acquired in     nilfs_evict_inode().

    Since nilfs2 may acquire ns_sem deep in the call stack holding other     locks via its error handler __nilfs_error(), this causes lockdep to report     circular locking.  This is a false positive and no circular locking     actually occurs as no inodes exist yet when     nilfs_sysfs_create_device_group() is called.  Fortunately, the lockdep     warnings can be resolved by simply moving the call to     nilfs_sysfs_create_device_group() out of ns_sem.

    This fixes these sysfs issues by revising where the device's sysfs     interface is created/deleted and keeping its lifetime within the lifetime     of the metadata files above.

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-2025-992997 advisory.

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

    nilfs2: fix sysfs interface lifetime

    The current nilfs2 sysfs support has issues with the timing of creation     and deletion of sysfs entries, potentially leading to null pointer     dereferences, use-after-free, and lockdep warnings.

    Some of the sysfs attributes for nilfs2 per-filesystem instance refer to     metadata file cpfile, sufile, or dat, but     nilfs_sysfs_create_device_group that creates those attributes is executed     before the inodes for these metadata files are loaded, and     nilfs_sysfs_delete_device_group which deletes these sysfs entries is     called after releasing their metadata file inodes.

    Therefore, access to some of these sysfs attributes may occur outside of     the lifetime of these metadata files, resulting in inode NULL pointer     dereferences or use-after-free.

    In addition, the call to nilfs_sysfs_create_device_group() is made during     the locking period of the semaphore ns_sem of nilfs object, so the     shrinker call caused by the memory allocation for the sysfs entries, may     derive lock dependencies ns_sem -> (shrinker) -> locks acquired in     nilfs_evict_inode().

    Since nilfs2 may acquire ns_sem deep in the call stack holding other     locks via its error handler __nilfs_error(), this causes lockdep to report     circular locking.  This is a false positive and no circular locking     actually occurs as no inodes exist yet when     nilfs_sysfs_create_device_group() is called.  Fortunately, the lockdep     warnings can be resolved by simply moving the call to     nilfs_sysfs_create_device_group() out of ns_sem.

    This fixes these sysfs issues by revising where the device's sysfs     interface is created/deleted and keeping its lifetime within the lifetime     of the metadata files above.

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-2025-992575 advisory.

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

    nilfs2: fix sysfs interface lifetime

    The current nilfs2 sysfs support has issues with the timing of creation     and deletion of sysfs entries, potentially leading to null pointer     dereferences, use-after-free, and lockdep warnings.

    Some of the sysfs attributes for nilfs2 per-filesystem instance refer to     metadata file cpfile, sufile, or dat, but     nilfs_sysfs_create_device_group that creates those attributes is executed     before the inodes for these metadata files are loaded, and     nilfs_sysfs_delete_device_group which deletes these sysfs entries is     called after releasing their metadata file inodes.

    Therefore, access to some of these sysfs attributes may occur outside of     the lifetime of these metadata files, resulting in inode NULL pointer     dereferences or use-after-free.

    In addition, the call to nilfs_sysfs_create_device_group() is made during     the locking period of the semaphore ns_sem of nilfs object, so the     shrinker call caused by the memory allocation for the sysfs entries, may     derive lock dependencies ns_sem -> (shrinker) -> locks acquired in     nilfs_evict_inode().

    Since nilfs2 may acquire ns_sem deep in the call stack holding other     locks via its error handler __nilfs_error(), this causes lockdep to report     circular locking.  This is a false positive and no circular locking     actually occurs as no inodes exist yet when     nilfs_sysfs_create_device_group() is called.  Fortunately, the lockdep     warnings can be resolved by simply moving the call to     nilfs_sysfs_create_device_group() out of ns_sem.

    This fixes these sysfs issues by revising where the device's sysfs     interface is created/deleted and keeping its lifetime within the lifetime     of the metadata files above.

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-2025-992393 advisory.

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

    nilfs2: fix sysfs interface lifetime

    The current nilfs2 sysfs support has issues with the timing of creation     and deletion of sysfs entries, potentially leading to null pointer     dereferences, use-after-free, and lockdep warnings.

    Some of the sysfs attributes for nilfs2 per-filesystem instance refer to     metadata file cpfile, sufile, or dat, but     nilfs_sysfs_create_device_group that creates those attributes is executed     before the inodes for these metadata files are loaded, and     nilfs_sysfs_delete_device_group which deletes these sysfs entries is     called after releasing their metadata file inodes.

    Therefore, access to some of these sysfs attributes may occur outside of     the lifetime of these metadata files, resulting in inode NULL pointer     dereferences or use-after-free.

    In addition, the call to nilfs_sysfs_create_device_group() is made during     the locking period of the semaphore ns_sem of nilfs object, so the     shrinker call caused by the memory allocation for the sysfs entries, may     derive lock dependencies ns_sem -> (shrinker) -> locks acquired in     nilfs_evict_inode().

    Since nilfs2 may acquire ns_sem deep in the call stack holding other     locks via its error handler __nilfs_error(), this causes lockdep to report     circular locking.  This is a false positive and no circular locking     actually occurs as no inodes exist yet when     nilfs_sysfs_create_device_group() is called.  Fortunately, the lockdep     warnings can be resolved by simply moving the call to     nilfs_sysfs_create_device_group() out of ns_sem.

    This fixes these sysfs issues by revising where the device's sysfs     interface is created/deleted and keeping its lifetime within the lifetime     of the metadata files above.

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 SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:03628-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-49138: Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt (bsc#1238160).
    - CVE-2022-49980: USB: gadget: fix use-after-free read in usb_udc_uevent() (bsc#1245110).
    - CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev->{dev_name,short_name} (bsc#1246968).
    - CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).
    - CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).
    - CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).
    - CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).
    - CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).
    - CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint (bsc#1242573).
    - CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).
    - CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).
    - CVE-2025-37958: mm/huge_memory: fix dereferencing invalid pmd migration entry (bsc#1243539).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38084: mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245498).
    - CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245499).
    - CVE-2025-38111: net/mdiobus: Fix potential out-of-bounds read/write access (bsc#1245666).
    - CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).
    - CVE-2025-38380: i2c/designware: Fix an initialization issue (bsc#1247028).
    - CVE-2025-38470: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime     (bsc#1247288).
    - CVE-2025-38476: rpl: Fix use-after-free in rpl_do_srh_inline() (bsc#1247317).
    - CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).
    - CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree     (bsc#1248255).
    - CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).
    - CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).
    - CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).
    - CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).
    - CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).
    - CVE-2025-38706: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (bsc#1249195).
    - CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).
    - CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).
    - CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).
    - CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).
    - CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).
    - CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).
    - CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).
    - CVE-2025-39790: bus: mhi: host: Detect events pointing to unexpected TREs (bsc#1249548).
    - CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).
    - CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).
    - CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).
    - CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).
    - CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).


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

    The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-49138: Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt (bsc#1238160).
    - CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev->{dev_name,short_name} (bsc#1246968).
    - CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).
    - CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).
    - CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).
    - CVE-2023-53257: wifi: mac80211: check S1G action frame size (bsc#1249869).
    - CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).
    - CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).
    - CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).
    - CVE-2025-37958: mm/huge_memory: fix dereferencing invalid pmd migration entry (bsc#1243539).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38111: net/mdiobus: Fix potential out-of-bounds read/write access (bsc#1245666).
    - CVE-2025-38380: i2c/designware: Fix an initialization issue (bsc#1247028).
    - CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).
    - CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree     (bsc#1248255).
    - CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).
    - CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).
    - CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).
    - CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).
    - CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).
    - CVE-2025-38706: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (bsc#1249195).
    - CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).
    - CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).
    - CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).
    - CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).
    - CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).
    - CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).
    - CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).
    - CVE-2025-39790: bus: mhi: host: Detect events pointing to unexpected TREs (bsc#1249548).
    - CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).
    - CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).
    - CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).
    - CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).


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.

  - nilfs2: fix sysfs interface lifetime The current nilfs2 sysfs support has issues with the timing of     creation and deletion of sysfs entries, potentially leading to null pointer dereferences, use-after-free,     and lockdep warnings. Some of the sysfs attributes for nilfs2 per-filesystem instance refer to metadata     file cpfile, sufile, or dat, but nilfs_sysfs_create_device_group that creates those attributes is     executed before the inodes for these metadata files are loaded, and nilfs_sysfs_delete_device_group which     deletes these sysfs entries is called after releasing their metadata file inodes. Therefore, access to     some of these sysfs attributes may occur outside of the lifetime of these metadata files, resulting in     inode NULL pointer dereferences or use-after-free. In addition, the call to     nilfs_sysfs_create_device_group() is made during the locking period of the semaphore ns_sem of nilfs     object, so the shrinker call caused by the memory allocation for the sysfs entries, may derive lock     dependencies ns_sem -> (shrinker) -> locks acquired in nilfs_evict_inode(). Since nilfs2 may acquire     ns_sem deep in the call stack holding other locks via its error handler __nilfs_error(), this causes     lockdep to report circular locking. This is a false positive and no circular locking actually occurs as no     inodes exist yet when nilfs_sysfs_create_device_group() is called. Fortunately, the lockdep warnings can     be resolved by simply moving the call to nilfs_sysfs_create_device_group() out of ns_sem. This fixes     these sysfs issues by revising where the device's sysfs interface is created/deleted and keeping its     lifetime within the lifetime of the metadata files above. (CVE-2023-53440)

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

The version of kernel installed on the remote host is prior to 4.14.313-235.533. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2023-2027 advisory.

    A use-after-free flaw was found in vhost_net_set_backend in drivers/vhost/net.c in virtio network     subcomponent in the Linux kernel due to a double fget. This flaw could allow a local attacker to crash the     system, and could even lead to a kernel information leak problem. (CVE-2023-1838)

    An insufficient permission check has been found in the Bluetooth subsystem ofthe Linux kernel when     handling ioctl system calls of HCI sockets. This causestasks without the proper CAP_NET_ADMIN capability     can easily mark HCI socketsas _trusted_. Trusted sockets are intended to enable the sending and     receivingof management commands and events, such as pairing or connecting with a newdevice.  As a result,     unprivileged users can acquire a trusted socket, leadingto unauthorized execution of management commands.
    The exploit requires onlythe presence of a set of commonly used setuid programs (e.g., su, sudo).
    (CVE-2023-2002)

    An out-of-bounds memory access flaw was found in the Linux kernel's XFS file system in how a user restores     an XFS image after failure (with a dirty log journal). This flaw allows a local user to crash or     potentially escalate their privileges on the system. (CVE-2023-2124)

    An out-of-bounds write vulnerability was found in the Linux kernel's SLIMpro I2C device driver. The     userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a     memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to     crash the system or potentially achieve code execution. (CVE-2023-2194)

    cbq_classify in net/sched/sch_cbq.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service (slab-out-of-bounds read) because of type confusion (non-negative numbers can sometimes     indicate a TC_ACT_SHOT condition rather than valid classification results). (CVE-2023-23454)

    The Linux kernel before 6.2.9 has a race condition and resultant use-after-free in     drivers/net/ethernet/qualcomm/emac/emac.c if a physically proximate attacker unplugs an emac based device.
    (CVE-2023-33203)

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

    nilfs2: fix kernel-infoleak in nilfs_ioctl_wrap_copy() (CVE-2023-53035)

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

    dm stats: check for and propagate alloc_percpu failure (CVE-2023-53044)

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

    dm crypt: add cond_resched() to dmcrypt_write() (CVE-2023-53051)

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

    igb: revert rtnl_lock() that causes deadlock (CVE-2023-53060)

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

    net: usb: smsc95xx: Limit packet length to skb->len (CVE-2023-53062)

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

    scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate() (CVE-2023-53078)

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

    ocfs2: fix data corruption after failed write (CVE-2023-53081)

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

    cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL (CVE-2023-53246)

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

    nilfs2: fix sysfs interface lifetime (CVE-2023-53440)

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

    nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread() (CVE-2023-53608)

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

    mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() (CVE-2023-53623)

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.

The version of kernel installed on the remote host is prior to 5.4.241-150.347. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2023-044 advisory.

    A vulnerability was found in the fs/inode.c:inode_init_owner() function logic of the LInux kernel that     allows local users to create files for the XFS file-system with an unintended group ownership and with     group execution and SGID permission bits set, in a scenario where a directory is SGID and belongs to a     certain group and is writable by a user who is not a member of this group. This can lead to excessive     permissions granted in case when they should not.  This vulnerability is similar to the previous     CVE-2018-13405 and adds the missed fix for the XFS. (CVE-2021-4037)

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

    tun: avoid double free in tun_free_netdev (CVE-2021-47082)

    A double-free flaw was found in the Linux kernel's TUN/TAP device driver functionality in how a user     registers the device when the register_netdevice function fails (NETDEV_REGISTER notifier). This flaw     allows a local user to crash or potentially escalate their privileges on the system. (CVE-2022-4744)

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

    gfs2: Always check inode size of inline inodes (CVE-2022-49739)

    A use-after-free flaw was found in qdisc_graft in net/sched/sch_api.c in the Linux Kernel due to a race     problem. This flaw leads to a denial of service issue. (CVE-2023-0590)

    An out-of-bounds memory access flaw was found in the Linux kernel's XFS file system in how a user restores     an XFS image after failure (with a dirty log journal). This flaw allows a local user to crash or     potentially escalate their privileges on the system. (CVE-2023-2124)

    An out-of-bounds write vulnerability was found in the Linux kernel's SLIMpro I2C device driver. The     userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a     memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to     crash the system or potentially achieve code execution. (CVE-2023-2194)

    do_tls_getsockopt in net/tls/tls_main.c in the Linux kernel through 6.2.6 lacks a lock_sock call, leading     to a race condition (with a resultant use-after-free or NULL pointer dereference). (CVE-2023-28466)

    The Linux kernel before 6.2.9 has a race condition and resultant use-after-free in     drivers/net/ethernet/qualcomm/emac/emac.c if a physically proximate attacker unplugs an emac based device.
    (CVE-2023-33203)

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

    nilfs2: fix kernel-infoleak in nilfs_ioctl_wrap_copy() (CVE-2023-53035)

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

    scsi: qla2xxx: Perform lockless command completion in abort path (CVE-2023-53041)

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

    dm stats: check for and propagate alloc_percpu failure (CVE-2023-53044)

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

    dm crypt: add cond_resched() to dmcrypt_write() (CVE-2023-53051)

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

    erspan: do not use skb_mac_header() in ndo_start_xmit() (CVE-2023-53053)

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

    igb: revert rtnl_lock() that causes deadlock (CVE-2023-53060)

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

    net: usb: smsc95xx: Limit packet length to skb->len (CVE-2023-53062)

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

    qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info (CVE-2023-53066)

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

    scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate() (CVE-2023-53078)

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

    ocfs2: fix data corruption after failed write (CVE-2023-53081)

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

    cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL (CVE-2023-53246)

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

    sctp: check send stream number after wait_for_sndbuf (CVE-2023-53296)

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

    can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write (CVE-2023-53344)

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

    sctp: fix a potential overflow in sctp_ifwdtsn_skip (CVE-2023-53372)

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

    tracing: Free error logs of tracing instances (CVE-2023-53375)

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

    nilfs2: fix sysfs interface lifetime (CVE-2023-53440)

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

    nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread() (CVE-2023-53608)

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

    mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() (CVE-2023-53623)

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.

The version of kernel installed on the remote host is prior to 5.10.178-162.673. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2023-031 advisory.

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

    sysctl: Fix data-races in proc_dou8vec_minmax(). (CVE-2022-49634)

    An out-of-bounds memory access flaw was found in the Linux kernel's XFS file system in how a user restores     an XFS image after failure (with a dirty log journal). This flaw allows a local user to crash or     potentially escalate their privileges on the system. (CVE-2023-2124)

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

    Drivers: vmbus: Check for channel allocation before looking up relids (CVE-2023-53273)

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

    sctp: check send stream number after wait_for_sndbuf (CVE-2023-53296)

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

    sctp: fix a potential overflow in sctp_ifwdtsn_skip (CVE-2023-53372)

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

    tracing: Free error logs of tracing instances (CVE-2023-53375)

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

    nilfs2: fix sysfs interface lifetime (CVE-2023-53440)

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

    scsi: iscsi_tcp: Check that sock is valid before iscsi_set_param() (CVE-2023-53464)

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

    RDMA/cma: Allow UD qp_type to join multicast only (CVE-2023-53525)

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

    nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread() (CVE-2023-53608)

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

    mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() (CVE-2023-53623)

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.

An update of the linux package has been released.

ID	Name	Product	Family	Severity
291260	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-004799)	Nessus	Unity Linux Local Security Checks	medium
281180	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-992997)	Nessus	Unity Linux Local Security Checks	medium
280380	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-992575)	Nessus	Unity Linux Local Security Checks	medium
280351	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-992393)	Nessus	Unity Linux Local Security Checks	medium
270857	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:03628-1)	Nessus	SuSE Local Security Checks	high
270837	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:03615-1)	Nessus	SuSE Local Security Checks	high
265907	Linux Distros Unpatched Vulnerability : CVE-2023-53440	Nessus	Misc.	medium
175018	Amazon Linux 2 : kernel, --advisory ALAS2-2023-2027 (ALAS-2023-2027)	Nessus	Amazon Linux Local Security Checks	high
174976	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2023-044 (ALASKERNEL-5.4-2023-044)	Nessus	Amazon Linux Local Security Checks	high
174973	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2023-031 (ALASKERNEL-5.10-2023-031)	Nessus	Amazon Linux Local Security Checks	high
153035	Photon OS 4.0: Linux PHSA-2021-4.0-0095	Nessus	PhotonOS Local Security Checks	high

Detections

Analytics

CVE-2023-53440

medium

Tenable Plugins

medium

medium

medium

medium

high

high

medium

high

high

high

high