Heimdall Security Logo

CVE-2024-50017

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 6.12, <=6.1.*, <=6.11.*, 5.15.221, 0, 6.1.188, <=6.6.*, <cc31744a294584a36bf764a0ffa3255a8e69f036, 6.6.78, 66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451, 6.11.3, <d113f9723f2bfd9c6feeb899b8ddbee6b8a6e01f, 4.12, <d80a99892f7a992d103138fa4636b2c33abd6740, <cb2555fb0223edac9e7820f16de17ae04a39ad39, <=*, <fe9bab1d6441ed49dc3dd0acce4c2215e8d85447, <=5.15.*, <4.12, 6.10.14, <=6.10.*, <a23823098ab2c277c14fc110b97d8d5c83597195

Description

In the Linux kernel, the following vulnerability has been resolved: x86/mm/ident_map: Use gbpages only where full GB page should be mapped. When ident_pud_init() uses only GB pages to create identity maps, large ranges of addresses not actually requested can be included in the resulting table; a 4K request will map a full GB. This can include a lot of extra address space past that requested, including areas marked reserved by the BIOS. That allows processor speculation into reserved regions, that on UV systems can cause system halts. Only use GB pages when map creation requests include the full GB page of space. Fall back to using smaller 2M pages when only portions of a GB page are included in the request. No attempt is made to coalesce mapping requests. If a request requires a map entry at the 2M (pmd) level, subsequent mapping requests within the same 1G region will also be at the pmd level, even if adjacent or overlapping such requests could have been combined to map a full GB page. Existing usage starts with larger regions and then adds smaller regions, so this should not have any great consequence.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 6.12, <=6.1.*, <=6.11.*, 5.15.221, 0, 6.1.188, <=6.6.*, <cc31744a294584a36bf764a0ffa3255a8e69f036, 6.6.78, 66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451, 6.11.3, <d113f9723f2bfd9c6feeb899b8ddbee6b8a6e01f, 4.12, <d80a99892f7a992d103138fa4636b2c33abd6740, <cb2555fb0223edac9e7820f16de17ae04a39ad39, <=*, <fe9bab1d6441ed49dc3dd0acce4c2215e8d85447, <=5.15.*, <4.12, 6.10.14, <=6.10.*, <a23823098ab2c277c14fc110b97d8d5c83597195) 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