LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47610: drm/msm: Fix null ptr access msm_ioctl_gem_submit()

In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix null ptr access msm_ioctl_gem_submit() Fix the below null pointer dereference in msm_ioctl_gem_submit(): 26545.260705: Call trace: 26545.263223: kref_put+0x1c/0x60 26545.266452: msm_ioctl_gem_submit+0x254/0x744 26545.270937: drm_ioctl_kernel+0xa8/0x124 26545.274976: drm_ioctl+0x21c/0x33c 26545.278478: drm_compat_ioctl+0xdc/0xf0 26545.282428: __arm64_compat_sys_ioctl+0xc8/0x100 26545.287169: el0_svc_common+0xf8/0x250 26545.291025: do_el0_svc_compat+0x28/0x54 26545.295066: el0_svc_compat+0x10/0x1c 26545.298838: el0_sync_compat_handler+0xa8/0xcc 26545.303403: el0_sync_compat+0x188/0x1c0 26545.307445: Code: d503201f d503201f 52800028 4b0803e8 (b8680008) 26545.318799: Kernel panic - not syncing: Oops: Fatal exception

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash the kernel through a null pointer dereference in the MSM DRM graphics submit path. The business impact is primarily availability: affected systems may panic if the vulnerable code path is reached. The provided sources do not report active exploitation or a CVSS score.

Executive priority

Treat this as a targeted availability issue, not a broadly proven remote compromise. Prioritize patching for Linux devices using MSM DRM graphics, especially production systems where a kernel panic creates operational downtime.

Technical view

CVE-2021-47610 is a resolved null pointer dereference in msm_ioctl_gem_submit() under drm/msm. The source trace shows the crash through DRM ioctl handling, including compat ioctl on arm64, ending in kernel panic. Fixed stable kernel commits are referenced, but no CWE, CVSS, or detailed affected distribution list is provided.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel builds with the drm/msm driver path present and reachable. The bundle lists Linux kernel versions including 3.12, 5.15.10, and 5.16 as affected, but does not provide distro-specific package mapping.

Exploitation context

No provided source states active exploitation, and KEV is false. The available evidence supports a local availability risk through DRM ioctl handling rather than remote compromise. Exploitability details, prerequisites, and privilege requirements are not fully documented in the supplied bundle.

Researcher notes

The source evidence is concise: a crash trace, fix title, affected version entries, and two stable commit references. There is not enough supplied detail to assign precise privilege requirements, affected downstream products, or exploit maturity beyond no KEV listing.

Mitigation direction

  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Check Linux distribution or device vendor advisories for mapped fixed package versions.
  • Prioritize systems where drm/msm graphics support is enabled or exposed to users.
  • Use vendor-supported kernels rather than manually carrying partial patches.

Validation and detection

  • Inventory Linux kernel versions against the CVE record and vendor advisories.
  • Confirm whether the drm/msm driver is present in affected system builds.
  • Verify that kernel packages include the referenced stable fix commits.
  • Review crash logs for kernel panics involving msm_ioctl_gem_submit().
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-2021-47610 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
LinuxLinux0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300, 0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300unaffected
LinuxLinux3.12, 0, 5.15.10, 5.16affected
Weakness

CWE details

No CWE listed

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