CVE-2024-35905

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <9970e059af471478455f9534e8c3db82f8c5496d, 6.9, <=6.1.*, <6.6.26, 6.8.5, 5.15.148, 0, 6.6.14, 6.6.26, b1d4d54d32ce6342f5faffe71bae736540ce7cb5, 6.8, 5.15.154, <6.8, 6.1.75, <98cdac206b112bec63852e94802791e316acc2c1, 08b91babccbb168353f8d43fea0ed28a4cad568c, <=5.10.*, 1858b8a331937f3976d8482cd5f6e1f945294ad3, <=6.6.*, 5.10.215, 02962684258eb53f414a8a59854767be526e6abb, <3f0784b2f1eb9147973d8c43ba085c5fdf44ff69, a833a17aeac73b33f79433d7cee68d5cafd71e4f, <5.15.154, <37dc1718dc0c4392dbfcb9adec22a776e745dd69, <=6.8.*, <203a68151e8eeb331d4a64ab78303f3a15faf103, <ecc6a2101840177e57c925c102d2d29f260d37c8, 6.7.2, 6.1.85, <=*, <=5.15.*, 5.10.209, afea95d319ccb4ad2060dece9ac5e2e364dec543, <6.1.85, <5.10.215

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Protect against int overflow for stack access size This patch re-introduces protection against the size of access to stack memory being negative; the access size can appear negative as a result of overflowing its signed int representation. This should not actually happen, as there are other protections along the way, but we should protect against it anyway. One code path was missing such protections (fixed in the previous patch in the series), causing out-of-bounds array accesses in check_stack_range_initialized(). This patch causes the verification of a program with such a non-sensical access size to fail. This check used to exist in a more indirect way, but was inadvertendly removed in a833a17aeac7.

Gravité et risque d'exploitation

CVE-2024-35905 obtient un score CVSS de 7.8/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.22 %, ce qui la place devant 12.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <9970e059af471478455f9534e8c3db82f8c5496d, 6.9, <=6.1.*, <6.6.26, 6.8.5, 5.15.148, 0, 6.6.14, 6.6.26, b1d4d54d32ce6342f5faffe71bae736540ce7cb5, 6.8, 5.15.154, <6.8, 6.1.75, <98cdac206b112bec63852e94802791e316acc2c1, 08b91babccbb168353f8d43fea0ed28a4cad568c, <=5.10.*, 1858b8a331937f3976d8482cd5f6e1f945294ad3, <=6.6.*, 5.10.215, 02962684258eb53f414a8a59854767be526e6abb, <3f0784b2f1eb9147973d8c43ba085c5fdf44ff69, a833a17aeac73b33f79433d7cee68d5cafd71e4f, <5.15.154, <37dc1718dc0c4392dbfcb9adec22a776e745dd69, <=6.8.*, <203a68151e8eeb331d4a64ab78303f3a15faf103, <ecc6a2101840177e57c925c102d2d29f260d37c8, 6.7.2, 6.1.85, <=*, <=5.15.*, 5.10.209, afea95d319ccb4ad2060dece9ac5e2e364dec543, <6.1.85, <5.10.215) 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