grant-table: type confusion in grant-copy
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
There is no known mitigation.
| 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.115% 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 | When grant-copy operations are processed, the respective grant may or may not already be in use by another operation (a mapping or another copy). For all copy operations the referenced guest frame is looked up. When another operation is already active for the grant (the grant is "pinned"), what is being supplied back to actually carry out permission checks and copy operation may not be consistent: The permission check may be carried out on a page different from the one involved in the copy. | |
| Title | grant-table: type confusion in grant-copy | |
| Weaknesses | CWE-367 | |
| References |
| |
| Metrics |
cvssV3_1
|