LiveActive security incident?Get immediate response
CVE Record

CVE-2024-43867: drm/nouveau: prime: fix refcount underflow

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: prime: fix refcount underflow Calling nouveau_bo_ref() on a nouveau_bo without initializing it (and hence the backing ttm_bo) leads to a refcount underflow. Instead of calling nouveau_bo_ref() in the unwind path of drm_gem_object_init(), clean things up manually. (cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)

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-43867 is a Linux kernel Nouveau graphics driver flaw involving incorrect cleanup after an initialization failure. The public record says it can cause a reference-count underflow. Business urgency depends on whether affected kernels run with Nouveau graphics support, especially on NVIDIA GPU systems.

Executive priority

Treat as a kernel patch-management item, not an emergency from the supplied evidence. Prioritize affected Linux desktop, workstation, and GPU systems, then fold remaining exposure into the next controlled kernel maintenance cycle.

Technical view

The issue is in drm/nouveau PRIME handling. Calling nouveau_bo_ref() before the nouveau_bo and backing ttm_bo are initialized can underflow a reference count during drm_gem_object_init() unwind. Linux stable commits fix the cleanup path by handling teardown manually instead of using nouveau_bo_ref().

Likely exposure

Exposure is most likely on Linux systems using affected kernel builds with the Nouveau DRM driver available or loaded. Servers without NVIDIA graphics or without Nouveau in use are less likely to be exposed, but distro backport status must be checked.

Exploitation context

The provided sources do not report active exploitation, public exploit availability, attacker prerequisites, or practical impact beyond the kernel refcount underflow. The CVE is not listed as KEV in the supplied bundle.

Researcher notes

The record lacks CVSS, CWE, and detailed impact analysis. Focus validation on Nouveau code presence, kernel version lineage, and distro backport advisories. Avoid assuming privilege escalation, denial of service, or exploitability without additional vendor or researcher evidence.

Mitigation direction

  • Update to Linux or distro kernels containing the referenced stable fixes.
  • Review Debian LTS advisories if running affected Debian kernel packages.
  • Check vendor kernel advisories for backported fixes and package-specific status.
  • Prioritize systems using Nouveau with NVIDIA graphics or GPU-enabled workloads.

Validation and detection

  • Inventory Linux hosts with affected kernel versions or vendor kernel packages.
  • Confirm whether the Nouveau DRM driver is present or loaded on those hosts.
  • Verify installed kernels include the referenced stable fix or distro backport.
  • Track remediation through normal kernel patch compliance reporting.
Prepared
Confidence
medium
Sources
11

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-43867 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
10Source 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
LinuxLinuxab9ccb96a6e6f95bcde6b8b2a524370efdbfdcd6, ab9ccb96a6e6f95bcde6b8b2a524370efdbfdcd6, ab9ccb96a6e6f95bcde6b8b2a524370efdbfdcd6, ab9ccb96a6e6f95bcde6b8b2a524370efdbfdcd6, ab9ccb96a6e6f95bcde6b8b2a524370efdbfdcd6, ab9ccb96a6e6f95bcde6b8b2a524370efdbfdcd6, ab9ccb96a6e6f95bcde6b8b2a524370efdbfdcd6unaffected
LinuxLinux3.9, 0, 5.4.282, 5.10.224, 5.15.165, 6.1.104, 6.6.45, 6.10.4, 6.11affected
Weakness

CWE details

No CWE listed

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