GHSA-22J6-XV38-9GXW
Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32In the Linux kernel, the following vulnerability has been resolved:
vduse: fix VA/PA confusion in the coherent page fault path
vduse_domain_get_coherent_page() assumes that iotlb entries above bounce_size were installed by vduse_domain_alloc_coherent(), so it treats map->addr as a physical address. But vduse registers with use_va = true, and when the device is bound to vhost_vdpa, vhost_vdpa_va_map() stores a userspace virtual address in map->addr, which vduse_domain_set_map() then copies into the same iotlb. A process holding the domain file descriptor across a rebind can therefore fault in an arbitrary physical page with read/write access, ignoring the entry permissions.
Additionally, since the domain file mmap lacks VM_IO, the domain file itself can be mapped and passed to vhost_vdpa_va_map(), producing self-referential entries that bypass the coherent path check.
To fix, only translate entries whose backing file is the domain file itself in vduse_domain_get_coherent_page(), reject such entries in vduse_domain_set_map() since only external mappings should be imported, and set VM_IO on the domain file mmap so vhost_vdpa_va_map() refuses to map it in the first place.
{
"affected": [],
"aliases": [
"CVE-2026-99683"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-20T06:18:03Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nvduse: fix VA/PA confusion in the coherent page fault path\n\nvduse_domain_get_coherent_page() assumes that iotlb entries above\nbounce_size were installed by vduse_domain_alloc_coherent(), so it\ntreats map-\u003eaddr as a physical address. But vduse registers with\nuse_va = true, and when the device is bound to vhost_vdpa,\nvhost_vdpa_va_map() stores a userspace virtual address in map-\u003eaddr,\nwhich vduse_domain_set_map() then copies into the same iotlb. A\nprocess holding the domain file descriptor across a rebind can\ntherefore fault in an arbitrary physical page with read/write\naccess, ignoring the entry permissions.\n\nAdditionally, since the domain file mmap lacks VM_IO, the domain\nfile itself can be mapped and passed to vhost_vdpa_va_map(),\nproducing self-referential entries that bypass the coherent path\ncheck.\n\nTo fix, only translate entries whose backing file is the domain\nfile itself in vduse_domain_get_coherent_page(), reject such\nentries in vduse_domain_set_map() since only external mappings\nshould be imported, and set VM_IO on the domain file mmap so\nvhost_vdpa_va_map() refuses to map it in the first place.",
"id": "GHSA-22j6-xv38-9gxw",
"modified": "2026-11-20T06:32:07Z",
"published": "2026-11-20T06:32:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99683"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1b46b4182d3d5c1a085cfe2578048e1ce09e0e01"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4c8fdb725614189b6c73cf5f7f509592758b6d18"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bb2e6f166547838fd7c320b01c90918b736f76e2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e74a3ed4f59d84036500c5da3905ee40d2c8efa1"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.