<?xml version="1.0" encoding="utf-8"?>
  <?xml-stylesheet type="text/xsl" href="sa-render.xsl"?>
  <update from="huaweicloud.com" type="security" status="stable" version="1">
    <id>HCE2-SA-2026-0363</id>
    <title>An update for qemu is now available for HCE 2.0</title>
    <severity>Critical</severity>
    <release>HCE 2.0</release>
    <issued date="2026-09-20 19:57:29"/>
    <updated date="2026-09-20 19:57:29"/>
    <references>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-8348" id="CVE-2026-8348" title="CVE-2026-8348 Base Score: 6.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2025-14876" id="CVE-2025-14876" title="CVE-2025-14876 Base Score: 5.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-48914" id="CVE-2026-48914" title="CVE-2026-48914 Base Score: 6.7 Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-15705" id="CVE-2026-15705" title="CVE-2026-15705 Base Score: 6.4 Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-36648" id="CVE-2022-36648" title="CVE-2022-36648 Base Score: 10.0 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-50626" id="CVE-2026-50626" title="CVE-2026-50626 Base Score: 8.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-61475" id="CVE-2026-61475" title="CVE-2026-61475 Base Score: 5.3 Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2024-6519" id="CVE-2024-6519" title="CVE-2024-6519 Base Score: 8.2 Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-15578" id="CVE-2026-15578" title="CVE-2026-15578 Base Score: 7.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-9238" id="CVE-2026-9238" title="CVE-2026-9238 Base Score: 3.8 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-16457" id="CVE-2026-16457" title="CVE-2026-16457 Base Score: 6.5 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-66021" id="CVE-2026-66021" title="CVE-2026-66021 Base Score: 7.3 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-16043" id="CVE-2026-16043" title="CVE-2026-16043 Base Score: 8.2 Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-2243" id="CVE-2026-2243" title="CVE-2026-2243 Base Score: 5.1 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-63319" id="CVE-2026-63319" title="CVE-2026-63319 Base Score: 7.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
    </references>
    <description>Security Fix(es):

hw/9pfs: add xattr FID limit to prevent memory exhaustion Add a limit on the number of simultaneously open xattr FIDs to prevent host memory exhaustion attacks. Each xattr FID contains a buffer for the xattr value, and without a limit, a malicious priviliged guest with direct communication access to 9p server could create a huge number of xattr FIDs until host memory is eventually exhausted. Fix this by: - add xattr_fid_limit to struct FsContext for the max. amount - add xattr_fid_count to struct FsContext for the current amount - init xattr_fid_limit with 1024 - init xattr_fid_count with 0 - add function xattr_fid_count_inc() to increment the count - add function xattr_fid_count_decr() to decrement the count - call xattr_fid_count_inc() in Txattrcreate handler - call xattr_fid_count_inc() in Txattrwalk handler - call xattr_fid_count_decr() when a xattr FID is freed Additionally: - reset the xattr FID counter in virtfs_reset() When the limit is reached then xattr_fid_count_inc() returns -ENOSPC and the request handler is aborted on its error path without turning the FID into an xattr type and without allocating memory for the xattr. The default value of 1024 was chosen, as (sane usage of) xattr requests in the 9p protocol are usually very short-lived, and even machines with 128 cores with very high xattr activity should have plenty of head room without ever hitting this limit. (CVE-2026-8348)

A flaw was found in the virtio-crypto device of QEMU. A malicious guest operating system can exploit a missing length limit in the AKCIPHER path, leading to uncontrolled memory allocation. This can result in a denial of service (DoS) on the host system by causing the QEMU process to terminate unexpectedly. (CVE-2025-14876)

A flaw was found in QEMU_x27;s virtio-blk device. The issue arises because the device does not properly validate the size of input descriptors before writing data. A malicious guest with high privileges could exploit this vulnerability by submitting a malformed virtio-blk SCSI request, leading to an out-of-bounds write in the host heap memory and a potential denial of service (DoS) for the QEMU process. (CVE-2026-48914)

CVE-2026-15705 is an undisclosed vulnerability in QEMU. The vulnerability has been identified in QEMU, but specific technical details and impact scope have not yet been publicly disclosed. (CVE-2026-15705)

The hardware emulation in the of_dpa_cmd_add_l2_flood of rocker device model in QEMU, as used in 7.0.0 and earlier, allows remote attackers to crash the host qemu and potentially execute code on the host via execute a malformed program in the guest OS. Note: This has been disputed by multiple third parties as not a valid vulnerability due to the rocker device not falling within the virtualization use case. (CVE-2022-36648)

An unknown vulnerability exists in QEMU, details are not yet disclosed. (CVE-2026-50626)

In the Linux kernel, the following vulnerabilities have been addressed: bpf: Support hardened BPF for JIT injection. The JIT allocator packages many small programs into larger executable allocations and reuses space in these allocations, loading and freeing them just like programs. When new code is written to the space of the previous code, the program is occupied, and indirect jumps to the new program can reuse the oracles left by the old oracles in the branch. Flush indirect branch predictors before reusing JIT memory so that indirect jumps to a newly written program do not reuse predictions from an old program that occupies the same space. Introduced bpf_arch_pred_flush_enabled static key and bpf_arch_pred_flush static call for refreshing the branch predictor of JIT memory reuse. Schemas that need to be refreshed can update them with the predictor refresh function. By default, it is a NOP and no CALLs will be issued. Allocations larger than the package are not covered by this flush. That_39;s safe because the cBPF program (unprivileged attack surface) is well constrained below the package size. If this assumption is violated, a warning is issued while flushing is active. (CVE-2026-61475)

A use-after-free vulnerability was found in the QEMU LSI53C895A SCSI Host Bus Adapter emulation. This issue can lead to a crash or VM escape. (CVE-2024-6519)

A security vulnerability exists in QEMU, the details of which have not been fully disclosed. (CVE-2026-15578)

hw/9pfs: cap Treaddir allocation (CVE-2026-9238) Constrain max_count in v9fs_readdir() to transport_x27;s current, real response buffer size before calling v9fs_do_readdir() to prevent excessive host memory allocation for specific, crafted, huge directories (large amount of entries) by bad clients. Client may send a Treaddir request with a large _x27;count_x27; parameter, and while the negotiated _x27;msize_x27; provides some limit, it accounts for guest being somewhat faithful on the negotiated _x27;msize_x27; value throughout the session. A bad guest client could have negotiated a large _x27;msize_x27; but provide a small reply buffer for Treaddir request, causing QEMU to allocate host memory proportional to _x27;msize_x27; before discovering the reply cannot fit. Possible consequence was a potential DoS by a priviliged guest, causing a disconnection of guest communication due to transport device being marked as &quot;broken&quot;, however QEMU process would have continued to run with potentially giant host memory allocation, which might have negative impact on other services running on host. (CVE-2026-9238)

CVE-2026-16457 is a security vulnerability in QEMU. The specific details of this vulnerability have not been fully disclosed. This vulnerability may affect the normal operation of the QEMU virtualization platform and poses potential security risks. (CVE-2026-16457)

QEMU (Quick Emulator) is an open-source machine emulator and virtualizer widely used to run operating systems for different architectures. CVE-2026-66021 is a security vulnerability affecting QEMU, with specific details not yet fully disclosed. (CVE-2026-66021)

A security vulnerability exists in QEMU. Detailed vulnerability information has not yet been disclosed. This vulnerability affects all versions. (CVE-2026-16043)

A flaw was found in QEMU. A specially crafted VMDK image could trigger an out-of-bounds read vulnerability, potentially leading to a 12-byte leak of sensitive information or a denial of service condition (DoS). (CVE-2026-2243)

An undisclosed vulnerability exists in QEMU, with no detailed vulnerability description available at this time. (CVE-2026-63319)
</description>
    <pkglist>
      <collection short="HCE 2.0" package="qemu">
        <name>HCE 2.0</name>
        <package arch="x86_64" name="qemu" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-6.2.0-263.r118.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="qemu-block-curl" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-block-curl-6.2.0-263.r118.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="qemu-block-iscsi" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-block-iscsi-6.2.0-263.r118.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="qemu-hw-usb-host" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-hw-usb-host-6.2.0-263.r118.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="qemu-img" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-img-6.2.0-263.r118.hce2.x86_64.rpm</filename>
        </package>
        <package arch="aarch64" name="qemu" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-6.2.0-263.r118.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="qemu-block-curl" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-block-curl-6.2.0-263.r118.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="qemu-block-iscsi" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-block-iscsi-6.2.0-263.r118.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="qemu-hw-usb-host" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-hw-usb-host-6.2.0-263.r118.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="qemu-img" version="6.2.0" release="263.r118.hce2">
          <filename>qemu-img-6.2.0-263.r118.hce2.aarch64.rpm</filename>
        </package>
      </collection>
    </pkglist>
  </update>
