Heimdall Security Logo

CVE-2023-53224

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <2b69cdd9f9a7f596e3dd31f05f9852940d177924, <4.16, 5.15.96, 0, 5.4.233, 6.1.14, b99fee58a20ab8e0557cce87b6f187e325993142, <=5.10.*, 5.10.170, 4.19.274, <99e3fd21f8fc975c95e8cf76fbf6a3d2656f8f71, 6.3, <=5.4.*, <c98077f7598a562f51051eec043be0cb3e1b1b5e, <=4.19.*, <118901ad1f25d2334255b3d50512fa20591531cd, <0a1394e07c5d6bf1bfc25db8589ff1b1bfb6f46a, <=6.2.*, <94d8de83286fb1827340eba35b61c308f6b46ead, 4.16, <=*, <=5.15.*, 6.2.1, <1ba10d3640e9783dad811fe4e24d55465c37c64d

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: Fix function prototype mismatch for ext4_feat_ktype With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed. ext4_feat_ktype was setting the "release" handler to "kfree", which doesn't have a matching function prototype. Add a simple wrapper with the correct prototype. This was found as a result of Clang's new -Wcast-function-type-strict flag, which is more sensitive than the simpler -Wcast-function-type, which only checks for type width mismatches. Note that this code is only reached when ext4 is a loadable module and it is being unloaded: CFI failure at kobject_put+0xbb/0x1b0 (target: kfree+0x0/0x180; expected type: 0x7c4aa698) ... RIP: 0010:kobject_put+0xbb/0x1b0 ... Call Trace: <TASK> ext4_exit_sysfs+0x14/0x60 [ext4] cleanup_module+0x67/0xedb [ext4]

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <2b69cdd9f9a7f596e3dd31f05f9852940d177924, <4.16, 5.15.96, 0, 5.4.233, 6.1.14, b99fee58a20ab8e0557cce87b6f187e325993142, <=5.10.*, 5.10.170, 4.19.274, <99e3fd21f8fc975c95e8cf76fbf6a3d2656f8f71, 6.3, <=5.4.*, <c98077f7598a562f51051eec043be0cb3e1b1b5e, <=4.19.*, <118901ad1f25d2334255b3d50512fa20591531cd, <0a1394e07c5d6bf1bfc25db8589ff1b1bfb6f46a, <=6.2.*, <94d8de83286fb1827340eba35b61c308f6b46ead, 4.16, <=*, <=5.15.*, 6.2.1, <1ba10d3640e9783dad811fe4e24d55465c37c64d) 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