Accesses to the CMOS memory contents are done using an indirect IO port
pair. Therefore Xen needs to cache the guest chosen index, and one of
the usages of the index didn't take the necessary locking to avoid
concurrent changes. As a result, a guest could change the index after
it being checked, causing a subsequent out-of-bound read access to the
contents of an array.
References
Configurations
No configuration.
History
28 Jul 2026, 17:16
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
28 Jul 2026, 16:19
| Type | Values Removed | Values Added |
|---|---|---|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 7.5 |
| CWE | CWE-362 |
28 Jul 2026, 14:16
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
28 Jul 2026, 13:19
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-07-28 13:19
Updated : 2026-07-28 17:16
NVD link : CVE-2026-62430
Mitre link : CVE-2026-62430
CVE.ORG link : CVE-2026-62430
JSON object : View
Products Affected
No product.
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
