LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47280: drm: Fix use-after-free read in drm_getunique()

In the Linux kernel, the following vulnerability has been resolved: drm: Fix use-after-free read in drm_getunique() There is a time-of-check-to-time-of-use error in drm_getunique() due to retrieving file_priv->master prior to locking the device's master mutex. An example can be seen in the crash report of the use-after-free error found by Syzbot: https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803 In the report, the master pointer was used after being freed. This is because another process had acquired the device's master mutex in drm_setmaster_ioctl(), then overwrote fpriv->master in drm_new_set_master(). The old value of fpriv->master was subsequently freed before the mutex was unlocked. To fix this, we lock the device's master mutex before retrieving the pointer from from fpriv->master. This patch passes the Syzbot reproducer test.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-47280 is a Linux kernel DRM bug where one process can trigger a stale pointer read while another changes graphics device master state. The public record shows a kernel fix and Syzbot crash evidence, but no CVSS score or active exploitation signal.

Executive priority

Schedule normal-priority remediation unless exposed systems are multi-user, GPU-shared, or host untrusted workloads. There is no cited active exploitation, but kernel memory safety bugs deserve timely patching because impact can exceed the visible crash symptom.

Technical view

The flaw is a time-of-check-to-time-of-use issue in drm_getunique(). file_priv->master was retrieved before taking the device master mutex. A concurrent drm_setmaster_ioctl() path could replace and free that master pointer, producing a use-after-free read. The fix locks the mutex before reading fpriv->master.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with DRM device access available to local processes. The source does not indicate remote exposure. Distro kernels may be patched through backports even when version strings appear affected.

Exploitation context

The evidence is Syzbot finding and a kernel crash report, not confirmed real-world exploitation. The CVE is not marked KEV. Treat this as a local kernel stability and potential security issue until vendor kernel status is confirmed.

Researcher notes

Key uncertainty is impact: sources document a use-after-free read and Syzbot reproducer success after the patch, but provide no CVSS, CWE, privilege requirement, or exploitability assessment. Validate against vendor backports rather than relying only on upstream version numbers.

Mitigation direction

  • Update to a kernel carrying the referenced DRM fixes or your distribution's backport.
  • Check vendor advisories for your exact distribution kernel package.
  • Limit untrusted local access to DRM device nodes where operationally feasible.
  • Prioritize shared workstations, GPU-enabled servers, and multi-user Linux hosts.
  • Track kernel package rollout through normal vulnerability management.

Validation and detection

  • Inventory Linux kernel versions across endpoints, servers, and GPU-enabled workloads.
  • Confirm whether vendor kernels include the referenced stable commits or equivalent backports.
  • Identify systems exposing DRM devices to untrusted local users or containers.
  • Review crash telemetry for DRM-related use-after-free reports.
  • Run non-offensive kernel regression testing after patch deployment.
Prepared
Confidence
medium
Sources
8

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-47280 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
7Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5acc614ac47465fee6375a9af4740f618830762d, 5acc614ac47465fee6375a9af4740f618830762d, 5acc614ac47465fee6375a9af4740f618830762d, 5acc614ac47465fee6375a9af4740f618830762d, 5acc614ac47465fee6375a9af4740f618830762d, 5acc614ac47465fee6375a9af4740f618830762dunaffected
LinuxLinux4.11, 0, 4.14.237, 4.19.195, 5.4.126, 5.10.44, 5.12.11, 5.13affected
Weakness

CWE details

No CWE listed

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