CVE-2026-99753: drm/loongson: Fix double free on BO initialization failure

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drm/loongson: Fix double free on BO initialization failure

If ttmboinitvalidate() fails, it drops the buffer object's reference and cleans it up through the supplied destroy callback. lsdcbodestroy() releases the GEM object and frees the enclosing lsdcbo, so freeing it again in lsdcbocreate() causes a double free on a synchronous failure path.

Let TTM own the cleanup after initialization has started and return the error directly. Keep the explicit free on drmgemobjectinit() failure, which occurs before ownership is passed to TTM.

Tested on LS7A2000 by making drmvmaoffsetadd() return -ENOSPC for one selected dumb-buffer creation. The error reached userspace, the destroy callback ran once, and no handle was published or tracked BO retained. Normal buffer creation, zeroing, mapping, readback and release passed.

AI assistance was used for the ownership analysis, fix, fault-injection tools, build and test execution.

Affected Software

6 affected componentsFixes available
linux/kernel>=6.6.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux<=6.12.107-1, <=6.12.117-1, <=7.3.4-1
6.1.176-16.1.192-27.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 7.3.5-1
  5. Compensating control

    In drm/loongson lsdc_bo_create(), keep the explicit free when drm_gem_object_init() fails before ownership is passed to TTM. Once initialization has started, let TTM clean up through the supplied destroy callback and return the error directly; do not free the buffer object again.

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

When can the double free occur?

It occurs only when ttm_bo_init_validate() fails after TTM has taken ownership of the buffer object. The affected path is synchronous buffer-object initialization, such as the tested dumb-buffer creation failure induced by drm_vma_offset_add() returning -ENOSPC.

2

Is a buffer handle or retained buffer object left behind when this failure occurs?

In the tested failure case, the error was returned to userspace, no handle was published, and no tracked buffer object was retained. The destroy callback ran once after the fix.

3

What behavior distinguishes the fixed cleanup path?

After initialization has started, the caller returns the error directly and lets TTM perform cleanup through the supplied destroy callback. Explicit freeing remains only for drm_gem_object_init() failures, before ownership has passed to TTM.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203