LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49830: drm/drv: Fix potential memory leak in drm_dev_init()

In the Linux kernel, the following vulnerability has been resolved: drm/drv: Fix potential memory leak in drm_dev_init() drm_dev_init() will add drm_dev_init_release() as a callback. When drmm_add_action() failed, the release function won't be added. As the result, the ref cnt added by device_get() in drm_dev_init() won't be put by drm_dev_init_release(), which leads to the memleak. Use drmm_add_action_or_reset() instead of drmm_add_action() to prevent memleak. unreferenced object 0xffff88810bc0c800 (size 2048): comm "modprobe", pid 8322, jiffies 4305809845 (age 15.292s) hex dump (first 32 bytes): e8 cc c0 0b 81 88 ff ff ff ff ff ff 00 00 00 00 ................ 20 24 3c 0c 81 88 ff ff 18 c8 c0 0b 81 88 ff ff $<............. backtrace: [<000000007251f72d>] __kmalloc+0x4b/0x1c0 [<0000000045f21f26>] platform_device_alloc+0x2d/0xe0 [<000000004452a479>] platform_device_register_full+0x24/0x1c0 [<0000000089f4ea61>] 0xffffffffa0736051 [<00000000235b2441>] do_one_initcall+0x7a/0x380 [<0000000001a4a177>] do_init_module+0x5c/0x230 [<000000002bf8a8e2>] load_module+0x227d/0x2420 [<00000000637d6d0a>] __do_sys_finit_module+0xd5/0x140 [<00000000c99fc324>] do_syscall_64+0x3f/0x90 [<000000004d85aa77>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-49830 is a Linux kernel DRM cleanup bug that can leave memory referenced after a failed device-initialization action. The public record describes a memory leak, not remote code execution or data theft. Business urgency is mainly patch hygiene for Linux fleets, especially systems using graphics or DRM-related kernel drivers.

Executive priority

Handle through routine Linux kernel patch management unless vendor advisories identify a stronger local impact. There is no source-provided evidence of active exploitation or a remote attack path.

Technical view

In drm_dev_init(), device_get() increments a reference count. If drmm_add_action() fails, drm_dev_init_release() is not registered, so the reference is not released. The fix changes the path to use drmm_add_action_or_reset(), ensuring cleanup occurs when registration fails.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream builds containing the vulnerable DRM driver code. The bundle lists Linux kernel versions including 5.8, 5.10.156, 5.15.80, 6.0.10, and 6.1; distro backports require vendor verification.

Exploitation context

The source bundle does not show active exploitation, KEV listing, CVSS scoring, or a public exploit. The observed trigger context is module or device initialization failure, shown by a modprobe-related backtrace. Practical impact appears to be resource leakage rather than direct compromise.

Researcher notes

The weakness is a failed cleanup registration path in DRM device initialization. The CVE record gives no CWE, CVSS vector, exploitability detail, or named affected hardware. Validate by commit presence and downstream vendor backport status.

Mitigation direction

  • Check your distribution's kernel advisory for CVE-2022-49830 coverage.
  • Update to a kernel containing the referenced stable DRM fix.
  • Prioritize systems with graphics, DRM, or custom kernel driver exposure.
  • Avoid treating upstream version strings as complete distro patch status.
  • Track kernel updates through normal maintenance windows unless vendor guidance escalates urgency.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Map distro kernel packages to vendor CVE advisories or changelogs.
  • Confirm the DRM fix commit is present in source or package metadata.
  • Review kernel logs for unusual DRM initialization failures if relevant.
  • Document affected, fixed, and vendor-backported kernel package versions.
Prepared
Confidence
medium
Sources
6

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-49830 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
5Source 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
LinuxLinux2cbf7fc6718b9443ecd6261308c6348d8ffcccae, 2cbf7fc6718b9443ecd6261308c6348d8ffcccae, 2cbf7fc6718b9443ecd6261308c6348d8ffcccae, 2cbf7fc6718b9443ecd6261308c6348d8ffcccaeunaffected
LinuxLinux5.8, 0, 5.10.156, 5.15.80, 6.0.10, 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.