The remote Ubuntu 21.10 host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-5009-2 advisory.

    USN-5009-1 fixed vulnerabilities in libslirp. This update provides the corresponding updates for Ubuntu     21.10.



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

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the bootp_input() function and could occur while processing a udp packet that is smaller than     the size of the 'bootp_t' structure. A malicious guest could use this flaw to leak 10 bytes of     uninitialized heap memory from the host. The highest threat from this vulnerability is to data     confidentiality. This flaw affects libslirp versions prior to 4.6.0. (CVE-2021-3592)

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

The remote AlmaLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2021:4191 advisory.

    * QEMU: net: e1000e: use-after-free while sending packets (CVE-2020-15859)

    * QEMU: slirp: invalid pointer initialization may lead to information disclosure (bootp) (CVE-2021-3592)

    * QEMU: slirp: invalid pointer initialization may lead to information disclosure (udp6) (CVE-2021-3593)

    * QEMU: slirp: invalid pointer initialization may lead to information disclosure (udp) (CVE-2021-3594)

    * QEMU: slirp: invalid pointer initialization may lead to information disclosure (tftp) (CVE-2021-3595)

    * libvirt: Insecure sVirt label generation (CVE-2021-3631)

    * libvirt: Improper locking on ACL failure in virStoragePoolLookupByTargetPath API (CVE-2021-3667)

Tenable has extracted the preceding description block directly from the AlmaLinux 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 SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2563-1 advisory.

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the bootp_input() function and could occur while processing a udp packet that is smaller than     the size of the 'bootp_t' structure. A malicious guest could use this flaw to leak 10 bytes of     uninitialized heap memory from the host. The highest threat from this vulnerability is to data     confidentiality. This flaw affects libslirp versions prior to 4.6.0. (CVE-2021-3592)

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the udp6_input() function and could occur while processing a udp packet that is smaller than the     size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0. (CVE-2021-3593)

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the udp_input() function and could occur while processing a udp packet that is smaller than the     size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0. (CVE-2021-3594)

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the tftp_input() function and could occur while processing a udp packet that is smaller than the     size of the 'tftp_t' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0. (CVE-2021-3595)

  - A stack overflow vulnerability was found in the Intel HD Audio device (intel-hda) of QEMU. A malicious     guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service     condition. The highest threat from this vulnerability is to system availability. This flaw affects QEMU     versions prior to 7.0.0. (CVE-2021-3611)

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 SUSE15 host has a package installed that is affected by multiple vulnerabilities as referenced in the openSUSE-SU-2021:2474-1 advisory.

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the bootp_input() function and could occur while processing a udp packet that is smaller than     the size of the 'bootp_t' structure. A malicious guest could use this flaw to leak 10 bytes of     uninitialized heap memory from the host. The highest threat from this vulnerability is to data     confidentiality. This flaw affects libslirp versions prior to 4.6.0. (CVE-2021-3592)

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the udp6_input() function and could occur while processing a udp packet that is smaller than the     size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0. (CVE-2021-3593)

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the udp_input() function and could occur while processing a udp packet that is smaller than the     size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0. (CVE-2021-3594)

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the tftp_input() function and could occur while processing a udp packet that is smaller than the     size of the 'tftp_t' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0. (CVE-2021-3595)

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 SLES11 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:14848-1 advisory.

  - Observable response discrepancy in some Intel(R) Processors may allow an authorized user to potentially     enable information disclosure via local access. (CVE-2021-0089)

  - A stack overflow via an infinite recursion vulnerability was found in the eepro100 i8255x device emulator     of QEMU. This issue occurs while processing controller commands due to a DMA reentry issue. This flaw     allows a guest user or process to consume CPU cycles or crash the QEMU process on the host, resulting in a     denial of service. The highest threat from this vulnerability is to system availability. (CVE-2021-20255)

  - x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort     speculative security vulnerability. Please see https://xenbits.xen.org/xsa/advisory-305.html for details.
    Mitigating TAA by disabling TSX (the default and preferred option) requires selecting a non-default     setting in MSR_TSX_CTRL. This setting isn't restored after S3 suspend. (CVE-2021-28690)

  - inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel     with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous     notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the     completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to     fail overly-slow commands. The course of action upon a perceived timeout actually being detected is     inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as     crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue     as if the IOMMU operation succeeded. (CVE-2021-28692)

  - grant table v2 status pages may remain accessible after de-allocation Guest get permitted access to     certain Xen-owned pages of memory. The majority of such pages remain allocated / associated with a guest     for its entire lifetime. Grant table v2 status pages, however, get de-allocated when a guest switched     (back) from v2 to v1. The freeing of such pages requires that the hypervisor know where in the guest these     pages were mapped. The hypervisor tracks only one use within guest space, but racing requests from the     guest to insert mappings of these pages may result in any of them to become mapped in multiple locations.
    Upon switching back from v2 to v1, the guest would then retain access to a page that was freed and perhaps     re-used for other purposes. (CVE-2021-28697)

  - long running loops in grant table handling In order to properly monitor resource use, Xen maintains     information on the grant mappings a domain may create to map grants offered by other domains. In the     process of carrying out certain actions, Xen would iterate over all such entries, including ones which     aren't in use anymore and some which may have been created but never used. If the number of entries for a     given domain is large enough, this iterating of the entire table may tie up a CPU for too long, starving     other domains or causing issues in the hypervisor itself. Note that a domain may map its own grants, i.e.
    there is no need for multiple domains to be involved here. A pair of cooperating guests may, however,     cause the effects to be more severe. (CVE-2021-28698)

  - Another race in XENMAPSPACE_grant_table handling Guests are permitted access to certain Xen-owned pages of     memory. The majority of such pages remain allocated / associated with a guest for its entire lifetime.
    Grant table v2 status pages, however, are de-allocated when a guest switches (back) from v2 to v1. Freeing     such pages requires that the hypervisor enforce that no parallel request can result in the addition of a     mapping of such a page to a guest. That enforcement was missing, allowing guests to retain access to pages     that were freed and perhaps re-used for other purposes. Unfortunately, when XSA-379 was being prepared,     this similar issue was not noticed. (CVE-2021-28701)

  - grant table v2 status pages may remain accessible after de-allocation (take two) Guest get permitted     access to certain Xen-owned pages of memory. The majority of such pages remain allocated / associated with     a guest for its entire lifetime. Grant table v2 status pages, however, get de-allocated when a guest     switched (back) from v2 to v1. The freeing of such pages requires that the hypervisor know where in the     guest these pages were mapped. The hypervisor tracks only one use within guest space, but racing requests     from the guest to insert mappings of these pages may result in any of them to become mapped in multiple     locations. Upon switching back from v2 to v1, the guest would then retain access to a page that was freed     and perhaps re-used for other purposes. This bug was fortuitously fixed by code cleanup in Xen 4.14, and     backported to security-supported Xen branches as a prerequisite of the fix for XSA-378. (CVE-2021-28703)

  - issues with partially successful P2M updates on x86 T[his CNA information record relates to multiple CVEs;
    the text explains which aspects/vulnerabilities correspond to which CVE.] x86 HVM and PVH guests may be     started in populate-on-demand (PoD) mode, to provide a way for them to later easily have more memory     assigned. Guests are permitted to control certain P2M aspects of individual pages via hypercalls. These     hypercalls may act on ranges of pages specified via page orders (resulting in a power-of-2 number of     pages). In some cases the hypervisor carries out the requests by splitting them into smaller chunks. Error     handling in certain PoD cases has been insufficient in that in particular partial success of some     operations was not properly accounted for. There are two code paths affected - page removal     (CVE-2021-28705) and insertion of new pages (CVE-2021-28709). (We provide one patch which combines the fix     to both issues.) (CVE-2021-28705, CVE-2021-28709)

  - guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of     memory, it may be able to issue hypercalls to increase its memory allocation beyond the administrator     established limit. This is a result of a calculation done with 32-bit precision, which may overflow. It     would then only be the overflowed (and hence small) number which gets compared against the established     upper bound. (CVE-2021-28706)

  - A flaw was found in the USB redirector device (usb-redir) of QEMU. Small USB packets are combined into a     single, large transfer request, to reduce the overhead and improve performance. The combined size of the     bulk transfer is used to dynamically allocate a variable length array (VLA) on the stack without proper     validation. Since the total size is not bounded, a malicious guest could use this flaw to influence the     array length and cause the QEMU process to perform an excessive allocation on the stack, resulting in a     denial of service. (CVE-2021-3527)

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the bootp_input() function and could occur while processing a udp packet that is smaller than     the size of the 'bootp_t' structure. A malicious guest could use this flaw to leak 10 bytes of     uninitialized heap memory from the host. The highest threat from this vulnerability is to data     confidentiality. This flaw affects libslirp versions prior to 4.6.0. (CVE-2021-3592)

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the udp_input() function and could occur while processing a udp packet that is smaller than the     size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0. (CVE-2021-3594)

  - An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the tftp_input() function and could occur while processing a udp packet that is smaller than the     size of the 'tftp_t' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0. (CVE-2021-3595)

  - A flaw was found in the USB redirector device emulation of QEMU in versions prior to 6.1.0-rc2. It occurs     when dropping packets during a bulk transfer from a SPICE client due to the packet queue being full. A     malicious SPICE client could use this flaw to make QEMU call free() with faked heap chunk metadata,     resulting in a crash of QEMU or potential code execution with the privileges of the QEMU process on the     host. (CVE-2021-3682)

  - An off-by-one error was found in the SCSI device emulation in QEMU. It could occur while processing MODE     SELECT commands in mode_sense_page() if the 'page' argument was set to MODE_PAGE_ALLS (0x3f). A malicious     guest could use this flaw to potentially crash QEMU, resulting in a denial of service condition.
    (CVE-2021-3930)

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

The remote Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS / 24.10 host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-7094-1 advisory.

    It was discovered that QEMU incorrectly handled memory during certain VNC operations. A remote attacker     could possibly use this issue to cause QEMU to consume resources, resulting in a denial of service. This     issue only affected Ubuntu 14.04 LTS. (CVE-2019-20382)

    It was discovered that QEMU incorrectly handled certain memory copy operations when loading ROM contents.
    If a user were tricked into running an untrusted kernel image, a remote attacker could possibly use this     issue to run arbitrary code. This issue only affected Ubuntu 14.04 LTS. (CVE-2020-13765)

    Aviv Sasson discovered that QEMU incorrectly handled Slirp networking. A remote attacker could use this     issue to cause QEMU to crash, resulting in a denial of service, or possibly execute arbitrary code. This     issue only affected Ubuntu 14.04 LTS. (CVE-2020-1983)

    It was discovered that the SLiRP networking implementation of the QEMU emulator did not properly manage     memory under certain circumstances. An attacker could use this to cause a heap-based buffer overflow or     other out- of-bounds access, which can lead to a denial of service (application crash) or potential     execute arbitrary code. This issue only affected Ubuntu 14.04 LTS. (CVE-2020-7039)

    It was discovered that the SLiRP networking implementation of the QEMU emulator misuses snprintf return     values. An attacker could use this to cause a denial of service (application crash) or potentially execute     arbitrary code. This issue only affected Ubuntu 14.04 LTS. (CVE-2020-8608)

    It was discovered that QEMU SLiRP networking incorrectly handled certain udp packets. An attacker inside a     guest could possibly use this issue to leak sensitive information from the host. This issue only affected     Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2021-3592, CVE-2021-3594)

    It was discovered that QEMU had a DMA reentrancy issue, leading to a use-after-free vulnerability. An     attacker could possibly use this issue to cause a denial of service. This issue only affected Ubuntu 18.04     LTS, Ubuntu 20.04 LTS and Ubuntu 22.04 LTS. (CVE-2023-3019)

    It was discovered that QEMU had a flaw in Virtio PCI Bindings, leading to a triggerable crash via     vhost_net_stop. An attacker inside a guest could possibly use this issue to cause a denial of service.
    This issue only affected Ubuntu 24.04 LTS and Ubuntu 24.10. (CVE-2024-4693)

    It was discovered that QEMU incorrectly handled memory in virtio-sound, leading to a heap-based buffer     overflow. An attacker could possibly use this issue to cause a denial of service or execute arbitrary     code. This issue only affected Ubuntu 24.04 LTS and Ubuntu 24.10. (CVE-2024-7730)

Tenable has extracted the preceding description block directly from the Ubuntu 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 Ubuntu 18.04 LTS / 20.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-5010-1 advisory.

    Lei Sun discovered that QEMU incorrectly handled certain MMIO operations. An attacker inside the guest     could possibly use this issue to cause QEMU to crash, resulting in a denial of service. (CVE-2020-15469)

    Wenxiang Qian discovered that QEMU incorrectly handled certain ATAPI commands. An attacker inside the     guest could possibly use this issue to cause QEMU to crash, resulting in a denial of service. This issue     only affected Ubuntu 21.04. (CVE-2020-29443)

    Cheolwoo Myung discovered that QEMU incorrectly handled SCSI device emulation. An attacker inside the     guest could possibly use this issue to cause QEMU to crash, resulting in a denial of service.
    (CVE-2020-35504, CVE-2020-35505, CVE-2021-3392)

    Alex Xu discovered that QEMU incorrectly handled the virtio-fs shared file system daemon. An attacker     inside the guest could possibly use this issue to read and write to host devices. This issue only affected     Ubuntu 20.10. (CVE-2020-35517)

    It was discovered that QEMU incorrectly handled ARM Generic Interrupt Controller emulation. An attacker     inside the guest could possibly use this issue to cause QEMU to crash, resulting in a denial of service.
    This issue only affected Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 20.10. (CVE-2021-20221)

    Alexander Bulekov, Cheolwoo Myung, Sergej Schumilo, Cornelius Aschermann, and Simon Werner discovered that     QEMU incorrectly handled e1000 device emulation. An attacker inside the guest could possibly use this     issue to cause QEMU to hang, resulting in a denial of service. This issue only affected Ubuntu 18.04 LTS,     Ubuntu 20.04 LTS, and Ubuntu 20.10. (CVE-2021-20257)

    It was discovered that QEMU incorrectly handled SDHCI controller emulation. An attacker inside the guest     could use this issue to cause QEMU to crash, resulting in a denial of service, or possibly execute     arbitrary code. In the default installation, when QEMU is used in combination with libvirt, attackers     would be isolated by the libvirt AppArmor profile. (CVE-2021-3409)

    It was discovered that QEMU incorrectly handled certain NIC emulation devices. An attacker inside the     guest could possibly use this issue to cause QEMU to hang or crash, resulting in a denial of service. This     issue only affected Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 20.10. (CVE-2021-3416)

    Remy Noel discovered that QEMU incorrectly handled the USB redirector device. An attacker inside the guest     could possibly use this issue to cause QEMU to consume resources, resulting in a denial of service.
    (CVE-2021-3527)

    It was discovered that QEMU incorrectly handled the virtio vhost-user GPU device. An attacker inside the     guest could possibly use this issue to cause QEMU to consume resources, leading to a denial of service.
    This issue only affected Ubuntu 20.04 LTS, Ubuntu 20.10, and Ubuntu 21.04. (CVE-2021-3544)

    It was discovered that QEMU incorrectly handled the virtio vhost-user GPU device. An attacker inside the     guest could possibly use this issue to obtain sensitive host information. This issue only affected Ubuntu     20.04 LTS, Ubuntu 20.10, and Ubuntu 21.04. (CVE-2021-3545)

    It was discovered that QEMU incorrectly handled the virtio vhost-user GPU device. An attacker inside the     guest could use this issue to cause QEMU to crash, resulting in a denial of service, or possibly execute     arbitrary code. In the default installation, when QEMU is used in combination with libvirt, attackers     would be isolated by the libvirt AppArmor profile. This issue only affected Ubuntu 20.04 LTS, Ubuntu     20.10, and Ubuntu 21.04. (CVE-2021-3546)

    It was discovered that QEMU incorrectly handled the PVRDMA device. An attacker inside the guest could use     this issue to cause QEMU to crash, resulting in a denial of service, or possibly execute arbitrary code.
    In the default installation, when QEMU is used in combination with libvirt, attackers would be isolated by     the libvirt AppArmor profile. This issue only affected Ubuntu 20.04 LTS, Ubuntu 20.10, and Ubuntu 21.04.
    (CVE-2021-3582, CVE-2021-3607, CVE-2021-3608)

    It was discovered that QEMU SLiRP networking incorrectly handled certain udp packets. An attacker inside a     guest could possibly use this issue to leak sensitive information from the host. (CVE-2021-3592,     CVE-2021-3593, CVE-2021-3594, CVE-2021-3595)

Tenable has extracted the preceding description block directly from the Ubuntu 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
156562	Ubuntu 21.10 : libslirp vulnerabilities (USN-5009-2)	Nessus	Ubuntu Local Security Checks	1/7/2022	9/3/2025	low
224108	Linux Distros Unpatched Vulnerability : CVE-2021-3592	Nessus	Misc.	3/5/2025	9/10/2025	low
158874	AlmaLinux 8 : virt:rhel and virt-devel:rhel (ALSA-2021:4191)	Nessus	Alma Linux Local Security Checks	3/12/2022	1/13/2025	medium
152153	SUSE SLES12 Security Update : qemu (SUSE-SU-2021:2563-1)	Nessus	SuSE Local Security Checks	7/30/2021	7/13/2023	low
152118	openSUSE 15 Security Update : qemu (openSUSE-SU-2021:2474-1)	Nessus	SuSE Local Security Checks	7/28/2021	12/6/2023	low
155812	SUSE SLES11 Security Update : xen (SUSE-SU-2021:14848-1)	Nessus	SuSE Local Security Checks	12/2/2021	7/13/2023	high
210736	Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS / 24.10 : QEMU vulnerabilities (USN-7094-1)	Nessus	Ubuntu Local Security Checks	11/11/2024	9/3/2025	high
151680	Ubuntu 18.04 LTS / 20.04 LTS : QEMU vulnerabilities (USN-5010-1)	Nessus	Ubuntu Local Security Checks	7/16/2021	9/3/2025	high

Detections

Analytics

Plugins Search

low

low

medium

low

low

high

high

high