Heimdall Security Logo

CVE-2026-89557

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <75d15738fd33a782606d0dc80cfeff47edf2ddd8, 5.15.221, <323f3a056dbccb39a642ebde642044a680f3a6d6, 5.10.270, <573fb68105fdc6a127ba6069e58a0d2aff3c9f93, 0, 7.2.4, 3.1, 6.1.188, 2699b67223aca6b1450fc2f72e40fada952afc85, <=5.10.*, <=6.6.*, <3.1, <0a03f9541c06fda64301dcf94f376f07ce2cc396, 6.6.157, <=6.18.*, <=7.2.*, <3b097416b4cff77285c1f472fc2c4058d8a7554f, <94c820d99a4305d4ded41a97ed37ec7d26c56e7f, <=*, <35d522bd32462afcf1981dab6da8a9256c26c1e0, <=5.15.*, 6.18.50, 6.12.109, <df7d4d011d5ace20699ea948712f09f9ac08924f, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: md: do overflow check for sb->bblog_shift in super_1_load() In super_1_load(), sb->bblog_shift is an __u8 type value loaded from on- disk superblock. It is used for badblocks API badblocks_set() by the following sequence, 1930 rdev->badblocks.shift = sb->bblog_shift; 1931 for (i = 0 ; i < (sectors << (9-3)) ; i++, bbp++) { 1932 u64 bb = le64_to_cpu(*bbp); 1933 int count = bb & (0x3ff); 1934 u64 sector = bb >> 10; 1935 sector <<= sb->bblog_shift; 1936 count <<= sb->bblog_shift; 1937 if (bb + 1 == 0) 1938 break; 1939 if (!badblocks_set(&rdev->badblocks, sector, count, 1)) 1940 return -EINVAL; 1941 } bb->bblog_shit is in range of 0-255, variable sector is 64bit width, for an invalid bb->bblog_shit, it is possible to make sector be overflowed by the following calculation, 1935 sector <<= sb->bblog_shift; Then in turn when call badblocks_set() at line 1939 with the invalid rdev->badblocks.shift set at line 1930, may result an overflow inside _badblocks_clear() in block/badblocks.c. Although there are many places to call badblocks APIs, the non-zero shift value is only used in super_1_load(), other places always use 0 as the shift value. Therefore it is unnecessary to do a general shift value overflow check inside badblock API, and just check here as the caller. This may avoid unnecessary check, make the badblocks API code more simple and elegant.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <75d15738fd33a782606d0dc80cfeff47edf2ddd8, 5.15.221, <323f3a056dbccb39a642ebde642044a680f3a6d6, 5.10.270, <573fb68105fdc6a127ba6069e58a0d2aff3c9f93, 0, 7.2.4, 3.1, 6.1.188, 2699b67223aca6b1450fc2f72e40fada952afc85, <=5.10.*, <=6.6.*, <3.1, <0a03f9541c06fda64301dcf94f376f07ce2cc396, 6.6.157, <=6.18.*, <=7.2.*, <3b097416b4cff77285c1f472fc2c4058d8a7554f, <94c820d99a4305d4ded41a97ed37ec7d26c56e7f, <=*, <35d522bd32462afcf1981dab6da8a9256c26c1e0, <=5.15.*, 6.18.50, 6.12.109, <df7d4d011d5ace20699ea948712f09f9ac08924f, 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