CVE-2025-38669

Source
https://cve.org/CVERecord?id=CVE-2025-38669
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38669.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-38669
Downstream
Published
2025-08-22T16:03:00.399Z
Modified
2026-07-08T08:12:44.165893215Z
Summary
Revert "drm/gem-shmem: Use dma_buf from GEM object instance"
Details

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

Revert "drm/gem-shmem: Use dma_buf from GEM object instance"

This reverts commit 1a148af06000e545e714fe3210af3d77ff903c11.

The dmabuf field in struct drmgem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.

Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer: Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.

Hence, this revert to going back to using .import_attach->dmabuf.

v3: - cc stable

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38669.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
1a148af06000e545e714fe3210af3d77ff903c11
Fixed
291a77604858a8b47cf6640a12b76e97f99e00ed
Fixed
6d496e9569983a0d7a05be6661126d0702cf94f7

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38669.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.15.0
Fixed
6.15.9

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38669.json"