https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 03:56:52 +0000 https://vulnerability.circl.lu/vuln/cve-2023-53991 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm/dpu: Disallow unallocated resources to be returned</p> <p>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 &#34;drm/msm/dpu: Reject topologies for which no DSC blocks are available&#34;) 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).</p> <p>To prevent this from happening, where null-pointer dereferences typically result in a hard-to-debug platform lockup, num_blks shouldn&#39;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.</p> <p>^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.</p> <p>Patchwork: https://patchwork.freedesktop.org/patch/517636/</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm/dpu: Disallow unallocated resources to be returned</p> <p>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 &#34;drm/msm/dpu: Reject topologies for which no DSC blocks are available&#34;) 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).</p> <p>To prevent this from happening, where null-pointer dereferences typically result in a hard-to-debug platform lockup, num_blks shouldn&#39;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.</p> <p>^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.</p> <p>Patchwork: https://patchwork.freedesktop.org/patch/517636/</p> https://vulnerability.circl.lu/vuln/cve-2023-53991