grant-table: version change racing with other operations
[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]
With the introduction of Grant Table v2 came the requirement to be able to
switch between versions. Switching from v1 to v2 reduces the number of
valid grant references, as a bigger shared entry structure is then needed
while the shared table doesn't change size. Switching from v2 back to v1
the status frames, which are separate in v2, go away.
Code holding, but intermediately dropping and then re-acquiring the grant
table lock, sometimes wrongly assumes that said properties wouldn't change
across the window in time where the lock is not being held.
The v1 -> v2 issue is CVE-2026-62435.
The v2 -> v1 issue is CVE-2026-62436.
Metrics
| Version | Base score | Base severity | Vector |
|---|
Impacts
| CAPEC ID | Description |
|---|
| N/A | An unprivileged guest may be able to elevate its privileges to that of the
host. Information leaks and Denial of Service (DoS) are possible as well. |
CAPEC ID: N/A
Description: An unprivileged guest may be able to elevate its privileges to that of the
host. Information leaks and Denial of Service (DoS) are possible as well.