LiveActive security incident?Get immediate response
CVE Record

CVE-2026-64050: drm/msm/dpu: don't mix devm and drmm functions

In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: don't mix devm and drmm functions Mixing devm and drmm functions will result in a use-after-free on msm driver teardown if userspace keeps a reference on the drm device: The WB connector data will be destroyed because of the use of devm_kzalloc()), while the usersoace still can try interacting with the WB connector (which uses drmm_ functions). Change dpu_writeback_init() to use drmm_. Patchwork: https://patchwork.freedesktop.org/patch/722656/

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-64050 is a Linux kernel flaw in the msm DPU display driver cleanup path. A local low-privileged user could potentially trigger use-after-free behavior during driver teardown, risking kernel-level confidentiality, integrity, and availability impact. The sources identify kernel fixes but do not show active exploitation.

Executive priority

Treat as high priority for Linux endpoints or devices with exposed local user access and affected display drivers. It is not currently evidenced as internet-exploitable or actively exploited, but kernel use-after-free impact justifies timely remediation.

Technical view

The issue occurs because drm/msm/dpu mixed devm-managed and drmm-managed lifetimes. WB connector data allocated with devm_kzalloc() could be freed while userspace still holds a DRM device reference, leaving later connector interaction exposed to use-after-free. The fix changes dpu_writeback_init() to use drmm-managed allocation consistently.

Likely exposure

Exposure is most likely on Linux systems running affected kernels with the drm/msm/dpu driver enabled or loaded. The provided version data references affected Linux kernel lines including 6.18, 6.18.34, 7.0.11, and 7.1, but distro package mapping requires vendor verification.

Exploitation context

The CVSS vector is local, low complexity, low privileges, and no user interaction. The CVE is not marked KEV, and the provided sources do not report active exploitation or public exploit availability.

Researcher notes

Key uncertainty is affected-version normalization: the source bundle lists commits and kernel versions but no distro-specific package names. Analysis should focus on the msm DPU writeback connector lifetime mismatch and whether downstream kernels carried the vulnerable allocation pattern.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported kernel package status.
  • Prioritize systems where untrusted local users can access affected graphics devices.
  • Limit local account access on shared systems until patched.
  • Track vendor guidance if your kernel is custom or downstream-patched.

Validation and detection

  • Inventory kernel versions and compare against vendor fixed packages.
  • Confirm whether the drm/msm/dpu driver is built, loaded, or reachable.
  • Verify patched kernels include the referenced stable commits or equivalent backports.
  • Review logs for unexpected DRM driver teardown or graphics subsystem crashes.
Prepared
Confidence
medium
Sources
6

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-64050 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-64050Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0b37ac63fc9db7779168ad18d7e6e8ab9df6a40b, 0b37ac63fc9db7779168ad18d7e6e8ab9df6a40b, 0b37ac63fc9db7779168ad18d7e6e8ab9df6a40bunaffected
LinuxLinux6.18, 0, 6.18.34, 7.0.11, 7.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.