Heimdall Security Logo

CVE-2024-57945

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : 6.13, <=6.1.*, 5.15.151, <=6.12.*, <d2bd51954ac8377c2f1eb1813e694788998add66, 8af1c121b0102041809bc137ec600d1865eaeedd, 0, 8310080799b40fd9f2a8b808c657269678c149af, 6.8, <6.8, 6.1.81, <=5.10.*, <=6.6.*, <5.10.258, a278d5c60f21aa15d540abb2f2da6e6d795c3e6e, <a4a7ac3d266008018f05fae53060fcb331151a14, 6.6.72, <92f08673d3f1893191323572f60e3c62f2e57c2f, a11dd49dcb9376776193e15641f84fcc1e5980c9, <5.16, 6.1.140, 5941a90c55d3bfba732b32208d58d997600b44ef, 2a1728c15ec4f45ed9248ae22f626541c179bfbe, <6.6.72, 5.10.258, <=*, <f754f27e98f88428aaf6be6e00f5cbce97f62d4b, 5.10.212, 6.12.10, 6.6.21, <04350304428063da6a55a8a4597d409dc69148b2, <6.1.140, 6.7.9

Description

In the Linux kernel, the following vulnerability has been resolved: riscv: mm: Fix the out of bound issue of vmemmap address In sparse vmemmap model, the virtual address of vmemmap is calculated as: ((struct page *)VMEMMAP_START - (phys_ram_base >> PAGE_SHIFT)). And the struct page's va can be calculated with an offset: (vmemmap + (pfn)). However, when initializing struct pages, kernel actually starts from the first page from the same section that phys_ram_base belongs to. If the first page's physical address is not (phys_ram_base >> PAGE_SHIFT), then we get an va below VMEMMAP_START when calculating va for it's struct page. For example, if phys_ram_base starts from 0x82000000 with pfn 0x82000, the first page in the same section is actually pfn 0x80000. During init_unavailable_range(), we will initialize struct page for pfn 0x80000 with virtual address ((struct page *)VMEMMAP_START - 0x2000), which is below VMEMMAP_START as well as PCI_IO_END. This commit fixes this bug by introducing a new variable 'vmemmap_start_pfn' which is aligned with memory section size and using it to calculate vmemmap address instead of phys_ram_base.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 6.13, <=6.1.*, 5.15.151, <=6.12.*, <d2bd51954ac8377c2f1eb1813e694788998add66, 8af1c121b0102041809bc137ec600d1865eaeedd, 0, 8310080799b40fd9f2a8b808c657269678c149af, 6.8, <6.8, 6.1.81, <=5.10.*, <=6.6.*, <5.10.258, a278d5c60f21aa15d540abb2f2da6e6d795c3e6e, <a4a7ac3d266008018f05fae53060fcb331151a14, 6.6.72, <92f08673d3f1893191323572f60e3c62f2e57c2f, a11dd49dcb9376776193e15641f84fcc1e5980c9, <5.16, 6.1.140, 5941a90c55d3bfba732b32208d58d997600b44ef, 2a1728c15ec4f45ed9248ae22f626541c179bfbe, <6.6.72, 5.10.258, <=*, <f754f27e98f88428aaf6be6e00f5cbce97f62d4b, 5.10.212, 6.12.10, 6.6.21, <04350304428063da6a55a8a4597d409dc69148b2, <6.1.140, 6.7.9) 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