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… (CVE-2026-64050)
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/
AI Analysis
Technical Summary
The vulnerability in the Linux kernel drm/msm/dpu component arises from mixing devm-managed and drmm-managed memory functions. Specifically, devm_kzalloc() was used to allocate WB connector data, which is freed during driver teardown, while userspace could still interact with the WB connector via drmm functions. This mismatch causes a use-after-free condition. The patch replaces devm_kzalloc() with drmm_ functions in dpu_writeback_init() to ensure consistent memory management and prevent use-after-free.
Potential Impact
This use-after-free vulnerability could lead to memory corruption or kernel instability if exploited, potentially allowing attackers to cause denial of service or other unintended behavior. However, no known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source to address this issue by changing the memory allocation method in the drm/msm/dpu driver. Users should apply the official kernel updates that include this patch. Patch status is not explicitly confirmed here; check the vendor or kernel mailing list advisories for the exact fixed versions and update accordingly.
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… (CVE-2026-64050)
Description
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/
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel drm/msm/dpu component arises from mixing devm-managed and drmm-managed memory functions. Specifically, devm_kzalloc() was used to allocate WB connector data, which is freed during driver teardown, while userspace could still interact with the WB connector via drmm functions. This mismatch causes a use-after-free condition. The patch replaces devm_kzalloc() with drmm_ functions in dpu_writeback_init() to ensure consistent memory management and prevent use-after-free.
Potential Impact
This use-after-free vulnerability could lead to memory corruption or kernel instability if exploited, potentially allowing attackers to cause denial of service or other unintended behavior. However, no known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source to address this issue by changing the memory allocation method in the drm/msm/dpu driver. Users should apply the official kernel updates that include this patch. Patch status is not explicitly confirmed here; check the vendor or kernel mailing list advisories for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9858-6444-xrjw
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64050"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912cbc8
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:55:40 UTC
Last updated: 07/20/2026, 19:41:22 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.