CVE-2023-53991 Details
Description
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: Disallow unallocated resources to be returned In the event that the topology requests resources that have not been created by the system (because they are typically not represented in dpu_mdss_cfg ^1), the resource(s) in global_state (in this case DSC blocks, until their allocation/assignment is being sanity-checked in "drm/msm/dpu: Reject topologies for which no DSC blocks are available") remain NULL but will still be returned out of dpu_rm_get_assigned_resources, where the caller expects to get an array containing num_blks valid pointers (but instead gets these NULLs). To prevent this from happening, where null-pointer dereferences typically result in a hard-to-debug platform lockup, num_blks shouldn't increase past NULL blocks and will print an error and break instead. After all, max_blks represents the static size of the maximum number of blocks whereas the actual amount varies per platform. ^1: which can happen after a git rebase ended up moving additions to _dpu_cfg to a different struct which has the same patch context. Patchwork: https://patchwork.freedesktop.org/patch/517636/
A vulnerability in the Linux kernel's Direct Rendering Manager (DRM) for the Qualcomm Mobile Subsystem (MSM) Display Pipeline Unit (DPU) has been addressed. This issue arises when the system's topology requests resources that have not been allocated, particularly Display Stream Compression (DSC) blocks. These unallocated resources remain as NULL in the global state but are incorrectly returned by the resource management function, leading to a null pointer dereference. Such dereferences can cause a platform lockup, creating a challenging debugging scenario. The vulnerability has been fixed by ensuring that the count of allocated blocks does not exceed the available resources, thereby preventing the null pointer dereference and the associated platform lockup.
Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 24, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/8dbd54d679e3ab37be43bc1ed9f463dbf83a2259 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/9e1e236acdc42b5c43ec8d7f03a39537e70cc309 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/9fe3644c720ac87d150f0bba5a4ae86cae55afaf | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/abc40122d9a69f56c04efb5a7485795f5ac799d1 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/bf661c5e3bc48973acb363c76e3db965d9ed26d0 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 24, 2025 | New CVE Received | kernel.org |
Volerion