vNUMA domain cleanup may race other operations
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Xen | Xen | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Xen | Xen |
|
Vendor Workaround
On x86, running only PV or PVH guests will avoid the vulnerability. Not enabling vNUMA for HVM guests will also avoid the vulnerability.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4818-1 | xen security update |
Debian DSA |
DSA-6424-1 | xen security update |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.224% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Xen
Xen xen |
|
| Vendors & Products |
Xen
Xen xen |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Accessing the vNUMA configuration data of a guest is still possible when domain destruction has already started. The cleaning up of that configuration information is not synchronized with its retrieval by a device model controlling the guest. | |
| Title | vNUMA domain cleanup may race other operations | |
| Weaknesses | CWE-362 | |
| References |
| |
| Metrics |
cvssV3_1
|