Heimdall Security Logo

CVE-2023-53991

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <9fe3644c720ac87d150f0bba5a4ae86cae55afaf, <9e1e236acdc42b5c43ec8d7f03a39537e70cc309, <bf661c5e3bc48973acb363c76e3db965d9ed26d0, 6.1.16, 0, 5.10.173, <8dbd54d679e3ab37be43bc1ed9f463dbf83a2259, <5.7, <=5.10.*, 6.2.3, 6.3, 5.15.99, <=6.2.*, 5.7, bb00a452d6f77391441ef7df48f7115dd459cd2f, <=*, <=5.15.*, <abc40122d9a69f56c04efb5a7485795f5ac799d1

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/

Gravité et risque d'exploitation

CVE-2023-53991 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.20 %, ce qui la place devant 9.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <9fe3644c720ac87d150f0bba5a4ae86cae55afaf, <9e1e236acdc42b5c43ec8d7f03a39537e70cc309, <bf661c5e3bc48973acb363c76e3db965d9ed26d0, 6.1.16, 0, 5.10.173, <8dbd54d679e3ab37be43bc1ed9f463dbf83a2259, <5.7, <=5.10.*, 6.2.3, 6.3, 5.15.99, <=6.2.*, 5.7, bb00a452d6f77391441ef7df48f7115dd459cd2f, <=*, <=5.15.*, <abc40122d9a69f56c04efb5a7485795f5ac799d1) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE