LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54091: drm/client: Fix memory leak in drm_client_target_cloned

In the Linux kernel, the following vulnerability has been resolved: drm/client: Fix memory leak in drm_client_target_cloned dmt_mode is allocated and never freed in this function. It was found with the ast driver, but most drivers using generic fbdev setup are probably affected. This fixes the following kmemleak report: backtrace: [<00000000b391296d>] drm_mode_duplicate+0x45/0x220 [drm] [<00000000e45bb5b3>] drm_client_target_cloned.constprop.0+0x27b/0x480 [drm] [<00000000ed2d3a37>] drm_client_modeset_probe+0x6bd/0xf50 [drm] [<0000000010e5cc9d>] __drm_fb_helper_initial_config_and_unlock+0xb4/0x2c0 [drm_kms_helper] [<00000000909f82ca>] drm_fbdev_client_hotplug+0x2bc/0x4d0 [drm_kms_helper] [<00000000063a69aa>] drm_client_register+0x169/0x240 [drm] [<00000000a8c61525>] ast_pci_probe+0x142/0x190 [ast] [<00000000987f19bb>] local_pci_probe+0xdc/0x180 [<000000004fca231b>] work_for_cpu_fn+0x4e/0xa0 [<0000000000b85301>] process_one_work+0x8b7/0x1540 [<000000003375b17c>] worker_thread+0x70a/0xed0 [<00000000b0d43cd9>] kthread+0x29f/0x340 [<000000008d770833>] ret_from_fork+0x1f/0x30 unreferenced object 0xff11000333089a00 (size 128):

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-54091 is a Linux kernel graphics memory leak. A display mode object can be allocated and not freed during DRM client setup. The source reports it was found with the ast driver and may affect many drivers using generic fbdev setup. No CVSS score or active exploitation evidence is provided.

Executive priority

Treat as a patch-management item unless your environment depends heavily on affected Linux graphics paths. Business risk is unclear from public data because severity, CVSS, and exploitation details are absent.

Technical view

The issue is in drm_client_target_cloned, where dmt_mode from drm_mode_duplicate is not freed. The cited kmemleak trace reaches drm_client_modeset_probe and drm_fbdev_client_hotplug during ast_pci_probe. Linux stable commits are listed as references for the resolution across affected kernel lines.

Likely exposure

Exposure is most relevant for Linux systems running affected kernel versions with DRM/KMS graphics paths, especially ast or other drivers using generic fbdev setup. The bundle lists multiple affected kernel series, but distro backport status is not provided.

Exploitation context

The source evidence describes a kernel memory leak found by kmemleak. It does not describe remote attackability, privilege requirements, denial-of-service conditions, public exploit code, or active exploitation. KEV status is false.

Researcher notes

The useful lead is the unresolved allocation lifetime in drm_client_target_cloned. The ast trace is evidence of discovery, not proof that only ast is affected. Do not infer exploitability beyond memory leakage without additional kernel analysis.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced Linux stable fix.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • Prioritize systems using ast or generic fbdev-based DRM drivers.
  • If patching is delayed, follow vendor guidance for operational mitigations.

Validation and detection

  • Inventory Linux kernel versions and vendor patch levels across exposed systems.
  • Identify systems using DRM/KMS graphics and generic fbdev setup paths.
  • Confirm whether the relevant stable commit is included in the deployed kernel source package.
  • Review kernel or QA logs for kmemleak reports matching the described DRM stack.
Prepared
Confidence
medium
Sources
10

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-2023-54091 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
9Source 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
LinuxLinux1d42bbc8f7f9ce4d852692ef7aa336b133b0830a, 1d42bbc8f7f9ce4d852692ef7aa336b133b0830a, 1d42bbc8f7f9ce4d852692ef7aa336b133b0830a, 1d42bbc8f7f9ce4d852692ef7aa336b133b0830a, 1d42bbc8f7f9ce4d852692ef7aa336b133b0830a, 1d42bbc8f7f9ce4d852692ef7aa336b133b0830a, 1d42bbc8f7f9ce4d852692ef7aa336b133b0830a, 1d42bbc8f7f9ce4d852692ef7aa336b133b0830aunaffected
LinuxLinux2.6.35, 0, 4.14.322, 4.19.291, 5.4.251, 5.10.188, 5.15.123, 6.1.42, 6.4.7, 6.5affected
Weakness

CWE details

No CWE listed

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