LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50884: drm: Prevent drm_copy_field() to attempt copying a NULL pointer

In the Linux kernel, the following vulnerability has been resolved: drm: Prevent drm_copy_field() to attempt copying a NULL pointer There are some struct drm_driver fields that are required by drivers since drm_copy_field() attempts to copy them to user-space via DRM_IOCTL_VERSION. But it can be possible that a driver has a bug and did not set some of the fields, which leads to drm_copy_field() attempting to copy a NULL pointer: [ +10.395966] Unable to handle kernel access to user memory outside uaccess routines at virtual address 0000000000000000 [ +0.010955] Mem abort info: [ +0.002835] ESR = 0x0000000096000004 [ +0.003872] EC = 0x25: DABT (current EL), IL = 32 bits [ +0.005395] SET = 0, FnV = 0 [ +0.003113] EA = 0, S1PTW = 0 [ +0.003182] FSC = 0x04: level 0 translation fault [ +0.004964] Data abort info: [ +0.002919] ISV = 0, ISS = 0x00000004 [ +0.003886] CM = 0, WnR = 0 [ +0.003040] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000115dad000 [ +0.006536] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 [ +0.006925] Internal error: Oops: 96000004 [#1] SMP ... [ +0.011113] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ +0.007061] pc : __pi_strlen+0x14/0x150 [ +0.003895] lr : drm_copy_field+0x30/0x1a4 [ +0.004156] sp : ffff8000094b3a50 [ +0.003355] x29: ffff8000094b3a50 x28: ffff8000094b3b70 x27: 0000000000000040 [ +0.007242] x26: ffff443743c2ba00 x25: 0000000000000000 x24: 0000000000000040 [ +0.007243] x23: ffff443743c2ba00 x22: ffff8000094b3b70 x21: 0000000000000000 [ +0.007241] x20: 0000000000000000 x19: ffff8000094b3b90 x18: 0000000000000000 [ +0.007241] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaab14b9af40 [ +0.007241] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ +0.007239] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffa524ad67d4d8 [ +0.007242] x8 : 0101010101010101 x7 : 7f7f7f7f7f7f7f7f x6 : 6c6e6263606e7141 [ +0.007239] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 [ +0.007241] x2 : 0000000000000000 x1 : ffff8000094b3b90 x0 : 0000000000000000 [ +0.007240] Call trace: [ +0.002475] __pi_strlen+0x14/0x150 [ +0.003537] drm_version+0x84/0xac [ +0.003448] drm_ioctl_kernel+0xa8/0x16c [ +0.003975] drm_ioctl+0x270/0x580 [ +0.003448] __arm64_sys_ioctl+0xb8/0xfc [ +0.003978] invoke_syscall+0x78/0x100 [ +0.003799] el0_svc_common.constprop.0+0x4c/0xf4 [ +0.004767] do_el0_svc+0x38/0x4c [ +0.003357] el0_svc+0x34/0x100 [ +0.003185] el0t_64_sync_handler+0x11c/0x150 [ +0.004418] el0t_64_sync+0x190/0x194 [ +0.003716] Code: 92402c04 b200c3e8 f13fc09f 5400088c (a9400c02) [ +0.006180] ---[ end trace 0000000000000000 ]---

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50884 is a Linux kernel DRM bug where a graphics driver missing required identification fields can trigger a NULL pointer copy attempt. The documented impact is a kernel oops/crash path, not data theft or remote compromise. Business urgency depends on whether affected kernels and DRM drivers are present.

Executive priority

Treat as a stability and local denial-of-service risk. Prioritize normal kernel patch cycles, with faster action for shared Linux systems or environments where untrusted users can access graphics devices.

Technical view

The flaw is in drm_copy_field() when handling DRM_IOCTL_VERSION. If a drm_driver leaves expected fields unset, the kernel may call strlen/copy logic on a NULL pointer, causing an oops. The CVE references stable kernel commits that add a guard to prevent copying NULL fields.

Likely exposure

Exposure is most relevant on Linux systems running affected kernel versions with DRM graphics drivers accessible to local users or workloads. Distribution kernels may already include backported fixes, so version strings alone are not definitive.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. The described trigger is a local DRM ioctl path leading to kernel fault conditions when a buggy driver omits required fields. No remote attack path is documented in the source bundle.

Researcher notes

The CVE record provides no CVSS, CWE, or exploit evidence. Affected data appears kernel-version oriented, but practical exposure depends on driver behavior and distro backports. The fix is represented by multiple Linux stable commit references.

Mitigation direction

  • Check Linux distribution advisories for CVE-2022-50884 or the referenced DRM fix.
  • Update to a kernel containing the stable fix or vendor backport.
  • Prioritize multi-user systems, shared workstations, and hosts exposing DRM devices to containers.
  • If patching is delayed, review vendor guidance for limiting untrusted access to DRM devices.

Validation and detection

  • Inventory Linux kernel versions and distribution patch levels.
  • Identify systems using DRM graphics drivers and exposed DRM device nodes.
  • Check vendor changelogs for the commit title or referenced stable commit hashes.
  • Review kernel logs for oops traces mentioning drm_copy_field or DRM_IOCTL_VERSION.
  • Confirm patched kernels through vendor package metadata, not only upstream version numbers.
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-2022-50884 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
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux22eae947bf76e236ba972f2f11cfd1b083b736ad, 22eae947bf76e236ba972f2f11cfd1b083b736ad, 22eae947bf76e236ba972f2f11cfd1b083b736ad, 22eae947bf76e236ba972f2f11cfd1b083b736ad, 22eae947bf76e236ba972f2f11cfd1b083b736ad, 22eae947bf76e236ba972f2f11cfd1b083b736ad, 22eae947bf76e236ba972f2f11cfd1b083b736ad, 22eae947bf76e236ba972f2f11cfd1b083b736ad, 22eae947bf76e236ba972f2f11cfd1b083b736adunaffected
LinuxLinux2.6.16, 0, 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

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