Heimdall Security Logo

CVE-2024-58007

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

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, <47470acd719d45c4c8c418c07962f74cc995652b, <9c88b3a3fae4d60641c3a45be66269d00eff33cd, <=6.12.*, <407c928305c1a37232a63811c400ef616f85ccbc, 5.4, 0, efb448d0a3fca01bb987dd70963da6185b81751e, <2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd, 6.14, <=5.10.*, <7445fa05317534bbd8b373c0eff8319187916030, 6.6.78, <=6.6.*, <2495c6598731b6d7f565140f2bd63ef4bc36ce7d, 6.1.129, <22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0, <=5.4.*, 6.13.3, 5.4.291, 5.15.179, <5.4, 6.12.14, <=*, <=5.15.*, 5.10.235, <=6.13.*, <0a92feddae0634a0b87c04b19d343f6af97af700

Description

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: socinfo: Avoid out of bounds read of serial number On MSM8916 devices, the serial number exposed in sysfs is constant and does not change across individual devices. It's always: db410c:/sys/devices/soc0$ cat serial_number 2644893864 The firmware used on MSM8916 exposes SOCINFO_VERSION(0, 8), which does not have support for the serial_num field in the socinfo struct. There is an existing check to avoid exposing the serial number in that case, but it's not correct: When checking the item_size returned by SMEM, we need to make sure the *end* of the serial_num is within bounds, instead of comparing with the *start* offset. The serial_number currently exposed on MSM8916 devices is just an out of bounds read of whatever comes after the socinfo struct in SMEM. Fix this by changing offsetof() to offsetofend(), so that the size of the field is also taken into account.

Gravité et risque d'exploitation

CVE-2024-58007 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.25 %, ce qui la place devant 15.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <47470acd719d45c4c8c418c07962f74cc995652b, <9c88b3a3fae4d60641c3a45be66269d00eff33cd, <=6.12.*, <407c928305c1a37232a63811c400ef616f85ccbc, 5.4, 0, efb448d0a3fca01bb987dd70963da6185b81751e, <2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd, 6.14, <=5.10.*, <7445fa05317534bbd8b373c0eff8319187916030, 6.6.78, <=6.6.*, <2495c6598731b6d7f565140f2bd63ef4bc36ce7d, 6.1.129, <22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0, <=5.4.*, 6.13.3, 5.4.291, 5.15.179, <5.4, 6.12.14, <=*, <=5.15.*, 5.10.235, <=6.13.*, <0a92feddae0634a0b87c04b19d343f6af97af700) 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