LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43105: drm/vc4: Fix memory leak of BO array in hang state

In the Linux kernel, the following vulnerability has been resolved: drm/vc4: Fix memory leak of BO array in hang state The hang state's BO array is allocated separately with kzalloc() in vc4_save_hang_state() but never freed in vc4_free_hang_state(). Add the missing kfree() for the BO array before freeing the hang state struct.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-43105 is a Linux kernel memory leak in the VC4 graphics driver hang-state cleanup path. It concerns missing cleanup of a separately allocated buffer-object array. Business impact is currently unclear, but the plausible concern is resource exhaustion on systems using affected kernels with VC4 graphics support.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize systems using VC4 graphics support and fold remediation into normal kernel update cycles unless vendor guidance raises severity.

Technical view

The issue is in drm/vc4. vc4_save_hang_state() allocates a BO array with kzalloc(), but vc4_free_hang_state() did not free it. The kernel fix adds the missing kfree() before freeing the hang-state structure. Sources do not provide CVSS, CWE, or detailed attack prerequisites.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds with the VC4 DRM graphics driver present or enabled, commonly associated with Broadcom/Raspberry Pi graphics stacks. Exact exposure depends on downstream kernel packaging and whether the stable fix commits are included.

Exploitation context

The provided sources do not report active exploitation, public exploit availability, or KEV listing. They describe a memory leak fixed in Linux stable commits. No source in the bundle establishes remote reachability, privilege requirements, or a confirmed denial-of-service scenario.

Researcher notes

Evidence is limited to the CVE description and upstream stable commit references. The bug is a leak in hang-state cleanup, but the bundle does not document trigger conditions, reachable interfaces, impact magnitude, or affected downstream distributions.

Mitigation direction

  • Check whether deployed kernels include the referenced Linux stable fix commits.
  • Prioritize kernel updates from your OS or device vendor.
  • Track vendor advisories for affected package versions and fixed builds.
  • Reduce exposure by disabling unused VC4 graphics support where operationally acceptable.

Validation and detection

  • Inventory Linux kernel versions on systems using VC4 graphics hardware or drivers.
  • Compare kernel source or package changelogs against the listed stable commit references.
  • Confirm whether CONFIG_DRM_VC4 is enabled in relevant kernels.
  • Review vendor advisories for backported fixes not visible in upstream version numbers.
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-43105 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.