CVE-2025-21871

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <3eb4911364c764572e9db4ab900a57689a54e8ce, <fd9d2d6124c293e40797a080adf8a9c237efd8b8, <21234efe2a8474a6d2d01ea9573319de7858ce44, <=6.1.*, <=6.12.*, 6.1.130, 0, <0180cf0373f84fff61b16f8c062553a13dd7cfca, 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2, 6.14, <=5.10.*, <=6.6.*, 6.6.80, 4.12, 6.13.5, <=5.4.*, 6.12.17, 5.4.291, 5.15.179, <ec18520f5edc20a00c34a8c9fdd6507c355e880f, <d61cc1a435e6894bfb0dd3370c6f765d2d12825d, <=*, <70b0d6b0a199c5a3ee6c72f5e61681ed6f759612, <=5.15.*, <4.12, 5.10.235, <=6.13.*, <c0a9a948159153be145f9471435695373904ee6d

Description

In the Linux kernel, the following vulnerability has been resolved: tee: optee: Fix supplicant wait loop OP-TEE supplicant is a user-space daemon and it's possible for it be hung or crashed or killed in the middle of processing an OP-TEE RPC call. It becomes more complicated when there is incorrect shutdown ordering of the supplicant process vs the OP-TEE client application which can eventually lead to system hang-up waiting for the closure of the client application. Allow the client process waiting in kernel for supplicant response to be killed rather than indefinitely waiting in an unkillable state. Also, a normal uninterruptible wait should not have resulted in the hung-task watchdog getting triggered, but the endless loop would. This fixes issues observed during system reboot/shutdown when supplicant got hung for some reason or gets crashed/killed which lead to client getting hung in an unkillable state. It in turn lead to system being in hung up state requiring hard power off/on to recover.

Gravité et risque d'exploitation

CVE-2025-21871 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.21 %, ce qui la place devant 10.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <3eb4911364c764572e9db4ab900a57689a54e8ce, <fd9d2d6124c293e40797a080adf8a9c237efd8b8, <21234efe2a8474a6d2d01ea9573319de7858ce44, <=6.1.*, <=6.12.*, 6.1.130, 0, <0180cf0373f84fff61b16f8c062553a13dd7cfca, 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2, 6.14, <=5.10.*, <=6.6.*, 6.6.80, 4.12, 6.13.5, <=5.4.*, 6.12.17, 5.4.291, 5.15.179, <ec18520f5edc20a00c34a8c9fdd6507c355e880f, <d61cc1a435e6894bfb0dd3370c6f765d2d12825d, <=*, <70b0d6b0a199c5a3ee6c72f5e61681ed6f759612, <=5.15.*, <4.12, 5.10.235, <=6.13.*, <c0a9a948159153be145f9471435695373904ee6d) 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