Heimdall Security Logo

CVE-2025-40068

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

CVSS 8.4 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 6.12.53, <3ac37e100385b59ac821a62118494442238aaac4, 6.17.3, 0, <5aa5799d162ad1b8e8b699d48b6218143c695a78, <736fc7bf5f68f6b74a0925b7e072c571838657d2, 6.18, 4342306f0f0d5ff4315a204d315c1b51b914fca5, <=6.6.*, <5.15, <a86c8b9d03f7101e1750233846fe989df6f0d631, 5.15, 5.15.195, <=*, 6.6.112, <9378cfe228c2c679564a4116bcb28c8e89dff989, <=5.15.*, 6.1.156, <f6b36cfd25cbadad63447c673743cf771090e756, <=6.17.*

Description

In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: Fix integer overflow in run_unpack() The MFT record relative to the file being opened contains its runlist, an array containing information about the file's location on the physical disk. Analysis of all Call Stack paths showed that the values of the runlist array, from which LCNs are calculated, are not validated before run_unpack function. The run_unpack function decodes the compressed runlist data format from MFT attributes (for example, $DATA), converting them into a runs_tree structure, which describes the mapping of virtual clusters (VCN) to logical clusters (LCN). The NTFS3 subsystem also has a shortcut for deleting files from MFT records - in this case, the RUN_DEALLOCATE command is sent to the run_unpack input, and the function logic provides that all data transferred to the runlist about file or directory is deleted without creating a runs_tree structure. Substituting the runlist in the $DATA attribute of the MFT record for an arbitrary file can lead either to access to arbitrary data on the disk bypassing access checks to them (since the inode access check occurs above) or to destruction of arbitrary data on the disk. Add overflow check for addition operation. Found by Linux Verification Center (linuxtesting.org) with SVACE.

Gravité et risque d'exploitation

CVE-2025-40068 obtient un score CVSS de 8.4/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.18 %, ce qui la place devant 7.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 6.12.53, <3ac37e100385b59ac821a62118494442238aaac4, 6.17.3, 0, <5aa5799d162ad1b8e8b699d48b6218143c695a78, <736fc7bf5f68f6b74a0925b7e072c571838657d2, 6.18, 4342306f0f0d5ff4315a204d315c1b51b914fca5, <=6.6.*, <5.15, <a86c8b9d03f7101e1750233846fe989df6f0d631, 5.15, 5.15.195, <=*, 6.6.112, <9378cfe228c2c679564a4116bcb28c8e89dff989, <=5.15.*, 6.1.156, <f6b36cfd25cbadad63447c673743cf771090e756, <=6.17.*) 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