CVE-2023-53991drm/msm/dpu: Disallow unallocated resources to be returned
- —Not scoredno CVSS score yet
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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/
Timeline
ID reserved
By Linux
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected bb00a452d6f77391441ef7df48f7115dd459cd2f – < 8dbd54d679e3ab37be43bc1ed9f463dbf83a2259
- affected bb00a452d6f77391441ef7df48f7115dd459cd2f – < bf661c5e3bc48973acb363c76e3db965d9ed26d0
- affected bb00a452d6f77391441ef7df48f7115dd459cd2f – < 9e1e236acdc42b5c43ec8d7f03a39537e70cc309
- affected bb00a452d6f77391441ef7df48f7115dd459cd2f – < 9fe3644c720ac87d150f0bba5a4ae86cae55afaf
- affected bb00a452d6f77391441ef7df48f7115dd459cd2f – < abc40122d9a69f56c04efb5a7485795f5ac799d1
- affected 5.7
- unaffected < 5.7
- unaffected 5.10.173 – ≤ 5.10.*
- unaffected 5.15.99 – ≤ 5.15.*
- unaffected 6.1.16 – ≤ 6.1.*
- unaffected 6.2.3 – ≤ 6.2.*
- unaffected 6.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/8dbd54d679e3ab37be43bc1ed9f463dbf83a2259 (opens in a new tab)
- https://git.kernel.org/stable/c/bf661c5e3bc48973acb363c76e3db965d9ed26d0 (opens in a new tab)
- https://git.kernel.org/stable/c/9e1e236acdc42b5c43ec8d7f03a39537e70cc309 (opens in a new tab)
- https://git.kernel.org/stable/c/9fe3644c720ac87d150f0bba5a4ae86cae55afaf (opens in a new tab)
- https://git.kernel.org/stable/c/abc40122d9a69f56c04efb5a7485795f5ac799d1 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-205155 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53991)Record last updated .