CVE-2026-72155

Description

In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: swp: Improve locking user experience In the case of the first block being locked (or the few first blocks), if the user want to fully unlock the device it has two possibilities: - either it asks to unlock the entire device, and this works; - or it asks to unlock just the block(s) that are currently locked, which fails. It fails because the conditions "can_be_top" and "can_be_bottom" are true. Indeed, in this case, we unlock everything, so the TB bit does not matter. However in the current implementation, use_top would be true (as this is the favourite option) and lock_len, which in practice should be reduced down to 0, is set to "nor->params->size - (ofs + len)" which is a positive number. This is wrong. An easy way is to simply add an extra condition. In the unlock() path, if we can achieve the same result from both sides, it means we unlock everything and lock_len must simply be 0. A comment is added to clarify that logic.

Gravité et risque d'exploitation

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

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, <c0806df5cf806545160f3fdac3c888926ceac557, 5.15.217, 0, <4.6, <=7.1.*, <9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, <6110ab5ffd84e8daa654652446a03ce2f77580a7, <12d4d69221159e6d0e72400ec81195d691169b53, 5.10.266, <dc341272cf8e15a2c511db3c4df5dab8adf70ad0, <e1d456b26bf23e30db305a6184e8abd9ab68bbf2, 4.6, <=6.18.*, 6.6.145, 3dd8012a8eeb3702fa17450ec1a16a3f38af138d, <=*, <=5.15.*, 7.2, <23c285be8f6fcde9088fe12bb69c701d46696be1, <a6fd2145c73b80bb6a5eed7355a4f63597d712d9) 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

• https://git.kernel.org/stable/c/23c285be8f6fcde9088fe12bb69c701d46696be1
• https://git.kernel.org/stable/c/a6fd2145c73b80bb6a5eed7355a4f63597d712d9
• https://git.kernel.org/stable/c/9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a
• https://git.kernel.org/stable/c/dc341272cf8e15a2c511db3c4df5dab8adf70ad0
• https://git.kernel.org/stable/c/6110ab5ffd84e8daa654652446a03ce2f77580a7
• https://git.kernel.org/stable/c/c0806df5cf806545160f3fdac3c888926ceac557
• https://git.kernel.org/stable/c/12d4d69221159e6d0e72400ec81195d691169b53
• https://git.kernel.org/stable/c/e1d456b26bf23e30db305a6184e8abd9ab68bbf2