GHSA-X462-GW38-389Q
Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32In the Linux kernel, the following vulnerability has been resolved:
drm/loongson: Handle buffer mapping failures when clearing a BO
lsdc_bo_clear() ignores the return value from lsdc_bo_kmap() and writes to lbo->kptr unconditionally. When the first mapping of a newly allocated buffer fails, kptr is still NULL and the subsequent memset accesses it.
Return the mapping error without touching the buffer and propagate it from lsdc_gem_object_create(). Install the GEM object functions before clearing so that drm_gem_object_put() can release the buffer correctly on failure. Do not add the failed object to the tracking list or return an uncleared buffer to the caller.
Imported buffers still skip clearing, and successfully mapped buffers are cleared and unmapped as before.
Tested on LS7A2000 with a one-shot range error in ttm_bo_kmap(). Its -EINVAL return reached userspace, the object was destroyed once, and no GEM handle was published. Normal create/map/zero/write/read/close cycles passed, with the tracked BO count and VRAM usage unchanged.
AI assistance was used for the lifetime analysis, fix, fault-injection tools, build and test execution.
{
"affected": [],
"aliases": [
"CVE-2026-99752"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-20T06:18:13Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/loongson: Handle buffer mapping failures when clearing a BO\n\nlsdc_bo_clear() ignores the return value from lsdc_bo_kmap() and writes\nto lbo-\u003ekptr unconditionally. When the first mapping of a newly allocated\nbuffer fails, kptr is still NULL and the subsequent memset accesses it.\n\nReturn the mapping error without touching the buffer and propagate it\nfrom lsdc_gem_object_create(). Install the GEM object functions before\nclearing so that drm_gem_object_put() can release the buffer correctly\non failure. Do not add the failed object to the tracking list or return\nan uncleared buffer to the caller.\n\nImported buffers still skip clearing, and successfully mapped buffers\nare cleared and unmapped as before.\n\nTested on LS7A2000 with a one-shot range error in ttm_bo_kmap(). Its\n-EINVAL return reached userspace, the object was destroyed once, and\nno GEM handle was published. Normal create/map/zero/write/read/close\ncycles passed, with the tracked BO count and VRAM usage unchanged.\n\nAI assistance was used for the lifetime analysis, fix, fault-injection\ntools, build and test execution.",
"id": "GHSA-x462-gw38-389q",
"modified": "2026-11-20T06:32:10Z",
"published": "2026-11-20T06:32:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99752"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/256ca06920504adde310fb5252342e4b827ebcce"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/389de73fb826e768c73d82c8f9f7e516b3fff70b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/834c2fdf737657c3a16c37b894a6bd07277ff082"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f00d7a241f846b053e89c0bb2285ef5988d4cafc"
}
],
"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.