Heimdall Security Logo

CVE-2026-93095

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 2.6.12, 5.15.221, 5.10.270, 0, 6.1.188, <e2ea5cac61acfc11dad22f1d2d4bc71d56c52a20, 6.18.52, <7898beee166c1145c0bca364d687b8437435bf1a, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <2.6.12, <e20f3b749ad241df77ec1c3e13a9c22209aa1eb3, <=5.10.*, <b9729c51a8b67f8b20b8a8cf395da4be63a0c15b, <=6.6.*, <e31985c67ba00a59d9b1340af473c1dbe6c87856, 6.6.157, <473ea7aa35615829f0de7a71e8691d69dc24e328, 7.2.6, <=6.18.*, 6.12.110, <=7.2.*, <=*, <=5.15.*, <af48abc1b00d865c3f4c4d76b901c44115cb7162, <33cda0036bc683fc888c20b04a5fc030e3e8413b, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: hfsplus: validate thread record before delete key rebuild hfsplus_delete_cat() is called with str == NULL when the last open reference to an unlinked HFS+ hardlink backing inode is closed. In that case, the function finds the catalog thread by CNID and rebuilds the catalog key from thread.nodeName. That reconstruction path reads thread.nodeName.length directly from the catalog B-tree into fd.search_key and then copies length * 2 bytes into fd.search_key->cat.name.unicode. It does not first check that the found record is a thread record or that its size matches the thread name. A corrupted image can therefore provide an oversized thread name length and make hfs_bnode_read() write past the catalog search-key allocation. Read the CNID record through hfsplus_brec_read_cat(), which bounds the record read to sizeof(hfsplus_cat_entry) and verifies that a thread record's size exactly matches nodeName.length. Together, these checks ensure an accepted thread name fits HFSPLUS_MAX_STRLEN. Reject non-thread records before building the delete key from the validated thread name. Share the thread-record-type helper between hfsplus_find_cat() and hfsplus_delete_cat().

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 2.6.12, 5.15.221, 5.10.270, 0, 6.1.188, <e2ea5cac61acfc11dad22f1d2d4bc71d56c52a20, 6.18.52, <7898beee166c1145c0bca364d687b8437435bf1a, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <2.6.12, <e20f3b749ad241df77ec1c3e13a9c22209aa1eb3, <=5.10.*, <b9729c51a8b67f8b20b8a8cf395da4be63a0c15b, <=6.6.*, <e31985c67ba00a59d9b1340af473c1dbe6c87856, 6.6.157, <473ea7aa35615829f0de7a71e8691d69dc24e328, 7.2.6, <=6.18.*, 6.12.110, <=7.2.*, <=*, <=5.15.*, <af48abc1b00d865c3f4c4d76b901c44115cb7162, <33cda0036bc683fc888c20b04a5fc030e3e8413b, 7.3) 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