In the Linux kernel, the following vulnerability has been resolved: dm: fix a race condition in retrieve_deps There's a race condition in the multipath target when retrieve_deps races with multipath_message calling dm_get_device and dm_put_device. retrieve_deps walks the list of open devices without holding any lock but multipath may add or remove devices to the list while it is running. The end result may be memory corruption or use-after-free memory access. See this description of a UAF with multipath_message(): https://listman.redhat.com/archives/dm-devel/2022-October/052373.html Fix this bug by introducing a new rw semaphore "devices_lock". We grab devices_lock for read in retrieve_deps and we grab it for write in dm_get_device and dm_put_device.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In the Linux kernel, the following vulnerability has been resolved: dm: fix a race condition in
    retrieve_deps There's a race condition in the multipath target when retrieve_deps races with
    multipath_message calling dm_get_device and dm_put_device. retrieve_deps walks the list of open devices
    without holding any lock but multipath may add or remove devices to the list while it is running. The end
    result may be memory corruption or use-after-free memory access. See this description of a UAF with
    multipath_message(): https://listman.redhat.com/archives/dm-devel/2022-October/052373.html Fix this bug by
    introducing a new rw semaphore "devices_lock". We grab devices_lock for read in retrieve_deps and we grab
    it for write in dm_get_device and dm_put_device. (CVE-2023-54324)

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

  - In the Linux kernel, the following vulnerability has been resolved: extcon: Modify extcon device to be     created after driver data is set Currently, someone can invoke the sysfs such as state_show()     intermittently before dev_set_drvdata() is done. And it can be a cause of kernel Oops because of edev is     Null at that time. So modified the driver registration to after setting drviver data. - Oops's backtrace.
    Backtrace: [<c067865c>] (state_show) from [<c05222e8>] (dev_attr_show) [<c05222c0>] (dev_attr_show) from     [<c02c66e0>] (sysfs_kf_seq_show) [<c02c6648>] (sysfs_kf_seq_show) from [<c02c496c>] (kernfs_seq_show)     [<c02c4938>] (kernfs_seq_show) from [<c025e2a0>] (seq_read) [<c025e11c>] (seq_read) from [<c02c50a0>]     (kernfs_fop_read) [<c02c5064>] (kernfs_fop_read) from [<c0231cac>] (__vfs_read) [<c0231c5c>] (__vfs_read)     from [<c0231ee0>] (vfs_read) [<c0231e34>] (vfs_read) from [<c0232464>] (ksys_read) [<c02323f0>]     (ksys_read) from [<c02324fc>] (sys_read) [<c02324e4>] (sys_read) from [<c00091d0>] (__sys_trace_return)     (CVE-2022-49308)

  - In the Linux kernel, the following vulnerability has been resolved: tick/nohz: unexport __init-annotated     tick_nohz_full_setup() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is     freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a     freed symbol may end up with kernel panic. modpost used to detect it, but it had been broken for a decade.
    Commit 28438794aba4 (modpost: fix section mismatch check for exported init/exit sections) fixed it so     modpost started to warn it again, then this showed up: MODPOST vmlinux.symvers WARNING: modpost:
    vmlinux.o(___ksymtab_gpl+tick_nohz_full_setup+0x0): Section mismatch in reference from the variable
    __ksymtab_tick_nohz_full_setup to the function .init.text:tick_nohz_full_setup() The symbol     tick_nohz_full_setup is exported and annotated __init Fix this by removing the __init annotation of     tick_nohz_full_setup or drop the export. Drop the export because tick_nohz_full_setup() is only called     from the built-in code in kernel/sched/isolation.c. (CVE-2022-49675)

  - In the Linux kernel, the following vulnerability has been resolved: ata: libata-core: fix NULL pointer     deref in ata_host_alloc_pinfo() In an unlikely (and probably wrong?) case that the 'ppi' parameter of     ata_host_alloc_pinfo() points to an array starting with a NULL pointer, there's going to be a kernel oops     as the 'pi' local variable won't get reassigned from the initial value of NULL. Initialize 'pi' instead to     '&ata_dummy_port_info' to fix the possible kernel oops for good... Found by Linux Verification Center     (linuxtesting.org) with the SVACE static analysis tool. (CVE-2022-49731)

  - In the Linux kernel, the following vulnerability has been resolved: bridge: switchdev: Fix memory leaks     when changing VLAN protocol The bridge driver can offload VLANs to the underlying hardware either via     switchdev or the 8021q driver. When the former is used, the VLAN is marked in the bridge driver with the     'BR_VLFLAG_ADDED_BY_SWITCHDEV' private flag. To avoid the memory leaks mentioned in the cited commit, the     bridge driver will try to delete a VLAN via the 8021q driver if the VLAN is not marked with the previously     mentioned flag. When the VLAN protocol of the bridge changes, switchdev drivers are notified via the     'SWITCHDEV_ATTR_ID_BRIDGE_VLAN_PROTOCOL' attribute, but the 8021q driver is also called to add the     existing VLANs with the new protocol and delete them with the old protocol. In case the VLANs were     offloaded via switchdev, the above behavior is both redundant and buggy. Redundant because the VLANs are     already programmed in hardware and drivers that support VLAN protocol change (currently only mlx5) change     the protocol upon the switchdev attribute notification. Buggy because the 8021q driver is called despite     these VLANs being marked with 'BR_VLFLAG_ADDED_BY_SWITCHDEV'. This leads to memory leaks [1] when the     VLANs are deleted. Fix by not calling the 8021q driver for VLANs that were already programmed via     switchdev. [1] unreferenced object 0xffff8881f6771200 (size 256): comm ip, pid 446855, jiffies     4298238841 (age 55.240s) hex dump (first 32 bytes): 00 00 7f 0e 83 88 ff ff 00 00 00 00 00 00 00 00     ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace:
    [<00000000012819ac>] vlan_vid_add+0x437/0x750 [<00000000f2281fad>] __br_vlan_set_proto+0x289/0x920     [<000000000632b56f>] br_changelink+0x3d6/0x13f0 [<0000000089d25f04>] __rtnl_newlink+0x8ae/0x14c0     [<00000000f6276baf>] rtnl_newlink+0x5f/0x90 [<00000000746dc902>] rtnetlink_rcv_msg+0x336/0xa00     [<000000001c2241c0>] netlink_rcv_skb+0x11d/0x340 [<0000000010588814>] netlink_unicast+0x438/0x710     [<00000000e1a4cd5c>] netlink_sendmsg+0x788/0xc40 [<00000000e8992d4e>] sock_sendmsg+0xb0/0xe0     [<00000000621b8f91>] ____sys_sendmsg+0x4ff/0x6d0 [<000000000ea26996>] ___sys_sendmsg+0x12e/0x1b0     [<00000000684f7e25>] __sys_sendmsg+0xab/0x130 [<000000004538b104>] do_syscall_64+0x3d/0x90     [<0000000091ed9678>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 (CVE-2022-49812)

  - In the Linux kernel, the following vulnerability has been resolved: capabilities: fix potential memleak on     error path from vfs_getxattr_alloc() In cap_inode_getsecurity(), we will use vfs_getxattr_alloc() to     complete the memory allocation of tmpbuf, if we have completed the memory allocation of tmpbuf, but failed     to call handler->get(...), there will be a memleak in below logic: |-- ret =     (int)vfs_getxattr_alloc(mnt_userns, ...) | /* ^^^ alloc for tmpbuf */ |-- value = krealloc(*xattr_value,     error + 1, flags) | /* ^^^ alloc memory */ |-- error = handler->get(handler, ...) | /* error! */ |--
    *xattr_value = value | /* xattr_value is &tmpbuf (memory leak!) */ So we will try to free(tmpbuf) after     vfs_getxattr_alloc() fails to fix it. [PM: subject line and backtrace tweaks] (CVE-2022-49890)

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

The Rocky Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ crxsa-2024_3138 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes     linked from the References section.

    This advisory is provided by Ctrl IQ, Inc for Rocky Linux systems. For more information about CIQ security     practices, visit https://ciq.com/security.

Tenable has extracted the preceding description block directly from the CIQ 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.

  - dm: fix a race condition in retrieve_deps There's a race condition in the multipath target when     retrieve_deps races with multipath_message calling dm_get_device and dm_put_device. retrieve_deps walks     the list of open devices without holding any lock but multipath may add or remove devices to the list     while it is running. The end result may be memory corruption or use-after-free memory access. See this     description of a UAF with multipath_message(): https://listman.redhat.com/archives/dm-     devel/2022-October/052373.html Fix this bug by introducing a new rw semaphore devices_lock. We grab     devices_lock for read in retrieve_deps and we grab it for write in dm_get_device and dm_put_device.
    (CVE-2023-54324)

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

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

    ceph: drop messages from MDS when unmounting (CVE-2022-48628)

    A use-after-free vulnerability in the Linux kernel's netfilter: nf_tables component can be exploited to     achieve local privilege escalation.

    Due to a race condition between nf_tables netlink control plane transaction and nft_set element garbage     collection, it is possible to underflow the reference counter causing a use-after-free vulnerability.

    We recommend upgrading past commit 3e91b0ebd994635df2346353322ac51ce84ce6d8. (CVE-2023-4244)

    A NULL pointer dereference flaw was found in the Linux kernel ipv4 stack. The socket buffer (skb) was     assumed to be associated with a device before calling __ip_options_compile, which is not always the case     if the skb is re-routed by ipvs. This issue may allow a local user with CAP_NET_ADMIN privileges to crash     the system. (CVE-2023-42754)

    A flaw was found in the Netfilter subsystem of the Linux kernel. A race condition between IPSET_CMD_ADD     and IPSET_CMD_SWAP can lead to a kernel panic due to the invocation of `__ip_set_put` on a wrong `set`.
    This issue may allow a local user to crash the system. (CVE-2023-42756)

    A use-after-free vulnerability in the Linux kernel's netfilter: nf_tables component can be exploited to     achieve local privilege escalation.

    Addition and removal of rules from chain bindings within the same transaction causes leads to use-after-     free.

    We recommend upgrading past commit f15f29fd4779be8a418b66e9d52979bb6d6c2325. (CVE-2023-5197)

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

    netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction

    New elements in this transaction might expired before such transactionends. Skip sync GC for such elements     otherwise commit path might walkover an already released object. Once transaction is finished, async     GCwill collect such expired element. (CVE-2023-52433)

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

    x86/srso: Add SRSO mitigation for Hygon processors (CVE-2023-52482)

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

    ring-buffer: Do not attempt to read past commit (CVE-2023-52501)

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

    mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() (CVE-2023-52562)

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

    serial: 8250_port: Check IRQ data before use (CVE-2023-52567)

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

    btrfs: remove BUG() after failure to insert delayed dir index item (CVE-2023-52569)

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

    cifs: Fix UAF in cifs_demultiplex_thread() (CVE-2023-52572)

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

    net: rds: Fix possible NULL-pointer dereference (CVE-2023-52573)

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

    team: fix null-ptr-deref when team device type is changed (CVE-2023-52574)

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

    x86/mm, kexec, ima: Use memblock_free_late() from ima_free_kexec_buffer() (CVE-2023-52576)

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

    net: bridge: use DEV_STATS_INC() (CVE-2023-52578)

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

    net/core: Fix ETH_P_1588 flow dissector (CVE-2023-52580)

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

    netfs: Only call folio_start_fscache() one time for each folio (CVE-2023-52582)

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

    netfilter: nf_tables: adapt set backend to use GC transaction API (CVE-2023-52923)

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

    netfilter: nf_tables: don't skip expired elements during walk (CVE-2023-52924)

    A use-after-free vulnerability in the Linux kernel's fs/smb/client component can be exploited to achieve     local privilege escalation.

    In case of an error in smb3_fs_context_parse_param, ctx->password was freed but the field was not set to     NULL which could lead to double free.

    We recommend upgrading past commit e6e43b8aa7cd3c3af686caf0c2e11819a886d705. (CVE-2023-5345)

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

    dm: fix a race condition in retrieve_deps (CVE-2023-54324)

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
451506	Google: sys-kernel/lakitu-kernel-6_1: security update to 18026.0.0	Tenable Cloud Security	Google COS Security Checks	Local	medium
451506	Google: sys-kernel/lakitu-kernel-6_1: security update to 18026.0.0	Tenable Self-Hosted Container Security	Google COS Security Checks	Local	medium
360687	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783362244)	Nessus	Alma Linux Local Security Checks	Local	high
353813	Rocky Linux 8 [CIQ] Security Update: bpftool / bpftool-debuginfo / kernel / kernel-abi-stablelists / etc Multiple Vulnerabilities (crxsa-2024_3138)	Nessus	Rocky Linux Local Security Checks	Local	critical
319448	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2026-2132)	Nessus	Huawei Local Security Checks	Local	high
319325	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2026-2171)	Nessus	Huawei Local Security Checks	Local	high
301628	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1280)	Nessus	Huawei Local Security Checks	Local	high
301595	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1244)	Nessus	Huawei Local Security Checks	Local	high
297194	SUSE SLED15 / SLES15 : Security update for the Linux Kernel (SUSE-SU-2026:0315-1)	Nessus	SuSE Local Security Checks	Local	high
296680	SUSE SLES15 / openSUSE 15 : Security update for the Linux Kernel (SUSE-SU-2026:0293-1)	Nessus	SuSE Local Security Checks	Local	high
296676	SUSE SLES15: kernel-azure / kernel-azure-devel / kernel-devel-azure / etc (SUSE-SU-2026:0281-1)	Nessus	SuSE Local Security Checks	Local	high
296481	SUSE SLES15 Security Update : kernel (SUSE-SU-2026:0278-1)	Nessus	SuSE Local Security Checks	Local	high
280695	Linux Distros Unpatched Vulnerability : CVE-2023-54324	Nessus	Misc.	Local	high
183798	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2023-385)	Nessus	Amazon Linux Local Security Checks	Local	high

Detections

Analytics

CVE-2023-54324

medium

Tenable Plugins

medium

medium

high

critical

high

high

high

high

high

high

high

high

high

high