Heimdall Security Logo

CVE-2026-31452

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <07c1a31af18290054da3d18221b8bf58983c5d3a, 0, 7.0, <699bac4d4c951974d55b045c983d1de777215949, <93cb2d103e5c707de0f7ad58a39b7f0fddc27aa6, <=5.10.*, <=6.6.*, 3.8, 6.19.11, <=6.19.*, <c047332be7195833a5c5126816c2502df8269fe4, 5.15.203, <ed9356a30e59c7cc3198e7fc46cfedf3767b9b17, <7920dcc571cef3d8aa9ee109c136125d61d41669, <=6.18.*, 67cf5b09a46f72e048501b84996f2f77bc42e947, 6.6.131, 6.12.80, <3.8, <110d7ef602659ce4d7947c5480f7ca2779696aaf, <=*, 5.10.253, <f53a5d9f32924bc2a810d2df243b7714da58b636, <=5.15.*, 6.1.168, 6.18.21

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: convert inline data to extents when truncate exceeds inline size Add a check in ext4_setattr() to convert files from inline data storage to extent-based storage when truncate() grows the file size beyond the inline capacity. This prevents the filesystem from entering an inconsistent state where the inline data flag is set but the file size exceeds what can be stored inline. Without this fix, the following sequence causes a kernel BUG_ON(): 1. Mount filesystem with inode that has inline flag set and small size 2. truncate(file, 50MB) - grows size but inline flag remains set 3. sendfile() attempts to write data 4. ext4_write_inline_data() hits BUG_ON(write_size > inline_capacity) The crash occurs because ext4_write_inline_data() expects inline storage to accommodate the write, but the actual inline capacity (~60 bytes for i_block + ~96 bytes for xattrs) is far smaller than the file size and write request. The fix checks if the new size from setattr exceeds the inode's actual inline capacity (EXT4_I(inode)->i_inline_size) and converts the file to extent-based storage before proceeding with the size change. This addresses the root cause by ensuring the inline data flag and file size remain consistent during truncate operations.

Gravité et risque d'exploitation

CVE-2026-31452 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.18 %, ce qui la place devant 7.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <07c1a31af18290054da3d18221b8bf58983c5d3a, 0, 7.0, <699bac4d4c951974d55b045c983d1de777215949, <93cb2d103e5c707de0f7ad58a39b7f0fddc27aa6, <=5.10.*, <=6.6.*, 3.8, 6.19.11, <=6.19.*, <c047332be7195833a5c5126816c2502df8269fe4, 5.15.203, <ed9356a30e59c7cc3198e7fc46cfedf3767b9b17, <7920dcc571cef3d8aa9ee109c136125d61d41669, <=6.18.*, 67cf5b09a46f72e048501b84996f2f77bc42e947, 6.6.131, 6.12.80, <3.8, <110d7ef602659ce4d7947c5480f7ca2779696aaf, <=*, 5.10.253, <f53a5d9f32924bc2a810d2df243b7714da58b636, <=5.15.*, 6.1.168, 6.18.21) 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