LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47423: drm/nouveau/debugfs: fix file release memory leak

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/debugfs: fix file release memory leak When using single_open() for opening, single_release() should be called, otherwise the 'op' allocated in single_open() will be leaked.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak in the Nouveau graphics driver's debugfs handling. When a debugfs file is opened through single_open(), the matching release path was not used, leaking a small allocation. The sources do not provide CVSS, impact scoring, or evidence of active exploitation.

Executive priority

Handle through normal kernel patch management. There is no supplied evidence of active exploitation or severe business impact, but kernel resource leaks should still be remediated during scheduled maintenance.

Technical view

CVE-2021-47423 affects Linux drm/nouveau/debugfs code. The bug is a file release mismatch: single_open() allocates state, but the code did not call single_release(), leaving the allocated operation data leaked on close. Upstream stable commits resolve the issue.

Likely exposure

Exposure is most likely on systems running affected Linux kernel versions with Nouveau DRM debugfs functionality present. The provided sources do not define required privileges, debugfs access conditions, or distribution-specific package status.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not claim active exploitation, public exploit availability, privilege escalation, or remote attack paths. Treat it as a kernel resource-leak issue unless vendor advisories say otherwise.

Researcher notes

The source bundle identifies the root cause and stable fix references, but lacks CVSS, CWE, exploitability analysis, and access prerequisites. Validation should focus on kernel lineage, vendor backports, and whether Nouveau debugfs code is reachable in the local configuration.

Mitigation direction

  • Upgrade to a vendor kernel containing the referenced upstream stable fix.
  • Confirm distro backport status before assuming version numbers are vulnerable or fixed.
  • Prioritize internet-facing or multi-user Linux fleets after higher-impact kernel flaws.
  • Review vendor guidance for any supported operational mitigations.

Validation and detection

  • Inventory Linux hosts and kernel versions across managed assets.
  • Identify systems using Nouveau DRM or exposing debugfs functionality.
  • Check installed kernels against vendor advisories and upstream stable references.
  • Confirm patched systems booted into the updated kernel.
Prepared
Confidence
medium
Sources
9

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-2021-47423 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
8Source 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
LinuxLinux6e9fc177399f08446293fec7607913fdbc95e191, 6e9fc177399f08446293fec7607913fdbc95e191, 6e9fc177399f08446293fec7607913fdbc95e191, 6e9fc177399f08446293fec7607913fdbc95e191, 6e9fc177399f08446293fec7607913fdbc95e191, 6e9fc177399f08446293fec7607913fdbc95e191, 6e9fc177399f08446293fec7607913fdbc95e191unaffected
LinuxLinux4.5, 0, 4.9.287, 4.14.251, 4.19.211, 5.4.153, 5.10.73, 5.14.12, 5.15affected
Weakness

CWE details

No CWE listed

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