LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26833: drm/amd/display: Fix memory leak in dm_sw_fini()

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak in dm_sw_fini() After destroying dmub_srv, the memory associated with it is not freed, causing a memory leak: unreferenced object 0xffff896302b45800 (size 1024): comm "(udev-worker)", pid 222, jiffies 4294894636 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 6265fd77): [<ffffffff993495ed>] kmalloc_trace+0x29d/0x340 [<ffffffffc0ea4a94>] dm_dmub_sw_init+0xb4/0x450 [amdgpu] [<ffffffffc0ea4e55>] dm_sw_init+0x15/0x2b0 [amdgpu] [<ffffffffc0ba8557>] amdgpu_device_init+0x1417/0x24e0 [amdgpu] [<ffffffffc0bab285>] amdgpu_driver_load_kms+0x15/0x190 [amdgpu] [<ffffffffc0ba09c7>] amdgpu_pci_probe+0x187/0x4e0 [amdgpu] [<ffffffff9968fd1e>] local_pci_probe+0x3e/0x90 [<ffffffff996918a3>] pci_device_probe+0xc3/0x230 [<ffffffff99805872>] really_probe+0xe2/0x480 [<ffffffff99805c98>] __driver_probe_device+0x78/0x160 [<ffffffff99805daf>] driver_probe_device+0x1f/0x90 [<ffffffff9980601e>] __driver_attach+0xce/0x1c0 [<ffffffff99803170>] bus_for_each_dev+0x70/0xc0 [<ffffffff99804822>] bus_add_driver+0x112/0x210 [<ffffffff99807245>] driver_register+0x55/0x100 [<ffffffff990012d1>] do_one_initcall+0x41/0x300 Fix this by freeing dmub_srv after destroying it.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2024-26833 is a Linux kernel AMD display driver cleanup bug. Memory allocated for dmub_srv is destroyed but not freed, causing a kernel memory leak. The sources do not show remote exploitation, privilege escalation, or data exposure. Treat it mainly as a stability and maintenance issue for affected Linux systems using AMDGPU display support.

Executive priority

Handle in the normal kernel patch cycle unless AMDGPU systems show instability or repeated driver reloads. There is no cited active exploitation, but kernel memory leaks can still affect reliability and should not remain unpatched indefinitely.

Technical view

The vulnerability is in drm/amd/display dm_sw_fini(). After dmub_srv is destroyed, its allocated memory remains referenced only by the leak detector path. The upstream fix frees dmub_srv after destruction. Affected entries include Linux kernel versions around 5.6 through fixed stable releases including 5.10.211, 5.15.150, 6.1.80, 6.6.19, 6.7.7, and 6.8.

Likely exposure

Exposure is most likely on Linux systems with AMDGPU display driver support running affected kernel builds. Systems without AMD GPUs, without the amdgpu driver, or already on vendor-fixed kernels are less likely exposed. The bundle does not provide distribution-specific status beyond a Debian LTS advisory reference.

Exploitation context

The provided sources do not report active exploitation, a public exploit, or CISA KEV listing. The described issue is a memory leak during AMDGPU driver initialization and cleanup paths, not a documented remote attack path. Practical security impact is unclear from available evidence.

Researcher notes

Evidence is limited to the CVE text, upstream stable commits, and a Debian LTS advisory reference. No CVSS, CWE, exploitability analysis, or detailed affected distribution matrix is included. Do not infer broader AMD product exposure beyond Linux AMDGPU display code.

Mitigation direction

  • Update Linux kernels through the operating system vendor’s supported security channel.
  • Prioritize systems with AMD GPUs or active AMDGPU display driver usage.
  • Review vendor advisories for exact fixed package versions and reboot requirements.
  • Avoid direct kernel deployment shortcuts outside normal change control.
  • Track Debian LTS guidance where Debian systems are in scope.

Validation and detection

  • Inventory Linux kernel versions across systems with AMD GPUs.
  • Check whether the amdgpu module is present or loaded.
  • Compare installed kernels against vendor-fixed release notes and advisories.
  • Confirm updated systems boot into the patched kernel after maintenance.
  • Monitor kernel logs for recurring amdgpu initialization or leak warnings.
Prepared
Confidence
medium
Sources
9

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-2024-26833 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
8Source 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux743b9786b14ae0d7d13b3782dccad158e577e9bb, 743b9786b14ae0d7d13b3782dccad158e577e9bb, 743b9786b14ae0d7d13b3782dccad158e577e9bb, 743b9786b14ae0d7d13b3782dccad158e577e9bb, 743b9786b14ae0d7d13b3782dccad158e577e9bb, 743b9786b14ae0d7d13b3782dccad158e577e9bbunaffected
LinuxLinux5.6, 0, 5.10.211, 5.15.150, 6.1.80, 6.6.19, 6.7.7, 6.8affected
Weakness

CWE details

No CWE listed

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