In the Linux kernel, the following vulnerability has been resolved:
drm/nouveau/kms/nv50-: 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.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the nouveau graphics driver. When a specific file-open helper is used, the matching release cleanup was not called, leaking allocated memory. The business risk appears limited, but affected Linux systems using nouveau should receive the relevant stable kernel fix through normal patch channels.
Executive priority
Handle through routine kernel patch management unless nouveau-dependent Linux systems are mission-critical or difficult to reboot. There is no cited evidence of active exploitation or high-impact compromise behavior.
Technical view
The issue is in drm/nouveau/kms/nv50-. Code using single_open() failed to call single_release(), leaking the operation structure allocated during open. The CVE record lists affected Linux kernel versions including 5.9, 5.10.73, 5.14.12, and 5.15, with fixes referenced in Linux stable commits.
Likely exposure
Exposure is likely limited to Linux systems running affected kernels with the nouveau DRM/KMS driver in use. The provided sources do not identify affected distributions, packaged kernel ranges, or non-Linux products.
Exploitation context
The source bundle does not report active exploitation, and CISA KEV status is false. The available evidence describes a memory leak, not privilege escalation, remote code execution, or data disclosure. Practical abuse conditions are not documented in the provided sources.
Researcher notes
Evidence is narrow: the CVE text and stable commits describe a missing single_release() after single_open(). No CVSS, CWE, exploit details, affected distribution packages, or operational mitigations are provided in the source bundle.
Mitigation direction
Update to a Linux kernel containing the referenced stable fixes.
Use distribution kernel updates when available instead of manual patching.
Prioritize Linux hosts using the nouveau DRM/KMS driver.
Track vendor advisories for backported fixes and package-specific status.
Check Linux stable guidance if no packaged fix is available.
Validation and detection
Inventory Linux kernel versions across affected systems.
Check whether the nouveau driver is loaded or required.
Verify the installed kernel includes a referenced fix or vendor backport.
Confirm distribution advisories map local packages to fixed kernels.
Monitor for unusual memory growth on systems awaiting patching.
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-47422 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.