RUSTSEC-2026-0485 (CVE-2026-20763)
Vulnerability from osv_rustsec – Published: 2026-08-11 12:00 – Updated: 2026-11-11 08:37 – Source websitetdx_guest::tdcall::enter_l2_vcpu() invokes the TDG.VP.ENTER TDCALL. RCX
must carry the L2 VM index in bits 53:52 and the invalidation control value
(InvdTranslations, 0 to 3) in bits 1:0. The function computed that value as
(l2_vm_idx << 52) | (invd_translations as u64), but then passed the raw
l2_vm_idx in RCX instead.
As a result, the TDX module received an operand that differs from the
caller's request. The VM index field was 0, and the low bits of the index
were interpreted as the invalidation control value. For example, VM 1 with
InvdTlb (2) should produce 0x0010_0000_0000_0002, but produced 0x1.
Intel describes the issue as an incorrect calculation and classifies it as escalation of privilege, with a CVSS 4.0 base score of 4.6, in INTEL-SA-01462.
The flaw was corrected in commit
311d33b,
released in 0.3.1, which passes the computed RCX value.
Reported by Borys Tsyrulnikov.
{
"affected": [
{
"database_specific": {
"categories": [
"privilege-escalation"
],
"cvss": "CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [
"tdx_guest::tdcall::enter_l2_vcpu"
],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "tdx-guest",
"purl": "pkg:cargo/tdx-guest"
},
"ranges": [
{
"events": [
{
"introduced": "0.1.8"
},
{
"fixed": "0.3.1"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2026-20763",
"GHSA-wgvc-hf5h-m5h7"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "`tdx_guest::tdcall::enter_l2_vcpu()` invokes the `TDG.VP.ENTER` TDCALL. RCX\nmust carry the L2 VM index in bits 53:52 and the invalidation control value\n(`InvdTranslations`, 0 to 3) in bits 1:0. The function computed that value as\n`(l2_vm_idx \u003c\u003c 52) | (invd_translations as u64)`, but then passed the raw\n`l2_vm_idx` in RCX instead.\n\nAs a result, the TDX module received an operand that differs from the\ncaller\u0027s request. The VM index field was 0, and the low bits of the index\nwere interpreted as the invalidation control value. For example, VM 1 with\n`InvdTlb` (2) should produce `0x0010_0000_0000_0002`, but produced `0x1`.\n\nIntel describes the issue as an incorrect calculation and classifies it as\nescalation of privilege, with a CVSS 4.0 base score of 4.6, in\nINTEL-SA-01462.\n\nThe flaw was corrected in commit\n[`311d33b`](https://github.com/intel/confidential-computing.tdx.tdx-guest/commit/311d33b18a5bef5dc67c9b0c86587dd00c77027e),\nreleased in 0.3.1, which passes the computed RCX value.\n\nReported by [Borys Tsyrulnikov](https://borystsyrulnikov.dev).",
"id": "RUSTSEC-2026-0485",
"modified": "2026-11-11T08:37:09Z",
"published": "2026-08-11T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/tdx-guest"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0485.html"
},
{
"type": "WEB",
"url": "https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01462.html"
},
{
"type": "WEB",
"url": "https://github.com/intel/confidential-computing.tdx.tdx-guest/commit/311d33b18a5bef5dc67c9b0c86587dd00c77027e"
},
{
"type": "WEB",
"url": "https://borystsyrulnikov.dev/posts/tdx-guest-l2-vm-bugs/"
}
],
"related": [],
"severity": [
{
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "`enter_l2_vcpu` passes the wrong RCX operand to `TDG.VP.ENTER`"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.