CVE-2025-38673
BaseFortify
Publication date: 2025-08-22
Last updated on: 2025-11-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the dma_buf field in the struct drm_gem_object, which is not stable over the object's lifetime. Specifically, the dma_buf field becomes NULL when user space releases the final GEM handle on the buffer object, leading to a NULL-pointer dereference. Previous workarounds only partially addressed the issue and did not cover buffer objects without a DRM framebuffer associated. The vulnerability was resolved by reverting a commit that changed how dma_buf was used, returning to using .import_attach->dmabuf to avoid the NULL-pointer dereference.
How can this vulnerability impact me? :
The vulnerability can cause a NULL-pointer dereference in the Linux kernel's DRM subsystem, which may lead to system crashes or instability when user space releases the final GEM handle on a buffer object. This could potentially be exploited to cause denial of service or affect system reliability.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is resolved by reverting the commit cce16fcd7446dcff7480cd9d2b6417075ed81065, which involved changes to the dma_buf field handling in the Linux kernel's drm_gem_object. Immediate mitigation involves updating your Linux kernel to a version that includes this revert. Workarounds from previous commits only partially addressed the issue and are not fully effective, especially for buffer objects without a DRM framebuffer. Therefore, applying the official patch or kernel update that reverts to using .import_attach->dmabuf is recommended.