Heimdall Security Logo

CVE-2024-50010

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 6.12, <=6.1.*, 5.15.170, <c9b77438077d5a20c79ead95bcdaf9bd4797baaf, 0, 6.1.115, <0d196e7589cefe207d5d41f37a0a28a1fdeeb7c6, 0fd338b2d2cdf827091ae819ae90ad760b94ad0c, <=5.10.*, <=6.6.*, 5.9, <5.9, 5.10.229, <b723f96407a0a078cf75970e4dbf16b46d286a61, <0d16f53c91111cec914f0811fcc526a2ba77b20d, <=*, <=5.15.*, 6.6.59, <0bdf77be2330062b3a64f2bec39f62ab874a6796

Description

In the Linux kernel, the following vulnerability has been resolved: exec: don't WARN for racy path_noexec check Both i_mode and noexec checks wrapped in WARN_ON stem from an artifact of the previous implementation. They used to legitimately check for the condition, but that got moved up in two commits: 633fb6ac3980 ("exec: move S_ISREG() check earlier") 0fd338b2d2cd ("exec: move path_noexec() check earlier") Instead of being removed said checks are WARN_ON'ed instead, which has some debug value. However, the spurious path_noexec check is racy, resulting in unwarranted warnings should someone race with setting the noexec flag. One can note there is more to perm-checking whether execve is allowed and none of the conditions are guaranteed to still hold after they were tested for. Additionally this does not validate whether the code path did any perm checking to begin with -- it will pass if the inode happens to be regular. Keep the redundant path_noexec() check even though it's mindless nonsense checking for guarantee that isn't given so drop the WARN. Reword the commentary and do small tidy ups while here. [brauner: keep redundant path_noexec() check]

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 6.12, <=6.1.*, 5.15.170, <c9b77438077d5a20c79ead95bcdaf9bd4797baaf, 0, 6.1.115, <0d196e7589cefe207d5d41f37a0a28a1fdeeb7c6, 0fd338b2d2cdf827091ae819ae90ad760b94ad0c, <=5.10.*, <=6.6.*, 5.9, <5.9, 5.10.229, <b723f96407a0a078cf75970e4dbf16b46d286a61, <0d16f53c91111cec914f0811fcc526a2ba77b20d, <=*, <=5.15.*, 6.6.59, <0bdf77be2330062b3a64f2bec39f62ab874a6796) 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