LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43104: drm/vc4: Fix a memory leak in hang state error path

In the Linux kernel, the following vulnerability has been resolved: drm/vc4: Fix a memory leak in hang state error path When vc4_save_hang_state() encounters an early return condition, it returns without freeing the previously allocated `kernel_state`, leaking memory. Add the missing kfree() calls by consolidating the early return paths into a single place.

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 memory leak in the vc4 graphics driver error path. If a hang-state save operation exits early, allocated kernel memory is not freed. The public record does not provide CVSS, exploitation evidence, or business-impact details, so urgency should be based on asset exposure and vendor kernel guidance.

Executive priority

Treat as a targeted kernel maintenance item, not a confirmed emergency. Patch through normal kernel update processes, with higher priority for exposed fleets using affected vc4 graphics paths. The absence of CVSS and exploitation evidence limits urgency confidence.

Technical view

CVE-2026-43104 affects Linux kernel drm/vc4 code. The described flaw is missing kfree() handling for kernel_state in vc4_save_hang_state() early returns. The fix consolidates early returns so cleanup occurs. Public sources identify stable kernel commits but do not describe privilege requirements, triggerability, or exploitability.

Likely exposure

Likely limited to Linux systems running affected kernels with the vc4 DRM code present and reachable. The source bundle lists Linux as affected but provides incomplete operational context, so exposure should be confirmed against kernel version, downstream vendor kernel patches, and whether vc4 is enabled.

Exploitation context

No active exploitation is supported by the supplied evidence. The CVE is not marked KEV, and the source bundle contains no reports of public exploitation or weaponized use. The known impact from the provided description is memory leakage on an error path.

Researcher notes

The public record is sparse: no CWE, CVSS, privilege model, or trigger detail is provided. Analysis should focus on the vc4_save_hang_state() cleanup change and downstream backport status. Do not infer denial-of-service exploitability beyond the documented memory leak.

Mitigation direction

  • Apply the relevant Linux stable kernel fix from your distribution or kernel vendor.
  • Prioritize systems where vc4 DRM is enabled or graphics hang handling is relevant.
  • Track downstream advisories for packaged kernel backports and release notes.
  • Avoid direct wrangler or deployment actions unrelated to kernel remediation.
  • If no vendor package exists, follow official kernel stable guidance.

Validation and detection

  • Inventory Linux kernel versions and downstream package build identifiers.
  • Check whether drm/vc4 support is enabled, loaded, or compiled into deployed kernels.
  • Map installed kernels to the referenced stable commits or vendor backports.
  • Review vendor advisories for fixed package versions and reboot requirements.
  • Confirm no unsupported custom kernel remains in production.
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-2026-43104 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
LinuxLinux214613656b5179f0daab6e0a080814b5100d45f0, 214613656b5179f0daab6e0a080814b5100d45f0, 214613656b5179f0daab6e0a080814b5100d45f0, 214613656b5179f0daab6e0a080814b5100d45f0, 214613656b5179f0daab6e0a080814b5100d45f0, 214613656b5179f0daab6e0a080814b5100d45f0, 214613656b5179f0daab6e0a080814b5100d45f0, 214613656b5179f0daab6e0a080814b5100d45f0unaffected
LinuxLinux4.5, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0affected
Weakness

CWE details

No CWE listed

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