The remote SUSE Linux SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2955-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)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - An issue was discovered in Xen 4.12.3 through 4.12.4 and 4.13.1 through 4.14.x. An x86 HVM guest with PCI     pass through devices can force the allocation of all IDT vectors on the system by rebooting itself with     MSI or MSI-X capabilities enabled and entries setup. Such reboots will leak any vectors used by the     MSI(-X) entries that the guest might had enabled, and hence will lead to vector exhaustion on the system,     not allowing further PCI pass through devices to work properly. HVM guests with PCI pass through devices     can mount a Denial of Service (DoS) attack affecting the pass through of PCI devices to other guests or     the hardware domain. In the latter case, this would affect the entire host. (CVE-2021-3308)

  - 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)

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 SLED15 / SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2922-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)

  - 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)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)     in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not     leaked from the modules, Xen must scrub them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

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 packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2021:2923-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)

  - 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)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)     in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not     leaked from the modules, Xen must scrub them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

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 SLED12 / SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2924-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)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)     in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not     leaked from the modules, Xen must scrub them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

  - 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)

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 packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2021:1236-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)

  - 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)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)     in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not     leaked from the modules, Xen must scrub them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

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

The remote host is affected by the vulnerability described in GLSA-202208-23 (Xen: Multiple Vulnerabilities)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

  - 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)

  - PCI devices with RMRRs not deassigned correctly Certain PCI devices in a system might be assigned Reserved     Memory Regions (specified via Reserved Memory Region Reporting, RMRR). These are typically used for     platform tasks such as legacy USB emulation. If such a device is passed through to a guest, then on guest     shutdown the device is not properly deassigned. The IOMMU configuration for these devices which are not     properly deassigned ends up pointing to a freed data structure, including the IO Pagetables. Subsequent     DMA or interrupts from the device will have unpredictable behaviour, ranging from IOMMU faults to memory     corruption. (CVE-2021-28702)

  - certain VT-d IOMMUs may not work in shared page table mode For efficiency reasons, address translation     control structures (page tables) may (and, on suitable hardware, by default will) be shared between CPUs,     for second-level translation (EPT), and IOMMUs. These page tables are presently set up to always be 4     levels deep. However, an IOMMU may require the use of just 3 page table levels. In such a configuration     the lop level table needs to be stripped before inserting the root table's address into the hardware     pagetable base register. When sharing page tables, Xen erroneously skipped this stripping. Consequently,     the guest is able to write to leaf page table entries. (CVE-2021-28710)

  - Incomplete cleanup of multi-core shared buffers for some Intel(R) Processors may allow an authenticated     user to potentially enable information disclosure via local access. (CVE-2022-21123)

  - Incomplete cleanup of microarchitectural fill buffers on some Intel(R) Processors may allow an     authenticated user to potentially enable information disclosure via local access. (CVE-2022-21125)

  - Incomplete cleanup in specific special register write operations for some Intel(R) Processors may allow an     authenticated user to potentially enable information disclosure via local access. (CVE-2022-21166)

  - arm: guest_physmap_remove_page not removing the p2m mappings The functions to remove one or more entries     from a guest p2m pagetable on Arm (p2m_remove_mapping, guest_physmap_remove_page, and p2m_set_entry with     mfn set to INVALID_MFN) do not actually clear the pagetable entry if the entry doesn't have the valid bit     set. It is possible to have a valid pagetable entry without the valid bit set when a guest operating     system uses set/way cache maintenance instructions. For instance, a guest issuing a set/way cache     maintenance instruction, then calling the XENMEM_decrease_reservation hypercall to give back memory pages     to Xen, might be able to retain access to those pages even after Xen started reusing them for other     purposes. (CVE-2022-23033)

  - A PV guest could DoS Xen while unmapping a grant To address XSA-380, reference counting was introduced for     grant mappings for the case where a PV guest would have the IOMMU enabled. PV guests can request two forms     of mappings. When both are in use for any individual mapping, unmapping of such a mapping can be requested     in two steps. The reference count for such a mapping would then mistakenly be decremented twice. Underflow     of the counters gets detected, resulting in the triggering of a hypervisor bug check. (CVE-2022-23034)

  - Insufficient cleanup of passed-through device IRQs The management of IRQs associated with physical devices     exposed to x86 HVM guests involves an iterative operation in particular when cleaning up after the guest's     use of the device. In the case where an interrupt is not quiescent yet at the time this cleanup gets     invoked, the cleanup attempt may be scheduled to be retried. When multiple interrupts are involved, this     scheduling of a retry may get erroneously skipped. At the same time pointers may get cleared (resulting in     a de-reference of NULL) and freed (resulting in a use-after-free), while other code would continue to     assume them to be valid. (CVE-2022-23035)

  - x86 pv: Race condition in typeref acquisition Xen maintains a type reference count for pages, in addition     to a regular reference count. This scheme is used to maintain invariants required for Xen's safety, e.g.
    PV guests may not have direct writeable access to pagetables; updates need auditing by Xen. Unfortunately,     the logic for acquiring a type reference has a race condition, whereby a safely TLB flush is issued too     early and creates a window where the guest can re-establish the read/write mapping before writeability is     prohibited. (CVE-2022-26362)

  - x86 pv: Insufficient care with non-coherent mappings T[his CNA information record relates to multiple     CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Xen maintains a type     reference count for pages, in addition to a regular reference count. This scheme is used to maintain     invariants required for Xen's safety, e.g. PV guests may not have direct writeable access to pagetables;
    updates need auditing by Xen. Unfortunately, Xen's safety logic doesn't account for CPU-induced cache non-     coherency; cases where the CPU can cause the content of the cache to be different to the content in main     memory. In such cases, Xen's safety logic can incorrectly conclude that the contents of a page is safe.
    (CVE-2022-26363, CVE-2022-26364)

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-2021:2925-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)

  - 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)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)     in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not     leaked from the modules, Xen must scrub them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

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-2021:2943-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)

  - 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)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

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 SLED15 / SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2923-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)

  - 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)

  - xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...)     in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not     leaked from the modules, Xen must scrub them before handing the page over to the allocator.
    Unfortunately, it was discovered that modules will not be scrubbed on Arm. (CVE-2021-28693)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

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

The remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-4977 advisory.

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - xen/arm: No memory limit for dom0less domUs The dom0less feature allows an administrator to create     multiple unprivileged domains directly from Xen. Unfortunately, the memory limit from them is not set.
    This allow a domain to allocate memory beyond what an administrator originally configured.
    (CVE-2021-28700)

  - 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)

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 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:2957-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)

  - IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains     which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify     regions of memory which should be left untranslated, which typically means these addresses should pass the     translation phase unaltered. While these are typically device specific ACPI properties, they can also be     specified to apply to a range of devices, or even all devices. On all systems with such regions Xen failed     to prevent guests from undoing/replacing such mappings (CVE-2021-28694). On AMD systems, where a     discontinuous range is specified by firmware, the supposedly-excluded middle range will also be identity-     mapped (CVE-2021-28695). Further, on AMD systems, upon de-assigment of a physical device from a guest, the     identity mappings would be left in place, allowing a guest continued access to ranges of memory which it     shouldn't have access to anymore (CVE-2021-28696). (CVE-2021-28694, CVE-2021-28695, CVE-2021-28696)

  - 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)

  - inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant     attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result,     guests also need to be able to retrieve the addresses that the new status tracking table can be accessed     through. For 32-bit guests on x86, translation of requests has to occur because the interface structure     layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers     of the grant status table involves translating the resulting array of frame numbers. Since the space used     to carry out the translation is limited, the translation layer tells the core function the capacity of the     array within translation space. Unfortunately the core function then only enforces array bounds to be     below 8 times the specified value, and would write past the available space if enough frame numbers needed     storing. (CVE-2021-28699)

  - 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)

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
152991	SUSE SLES12 Security Update : xen (SUSE-SU-2021:2955-1)	Nessus	SuSE Local Security Checks	9/4/2021	7/14/2023	high
153016	SUSE SLED15 / SLES15 Security Update : xen (SUSE-SU-2021:2922-1)	Nessus	SuSE Local Security Checks	9/4/2021	7/14/2023	high
153009	openSUSE 15 Security Update : xen (openSUSE-SU-2021:2923-1)	Nessus	SuSE Local Security Checks	9/4/2021	5/9/2022	high
153017	SUSE SLED12 / SLES12 Security Update : xen (SUSE-SU-2021:2924-1)	Nessus	SuSE Local Security Checks	9/4/2021	7/14/2023	high
153108	openSUSE 15 Security Update : xen (openSUSE-SU-2021:1236-1)	Nessus	SuSE Local Security Checks	9/8/2021	5/9/2022	high
164116	GLSA-202208-23 : Xen: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	8/15/2022	10/16/2023	high
153013	SUSE SLES15 Security Update : xen (SUSE-SU-2021:2925-1)	Nessus	SuSE Local Security Checks	9/4/2021	7/14/2023	high
152990	SUSE SLES15 Security Update : xen (SUSE-SU-2021:2943-1)	Nessus	SuSE Local Security Checks	9/4/2021	7/14/2023	high
153010	SUSE SLED15 / SLES15 Security Update : xen (SUSE-SU-2021:2923-1)	Nessus	SuSE Local Security Checks	9/4/2021	7/13/2023	high
153509	Debian DSA-4977-1 : xen - security update	Nessus	Debian Local Security Checks	9/21/2021	5/9/2022	high
153027	SUSE SLES12 Security Update : xen (SUSE-SU-2021:2957-1)	Nessus	SuSE Local Security Checks	9/6/2021	7/14/2023	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high

high

high

high

high