Skip to content
Threat Brief

← All advisories

CVE-2026-99752

Severity unknownNo known exploitationFix available

drm/loongson: Handle buffer mapping failures when clearing a BO

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 9% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In 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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom f39db26c54281da6a785259498ca74b5e470476f before 834c2fdf737657c3a16c37b894a6bd07277ff082834c2fdf737657c3a16c37b894a6bd07277ff082CVE Program
LinuxLinuxfrom f39db26c54281da6a785259498ca74b5e470476f before 256ca06920504adde310fb5252342e4b827ebcce256ca06920504adde310fb5252342e4b827ebcceCVE Program
LinuxLinuxfrom f39db26c54281da6a785259498ca74b5e470476f before f00d7a241f846b053e89c0bb2285ef5988d4cafcf00d7a241f846b053e89c0bb2285ef5988d4cafcCVE Program
LinuxLinuxfrom f39db26c54281da6a785259498ca74b5e470476f before 389de73fb826e768c73d82c8f9f7e516b3fff70b389de73fb826e768c73d82c8f9f7e516b3fff70bCVE Program
LinuxLinux6.6Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.6Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references