Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99752drm/loongson: Handle buffer mapping failures when clearing a BO

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.

Timeline

  1. ID reserved

    By Linux

  2. · 56 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE.

EPSS (exploitation in 30 days)
Not scored

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected f39db26c54281da6a785259498ca74b5e470476f – < 389de73fb826e768c73d82c8f9f7e516b3fff70b
    • affected f39db26c54281da6a785259498ca74b5e470476f – < 834c2fdf737657c3a16c37b894a6bd07277ff082
    • affected f39db26c54281da6a785259498ca74b5e470476f – < 256ca06920504adde310fb5252342e4b827ebcce
    • affected f39db26c54281da6a785259498ca74b5e470476f – < f00d7a241f846b053e89c0bb2285ef5988d4cafc
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.12.118 – ≤ 6.12.*
    • unaffected 6.18.64 – ≤ 6.18.*
    • unaffected 7.3.5 – ≤ 7.3.*
    • unaffected 7.4-rc2 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99752 badge
[![CVE-2026-99752](https://cveledger.app/badge/CVE-2026-99752.svg)](https://cveledger.app/cve/CVE-2026-99752)

Record last updated .