Skip to content
Heist/ feed
Back to feed
UnratedFix available

drm/nouveau: fix several DMA buffer leaks

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix several DMA buffer leaks Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects. Several of these buffers are never dealloced. Some of them can be deallocated right after GSP-RM is initialized, but the rest need to stay until the driver unloads. Also futher bullet-proof these objects by poisoning the buffer and clearing the nvkm_gsp_mem object when it is deallocated. Poisoning the buffer should trigger an error (or crash) from GSP-RM if it tries to access the buffer after we've deallocated it, because we were wrong about when it is safe to deallocate. Finally, change the mem->size field to a size_t because that's the same type that dma_alloc_coherent expects.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.7.6
CVEs
CVE-2024-26912
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 05:34 UTC · Revision 1

Source evidence

drm/nouveau: fix several DMA buffer leaks

core-osv · Original source

Published 17 Apr 2024, 15:59 UTC

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix several DMA buffer leaks Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects. Several of these buffers are never dealloced. Some of them can be deallocated right after GSP-RM is initialized, but the rest need to stay until the driver unloads. Also futher bullet-proof these objects by poisoning the buffer and clearing the nvkm_gsp_mem object when it is deallocated. Poisoning the buffer should trigger an error (or crash) from GSP-RM if it tries to access the buffer after we've deallocated it, because we were wrong about when it is safe to deallocate. Finally, change the mem->size field to a size_t because that's the same type that dma_alloc_coherent expects.

osv:CVE-2024-26912

Kernel

Fixed versions: 6.7.6

Complete source record
{
  "id": "247e00d005f0584b9492f5a52869f53a67cacff1c0cecdbc0009d8b6090e25fe",
  "url": "https://osv.dev/vulnerability/CVE-2024-26912",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "drm/nouveau: fix several DMA buffer leaks",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix several DMA buffer leaks Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects. Several of these buffers are never dealloced. Some of them can be deallocated right after GSP-RM is initialized, but the rest need to stay until the driver unloads. Also futher bullet-proof these objects by poisoning the buffer and clearing the nvkm_gsp_mem object when it is deallocated. Poisoning the buffer should trigger an error (or crash) from GSP-RM if it tries to access the buffer after we've deallocated it, because we were wrong about when it is safe to deallocate. Finally, change the mem->size field to a size_t because that's the same type that dma_alloc_coherent expects.",
    "evidence": "osv:CVE-2024-26912",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.7.6",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2024-26912",
      "aliases": [
        "CVE-2024-26912"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "176fdcbddfd288408ce8571c1760ad618d962096"
                },
                {
                  "fixed": "6190d4c08897d748dd25f0b78267a90aa1694e15"
                },
                {
                  "fixed": "042b5f83841fbf7ce39474412db3b5e4765a7ea7"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26912.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.7.6"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26912.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.296322595Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/042b5f83841fbf7ce39474412db3b5e4765a7ea7",
        "https://git.kernel.org/stable/c/6190d4c08897d748dd25f0b78267a90aa1694e15",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/26xxx/CVE-2024-26912.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2024-26912",
        "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/2024/26xxx/CVE-2024-26912.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2024-26912",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 492753,
  "published_at": "2024-04-17T15:59:23.223+00:00"
}