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

  - VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host() Syzkaller hit 'WARNING in     dg_dispatch_as_host' bug. memcpy: detected field-spanning write (size 56) of single field &dg_info->msg     at drivers/misc/vmw_vmci/vmci_datagram.c:237 (size 24) WARNING: CPU: 0 PID: 1555 at     drivers/misc/vmw_vmci/vmci_datagram.c:237 dg_dispatch_as_host+0x88e/0xa60     drivers/misc/vmw_vmci/vmci_datagram.c:237 Some code commentry, based on my understanding: 544 #define     VMCI_DG_SIZE(_dg) (VMCI_DG_HEADERSIZE + (size_t)(_dg)->payload_size) /// This is 24 + payload_size     memcpy(&dg_info->msg, dg, dg_size); Destination = dg_info->msg ---> this is a 24 byte structure(struct     vmci_datagram) Source = dg --> this is a 24 byte structure (struct vmci_datagram) Size = dg_size = 24 +     payload_size {payload_size = 56-24 =32} -- Syzkaller managed to set payload_size to 32. 35 struct     delayed_datagram_info { 36 struct datagram_entry *entry; 37 struct work_struct work; 38 bool     in_dg_host_queue; 39 /* msg and msg_payload must be together. */ 40 struct vmci_datagram msg; 41 u8     msg_payload[]; 42 }; So those extra bytes of payload are copied into msg_payload[], a run time warning is     seen while fuzzing with Syzkaller. One possible way to fix the warning is to split the memcpy() into two     parts -- one -- direct assignment of msg and second taking care of payload. Gustavo quoted: Under     FORTIFY_SOURCE we should not copy data across multiple members in a structure. (CVE-2024-35944)

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

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

    VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host()

    Syzkaller hit 'WARNING in dg_dispatch_as_host' bug.

    memcpy: detected field-spanning write (size 56) of single field &dg_info->msg     at drivers/misc/vmw_vmci/vmci_datagram.c:237 (size 24)

    WARNING: CPU: 0 PID: 1555 at drivers/misc/vmw_vmci/vmci_datagram.c:237     dg_dispatch_as_host+0x88e/0xa60 drivers/misc/vmw_vmci/vmci_datagram.c:237

    Some code commentry, based on my understanding:

    544 #define VMCI_DG_SIZE(_dg) (VMCI_DG_HEADERSIZE + (size_t)(_dg)->payload_size)     /// This is 24 + payload_size

    memcpy(&dg_info->msg, dg, dg_size);
            Destination = dg_info->msg ---> this is a 24 byte                                             structure(struct vmci_datagram)             Source = dg --> this is a 24 byte structure (struct vmci_datagram)             Size = dg_size = 24 + payload_size

    {payload_size = 56-24 =32} -- Syzkaller managed to set payload_size to 32.

     35 struct delayed_datagram_info {      36         struct datagram_entry *entry;
     37         struct work_struct work;
     38         bool in_dg_host_queue;
     39         /* msg and msg_payload must be together. */      40         struct vmci_datagram msg;
     41         u8 msg_payload[];
     42 };

    So those extra bytes of payload are copied into msg_payload[], a run time     warning is seen while fuzzing with Syzkaller.

    One possible way to fix the warning is to split the memcpy() into     two parts -- one -- direct assignment of msg and second taking care of payload.

    Gustavo quoted:
    Under FORTIFY_SOURCE we should not copy data across multiple members     in a structure.

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 Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2025:4342 advisory.

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

    Security Fix(es):

    * kernel: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg (CVE-2023-52528)

    * kernel: RDMA/qedr: Fix qedr_create_user_qp error flow (CVE-2024-26743)

    * kernel: mlxsw: spectrum_acl_tcam: Fix memory leak during rehash (CVE-2024-35853)

    * kernel: VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host() (CVE-2024-35944)

    * kernel: dma-direct: Leak pages on dma_set_decrypted() failure (CVE-2024-35939)

    * kernel: i40e: Do not use WQ_MEM_RECLAIM flag for workqueue (CVE-2024-36004)

    * kernel: can: dev: can_put_echo_skb(): don't crash kernel if can_priv::echo_skb is accessed out of     bounds (CVE-2023-52878)

    * kernel: drm/amdgpu/mes: fix use-after-free issue (CVE-2024-38581)

    * kernel: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (CVE-2024-42070)

    * kernel: wifi: cfg80211: restrict NL80211_ATTR_TXQ_QUANTUM values (CVE-2024-42114)

    * kernel: dev/parport: fix the array out-of-bounds risk (CVE-2024-42301)

    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.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 MiracleLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2024-9035:37 advisory.

    CVE-2023-6040 CVE-2024-26595 CVE-2024-26600 CVE-2021-46984 CVE-2023-52478     CVE-2023-52476 CVE-2023-52522 CVE-2021-47101 CVE-2021-47097 CVE-2023-52605     CVE-2024-26638 CVE-2024-26645 CVE-2024-26665 CVE-2024-26720 CVE-2024-26717     CVE-2024-26769 CVE-2024-26846 CVE-2024-26894 CVE-2024-26880 CVE-2024-26855     CVE-2024-26923 CVE-2024-26939 CVE-2024-27013 CVE-2024-27042 CVE-2024-35809     CVE-2023-52683 CVE-2024-35884 CVE-2024-35877 CVE-2024-35944 CVE-2024-35989     CVE-2021-47412 CVE-2021-47393 CVE-2021-47386 CVE-2021-47385 CVE-2021-47384     CVE-2021-47383 CVE-2021-47432 CVE-2021-47352 CVE-2021-47338 CVE-2021-47321     CVE-2021-47289 CVE-2021-47287 CVE-2023-52798 CVE-2023-52809 CVE-2023-52817     CVE-2023-52840 CVE-2023-52800 CVE-2021-47441 CVE-2021-47466 CVE-2021-47455     CVE-2021-47497 CVE-2021-47560 CVE-2021-47527 CVE-2024-36883 CVE-2024-36922     CVE-2024-36920 CVE-2024-36902 CVE-2024-36953 CVE-2024-36939 CVE-2024-36919     CVE-2024-36901 CVE-2021-47582 CVE-2021-47609 CVE-2024-38619 CVE-2022-48754     CVE-2022-48760 CVE-2024-38581 CVE-2024-38579 CVE-2024-38570 CVE-2024-38559     CVE-2024-38558 CVE-2024-37356 CVE-2024-39471 CVE-2024-39499 CVE-2024-39501     CVE-2024-39506 CVE-2024-40904 CVE-2024-40911 CVE-2024-40912 CVE-2024-40929     CVE-2024-40931 CVE-2024-40941 CVE-2024-40954 CVE-2024-40958 CVE-2024-40959     CVE-2024-40960 CVE-2024-40972 CVE-2024-40977 CVE-2024-40978 CVE-2024-40988     CVE-2024-40989 CVE-2024-40995 CVE-2024-40997 CVE-2024-40998 CVE-2024-41005     CVE-2024-40901 CVE-2024-41007 CVE-2024-41008 CVE-2022-48804 CVE-2022-48836     CVE-2022-48866 CVE-2024-41090 CVE-2024-41091 CVE-2024-41012 CVE-2024-41013     CVE-2024-41014 CVE-2024-41023 CVE-2024-41035 CVE-2024-41038 CVE-2024-41039     CVE-2024-41040 CVE-2024-41041 CVE-2024-41044 CVE-2024-41055 CVE-2024-41056     CVE-2024-41060 CVE-2024-41064 CVE-2024-41065 CVE-2024-41071 CVE-2024-41076     CVE-2024-41097 CVE-2024-42084 CVE-2024-42090 CVE-2024-42094 CVE-2024-42096     CVE-2024-42114 CVE-2024-42124 CVE-2024-42131 CVE-2024-42152 CVE-2024-42154     CVE-2024-42225 CVE-2024-42226 CVE-2024-42228 CVE-2024-42237 CVE-2024-42238     CVE-2024-42240 CVE-2024-42246 CVE-2024-42322 CVE-2024-43830 CVE-2024-43871

Tenable has extracted the preceding description block directly from the MiracleLinux 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	Published	Updated	Severity
228710	Linux Distros Unpatched Vulnerability : CVE-2024-35944	Nessus	Misc.	3/5/2025	7/17/2026	medium
308685	Unity Linux 20.1050e / 20.1070e Security Update: kernel (UTSA-2026-010798)	Nessus	Unity Linux Local Security Checks	4/21/2026	4/22/2026	medium
235004	RHEL 9 : kernel (RHSA-2025:4342)	Nessus	Red Hat Local Security Checks	4/30/2025	6/5/2025	high
239541	TencentOS Server 2: kernel (TSSA-2024:1029)	Nessus	Tencent Local Security Checks	6/16/2025	11/20/2025	high
292346	MiracleLinux 8 : kernel-4.18.0-553.22.1.el8_10 (AXSA:2024-9035:37)	Nessus	Miracle Linux Local Security Checks	1/20/2026	3/24/2026	high

Detections

Analytics

Plugins Search

medium

medium

high

high

high