LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26912: drm/nouveau: fix several DMA buffer leaks

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26912 is a Linux kernel nouveau graphics driver issue where some DMA buffers are not freed correctly. The public record does not provide a severity score or evidence of exploitation. Business urgency depends on whether affected Linux systems use the nouveau driver with NVIDIA hardware.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize patching where Linux workstations, GPU nodes, or servers use nouveau with NVIDIA hardware.

Technical view

The issue is in drm/nouveau GSP-RM DMA buffer handling. nvkm_gsp_mem objects could remain allocated longer than intended. The fix deallocates some buffers after GSP-RM initialization, keeps others until driver unload, poisons cleared buffers, clears objects on deallocation, and changes mem->size to size_t.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the nouveau driver path involved. The bundle lists Linux 6.7, 6.7.6, and 6.8 as affected, but exact downstream distro exposure requires vendor kernel backport verification.

Exploitation context

No active exploitation is supported by the provided sources, and the CVE is not marked KEV. The available description indicates a resource-management flaw, not a published remote attack path. Impact evidence is incomplete.

Researcher notes

The source evidence is narrow: it documents buffer lifetime cleanup in nouveau, but not exploitability, attacker prerequisites, or downstream vendor status. Avoid extrapolating beyond kernel versions and commits cited in the CVE bundle.

Mitigation direction

  • Apply Linux kernel updates that include the referenced stable fixes.
  • Check distribution security advisories for backported nouveau patches.
  • Prioritize systems using NVIDIA GPUs with the nouveau driver enabled.
  • If no vendor patch is available, follow vendor guidance for temporary risk reduction.

Validation and detection

  • Inventory Linux kernel versions against vendor-fixed package versions.
  • Confirm whether nouveau is present and used on relevant systems.
  • Review kernel package changelogs for the referenced stable commits.
  • Track vendor advisories because the source bundle lacks CVSS and impact detail.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26912 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux176fdcbddfd288408ce8571c1760ad618d962096, 176fdcbddfd288408ce8571c1760ad618d962096unaffected
LinuxLinux6.7, 0, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.