CVE-2024-50195

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.1 · Élevée
EPSS 0.2%
Linux•Linux•Versions : 6.12, <=6.1.*, <1ff7247101af723731ea42ed565d54fb8f341264, <=6.11.*, 5.15.169, 2.6.39, 5.4.285, 0, 6.1.114, 6.11.5, <=5.10.*, <=6.6.*, <d8794ac20a299b647ba9958f6d657051fc51a540, <c8789fbe2bbf75845e45302cba6ffa44e1884d01, <29f085345cde24566efb751f39e5d367c381c584, <a3f169e398215e71361774d13bf91a0101283ac2, <=5.4.*, <=4.19.*, 4.19.323, 6.6.58, <=*, 5.10.228, <=5.15.*, 0606f422b453f76c31ab2b1bd52943ff06a2dcf2, <e0c966bd3e31911b57ef76cec4c5796ebd88e512, <27abbde44b6e71ee3891de13e1a228aa7ce95bfe, <673a1c5a2998acbd429d6286e6cad10f17f4f073, <2.6.39

Description

In the Linux kernel, the following vulnerability has been resolved: posix-clock: Fix missing timespec64 check in pc_clock_settime() As Andrew pointed out, it will make sense that the PTP core checked timespec64 struct's tv_sec and tv_nsec range before calling ptp->info->settime64(). As the man manual of clock_settime() said, if tp.tv_sec is negative or tp.tv_nsec is outside the range [0..999,999,999], it should return EINVAL, which include dynamic clocks which handles PTP clock, and the condition is consistent with timespec64_valid(). As Thomas suggested, timespec64_valid() only check the timespec is valid, but not ensure that the time is in a valid range, so check it ahead using timespec64_valid_strict() in pc_clock_settime() and return -EINVAL if not valid. There are some drivers that use tp->tv_sec and tp->tv_nsec directly to write registers without validity checks and assume that the higher layer has checked it, which is dangerous and will benefit from this, such as hclge_ptp_settime(), igb_ptp_settime_i210(), _rcar_gen4_ptp_settime(), and some drivers can remove the checks of itself.

Gravité et risque d'exploitation

CVE-2024-50195 obtient un score CVSS de 7.1/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.23 %, ce qui la place devant 13.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.12, <=6.1.*, <1ff7247101af723731ea42ed565d54fb8f341264, <=6.11.*, 5.15.169, 2.6.39, 5.4.285, 0, 6.1.114, 6.11.5, <=5.10.*, <=6.6.*, <d8794ac20a299b647ba9958f6d657051fc51a540, <c8789fbe2bbf75845e45302cba6ffa44e1884d01, <29f085345cde24566efb751f39e5d367c381c584, <a3f169e398215e71361774d13bf91a0101283ac2, <=5.4.*, <=4.19.*, 4.19.323, 6.6.58, <=*, 5.10.228, <=5.15.*, 0606f422b453f76c31ab2b1bd52943ff06a2dcf2, <e0c966bd3e31911b57ef76cec4c5796ebd88e512, <27abbde44b6e71ee3891de13e1a228aa7ce95bfe, <673a1c5a2998acbd429d6286e6cad10f17f4f073, <2.6.39) 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