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

{
  "id": "3a11a3b93e6e0268d6949e5c4605e198170331123c8b51ec479fad1f6a58a97a",
  "url": "https://osv.dev/vulnerability/CVE-2025-38673",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Revert \"drm/gem-framebuffer: Use dma_buf from GEM object instance\"",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: Revert \"drm/gem-framebuffer: Use dma_buf from GEM object instance\" This reverts commit cce16fcd7446dcff7480cd9d2b6417075ed81065. The dma_buf field in struct drm_gem_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",
    "evidence": "osv:CVE-2025-38673",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.15.9",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2025-38673",
      "aliases": [
        "CVE-2025-38673"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "cce16fcd7446dcff7480cd9d2b6417075ed81065"
                },
                {
                  "fixed": "e31f5a1c2cd38bf977736cdfa79444e19d4005ec"
                },
                {
                  "fixed": "2712ca878b688682ac2ce02aefc413fc76019cd9"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38673.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.15.0"
                },
                {
                  "fixed": "6.15.9"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38673.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.283030380Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/2712ca878b688682ac2ce02aefc413fc76019cd9",
        "https://git.kernel.org/stable/c/e31f5a1c2cd38bf977736cdfa79444e19d4005ec",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38673.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-38673",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38673.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-38673",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 492698,
  "published_at": "2025-08-22T16:03:03.594+00:00"
}