CVE-2023-53991
published 2025-12-24CVE-2023-53991: 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…
PriorityP420
EPSS
0.18%
7.2th percentile
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/
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.20-1 (bookworm) | linux 6.1.20-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= bb00a452d6f77391441ef7df48f7115dd459cd2f < 8dbd54d679e3ab37be43bc1ed9f463dbf83a2259 | 8dbd54d679e3ab37be43bc1ed9f463dbf83a2259 |
| linux | linux | >= bb00a452d6f77391441ef7df48f7115dd459cd2f < bf661c5e3bc48973acb363c76e3db965d9ed26d0 | bf661c5e3bc48973acb363c76e3db965d9ed26d0 |
| linux | linux | >= bb00a452d6f77391441ef7df48f7115dd459cd2f < 9e1e236acdc42b5c43ec8d7f03a39537e70cc309 | 9e1e236acdc42b5c43ec8d7f03a39537e70cc309 |
| linux | linux | >= bb00a452d6f77391441ef7df48f7115dd459cd2f < 9fe3644c720ac87d150f0bba5a4ae86cae55afaf | 9fe3644c720ac87d150f0bba5a4ae86cae55afaf |
| linux | linux | >= bb00a452d6f77391441ef7df48f7115dd459cd2f < abc40122d9a69f56c04efb5a7485795f5ac799d1 | abc40122d9a69f56c04efb5a7485795f5ac799d1 |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 5.11.0 < 5.15.99 | 5.15.99 |
| linux | linux_kernel | >= 5.16.0 < 6.1.16 | 6.1.16 |
| linux | linux_kernel | >= 5.7.0 < 5.10.173 | 5.10.173 |
| linux | linux_kernel | >= 6.2.0 < 6.2.3 | 6.2.3 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
drm/msm/dpu: Disallow unallocated resources to be returned
osv·2025-12-24
CVE-2023-53991 drm/msm/dpu: Disallow unallocated resources to be returned
drm/msm/dpu: Disallow unallocated resources to be returned
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 resu
GHSA
GHSA-8m95-4p4w-6hv6: In the Linux kernel, the following vulnerability has been resolved:
drm/msm/dpu: Disallow unallocated resources to be returned
In the event that the
ghsa_unreviewed·2025-12-24
CVE-2023-53991 GHSA-8m95-4p4w-6hv6: In the Linux kernel, the following vulnerability has been resolved:
drm/msm/dpu: Disallow unallocated resources to be returned
In the event that the
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
in
OSV
CVE-2023-53991: In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: Disallow unallocated resources to be returned In the event that the t
osv·2025-12-24
CVE-2023-53991 CVE-2023-53991: In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: Disallow unallocated resources to be returned In the event that the t
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 incre
Red Hat
kernel: drm/msm/dpu: Disallow unallocated resources to be returned
vendor_redhat·2025-12-24
CVE-2023-53991 kernel: drm/msm/dpu: Disallow unallocated resources to be returned
kernel: drm/msm/dpu: Disallow unallocated resources to be returned
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
Debian
CVE-2023-53991: linux - In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu...
vendor_debian·2023
CVE-2023-53991 CVE-2023-53991: linux - In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu...
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 incre
No detection rules found.
No public exploits indexed.
Wiz
CVE-2023-53991 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2023-53991 CVE-2023-53991 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2023-53991 :
Linux Kernel vulnerability analysis and mitigation
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
t
Bugzilla
CVE-2023-53991 kernel: drm/msm/dpu: Disallow unallocated resources to be returned
bugzilla·2025-12-24
CVE-2023-53991 CVE-2023-53991 kernel: drm/msm/dpu: Disallow unallocated resources to be returned
CVE-2023-53991 kernel: drm/msm/dpu: Disallow unallocated resources to be returned
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 dere
https://git.kernel.org/stable/c/8dbd54d679e3ab37be43bc1ed9f463dbf83a2259https://git.kernel.org/stable/c/9e1e236acdc42b5c43ec8d7f03a39537e70cc309https://git.kernel.org/stable/c/9fe3644c720ac87d150f0bba5a4ae86cae55afafhttps://git.kernel.org/stable/c/abc40122d9a69f56c04efb5a7485795f5ac799d1https://git.kernel.org/stable/c/bf661c5e3bc48973acb363c76e3db965d9ed26d0
2025-12-24
Published