CVE-2024-40984

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

CVSS 7.8 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, <2.6.32, 5.4.279, 6.10, 0, <ddc1f5f124479360a1fd43f73be950781d172239, <6eca23100e9030725f69c1babacd58803f29ec8d, <435ecc978c3d5d0c4e172ec5b956dc1904061d98, <434c6b924e1f4c219aab2d9e05fe79c5364e37d3, <a83e1385b780d41307433ddbc86e3c528db031f0, <=5.10.*, <=6.6.*, 6.6.36, <dc5017c57f5eee80020c73ff8b67ba7f9fd08b1f, <=6.9.*, 6.9.7, 5.15.162, <=5.4.*, <=4.19.*, 2.6.32, 5.10.221, <e21a4c9129c72fa54dd00f5ebf71219b41d43c04, 6.1.96, <=*, <=5.15.*, 4.19.317, d410ee5109a1633a686a5663c6743a92e1181f9b, <ae465109d82f4fb03c5adbe85f2d6a6a3d59124c

Description

In the Linux kernel, the following vulnerability has been resolved: ACPICA: Revert "ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine." Undo the modifications made in commit d410ee5109a1 ("ACPICA: avoid "Info: mapping multiple BARs. Your kernel is fine.""). The initial purpose of this commit was to stop memory mappings for operation regions from overlapping page boundaries, as it can trigger warnings if different page attributes are present. However, it was found that when this situation arises, mapping continues until the boundary's end, but there is still an attempt to read/write the entire length of the map, leading to a NULL pointer deference. For example, if a four-byte mapping request is made but only one byte is mapped because it hits the current page boundary's end, a four-byte read/write attempt is still made, resulting in a NULL pointer deference. Instead, map the entire length, as the ACPI specification does not mandate that it must be within the same page boundary. It is permissible for it to be mapped across different regions.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <2.6.32, 5.4.279, 6.10, 0, <ddc1f5f124479360a1fd43f73be950781d172239, <6eca23100e9030725f69c1babacd58803f29ec8d, <435ecc978c3d5d0c4e172ec5b956dc1904061d98, <434c6b924e1f4c219aab2d9e05fe79c5364e37d3, <a83e1385b780d41307433ddbc86e3c528db031f0, <=5.10.*, <=6.6.*, 6.6.36, <dc5017c57f5eee80020c73ff8b67ba7f9fd08b1f, <=6.9.*, 6.9.7, 5.15.162, <=5.4.*, <=4.19.*, 2.6.32, 5.10.221, <e21a4c9129c72fa54dd00f5ebf71219b41d43c04, 6.1.96, <=*, <=5.15.*, 4.19.317, d410ee5109a1633a686a5663c6743a92e1181f9b, <ae465109d82f4fb03c5adbe85f2d6a6a3d59124c) 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