EulerOS 2.0 SP15 : qemu (EulerOS-SA-2026-5207)

medium Nessus Plugin ID 383298

Synopsis

The remote EulerOS host is missing multiple security updates.

Description

According to the versions of the qemu packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

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 security vulnerability exists in QEMU. Detailed vulnerability information has not yet been disclosed.
This vulnerability affects all versions.(CVE-2026-16043)

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 security vulnerability exists in QEMU, the details of which have not been fully disclosed.(CVE-2026-15578)

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)

hw/9pfs: cap Treaddir allocation (CVE-2026-9238) Constrain max_count in v9fs_readdir() to transport'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 'count' parameter, and while the negotiated 'msize' provides some limit, it accounts for guest being somewhat faithful on the negotiated 'msize' value throughout the session. A bad guest client could have negotiated a large 'msize' but provide a small reply buffer for Treaddir request, causing QEMU to allocate host memory proportional to 'msize' 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 'broken', 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)

An undisclosed vulnerability exists in QEMU, with no detailed vulnerability description available at this time.(CVE-2026-63319)

Tenable has extracted the preceding description block directly from the EulerOS qemu security advisory.

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

Solution

Update the affected qemu packages.

See Also

http://www.nessus.org/u?57ca2dc4

Plugin Details

Severity: Medium

ID: 383298

File Name: EulerOS_SA-2026-5207.nasl

Version: 1.1

Type: Local

Published: 11/19/2026

Updated: 11/19/2026

Supported Sensors: Nessus

Risk Information

VPR

Risk Factor: Medium

Score: 4.3

Percentile: 53.48

CVSS v2

Risk Factor: Low

Base Score: 2.1

Temporal Score: 1.6

Vector: CVSS2#AV:L/AC:L/Au:N/C:N/I:N/A:P

CVSS Score Source: CVE-2026-9238

CVSS v3

Risk Factor: Medium

Base Score: 6.5

Temporal Score: 5.7

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

CPE: cpe:/o:huawei:euleros:2.0, p-cpe:/a:huawei:euleros:qemu-img, p-cpe:/a:huawei:euleros:qemu

Required KB Items: Host/local_checks_enabled, Host/cpu, Host/EulerOS/release, Host/EulerOS/rpm-list, Host/EulerOS/sp

Excluded KB Items: Host/EulerOS/uvp_version

Exploit Ease: No known exploits are available

Patch Publication Date: 11/19/2026

Vulnerability Publication Date: 8/17/2026

Reference Information

CVE: CVE-2026-15578, CVE-2026-15705, CVE-2026-16043, CVE-2026-61475, CVE-2026-63319, CVE-2026-8348, CVE-2026-9238