CVE-2023-53991
Last modified
CVE-2023-53991 is a vulnerability of currently unknown severity. 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/. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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/
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= bb00a452d6f77391441ef7df48f7115dd459cd2f, < 8dbd54d679e3ab37be43bc1ed9f463dbf83a2259; >= bb00a452d6f77391441ef7df48f7115dd459cd2f, < bf661c5e3bc48973acb363c76e3db965d9ed26d0; >= bb00a452d6f77391441ef7df48f7115dd459cd2f, < 9e1e236acdc42b5c43ec8d7f03a39537e70cc309; >= bb00a452d6f77391441ef7df48f7115dd459cd2f, < 9fe3644c720ac87d150f0bba5a4ae86cae55afaf; >= bb00a452d6f77391441ef7df48f7115dd459cd2f, < abc40122d9a69f56c04efb5a7485795f5ac799d1 |
| Linux | Linux | 5.7 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2023-53991?
How severe is CVE-2023-53991?
How do I fix CVE-2023-53991?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53986In the Linux kernel, the following vulnerability has been re…8.6
- CVE-2023-53987In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53988In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53989In the Linux kernel, the following vulnerability has been re…
- CVE-2023-5399 A CWE-22: Improper Limitation of a Pathname to a Restri…9.8
- CVE-2023-53990In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53992In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53993In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53994In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53995In the Linux kernel, the following vulnerability has been re…
- CVE-2023-53996In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2023-53997In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2023-53991?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
