LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50556: drm: Fix potential null-ptr-deref due to drmm_mode_config_init()

In the Linux kernel, the following vulnerability has been resolved: drm: Fix potential null-ptr-deref due to drmm_mode_config_init() drmm_mode_config_init() will call drm_mode_create_standard_properties() and won't check the ret value. When drm_mode_create_standard_properties() failed due to alloc, property will be a NULL pointer and may causes the null-ptr-deref. Fix the null-ptr-deref by adding the ret value check. Found null-ptr-deref while testing insert module bochs: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] CPU: 3 PID: 249 Comm: modprobe Not tainted 6.1.0-rc1+ #364 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 RIP: 0010:drm_object_attach_property+0x73/0x3c0 [drm] Call Trace: <TASK> __drm_connector_init+0xb6c/0x1100 [drm] bochs_pci_probe.cold.11+0x4cb/0x7fe [bochs] pci_device_probe+0x17d/0x340 really_probe+0x1db/0x5d0 __driver_probe_device+0x1e7/0x250 driver_probe_device+0x4a/0x120 __driver_attach+0xcd/0x2c0 bus_for_each_dev+0x11a/0x1b0 bus_add_driver+0x3d7/0x500 driver_register+0x18e/0x320 do_one_initcall+0xc4/0x3e0 do_init_module+0x1b4/0x630 load_module+0x5dca/0x7230 __do_sys_finit_module+0x100/0x170 do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7ff65af9f839

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel graphics subsystem bug where a failed memory allocation can lead to a kernel crash path. Business impact is primarily availability on affected Linux systems using DRM graphics drivers. The supplied sources do not provide a CVSS score or evidence of active exploitation.

Executive priority

Treat as a patch-management item for Linux availability risk, not as confirmed active exploitation. Prioritize internet-facing infrastructure less than exposed critical workloads, unless local module loading or graphics driver instability affects service reliability.

Technical view

drmm_mode_config_init() called drm_mode_create_standard_properties() without checking its return value. If allocation failed, a later DRM connector path could dereference a NULL property pointer in drm_object_attach_property(). The source reports the crash while loading the bochs DRM module under KASAN/QEMU.

Likely exposure

Exposure appears limited to affected Linux kernel versions or unpatched downstream kernels using the DRM mode configuration path. The bundle lists Linux 4.0 through fixed stable version boundaries including 5.10.173, 5.15.99, 6.1.16, 6.2.3, and 6.3, but operational exposure depends on vendor backports.

Exploitation context

The source bundle describes a discovered null-pointer dereference during module insertion testing. It does not cite KEV listing, public exploitation, weaponized proof of concept, privilege impact, or remote attack conditions.

Researcher notes

Evidence is narrow: the CVE text names an unchecked allocation failure in DRM setup and shows a KASAN trace via bochs module probing. No CVSS, CWE, exploitability analysis, or distribution-specific advisories are included in the bundle.

Mitigation direction

  • Check vendor kernel advisories for the relevant distribution and kernel branch.
  • Update to a kernel containing the referenced stable fixes or vendor backport.
  • Prioritize systems where DRM drivers or module loading are in use.
  • Track kernel crash telemetry for DRM connector initialization faults.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Confirm whether vendor kernels include the referenced stable commits or backports.
  • Review dmesg or crash logs for drm_object_attach_property NULL dereference traces.
  • Verify graphics or virtual-display drivers using DRM mode configuration are present.
Prepared
Confidence
medium
Sources
7

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-50556 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
0ADP providers
6Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6b4959f43a04e12d39c5700607727f2cbcfeac31, 6b4959f43a04e12d39c5700607727f2cbcfeac31, 6b4959f43a04e12d39c5700607727f2cbcfeac31, 6b4959f43a04e12d39c5700607727f2cbcfeac31, 6b4959f43a04e12d39c5700607727f2cbcfeac31unaffected
LinuxLinux4.0, 0, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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