Heimdall Security Logo

CVE-2025-71113

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

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : 6.12.64, <=6.1.*, <=6.12.*, 6.1.160, <5a4b65523608974a81edbe386f8a667a3e10c726, 0, <2.6.38, 6.6.120, <6f6e309328d53a10c0fe1f77dec2db73373179b6, 5.15.198, <f81244fd6b14fecfa93b66b6bb1d59f96554e550, <=5.10.*, <=6.6.*, 6.18.3, 2.6.38, <=6.18.*, <e125c8e346e4eb7b3e854c862fcb4392bc13ddba, <51a5ab36084f3251ef87eda3e6a6236f6488925e, 5.10.248, <=*, <543bf004e4eafbb302b1e6c78570d425d2ca13a0, <=5.15.*, 6.19, <84238876e3b3b262cf62d5f4d1338e983fb27010, fe869cdb89c95d060c77eea20204d6c91f233b53

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - zero initialize memory allocated via sock_kmalloc Several crypto user API contexts and requests allocated with sock_kmalloc() were left uninitialized, relying on callers to set fields explicitly. This resulted in the use of uninitialized data in certain error paths or when new fields are added in the future. The ACVP patches also contain two user-space interface files: algif_kpp.c and algif_akcipher.c. These too rely on proper initialization of their context structures. A particular issue has been observed with the newly added 'inflight' variable introduced in af_alg_ctx by commit: 67b164a871af ("crypto: af_alg - Disallow multiple in-flight AIO requests") Because the context is not memset to zero after allocation, the inflight variable has contained garbage values. As a result, af_alg_alloc_areq() has incorrectly returned -EBUSY randomly when the garbage value was interpreted as true: https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209 The check directly tests ctx->inflight without explicitly comparing against true/false. Since inflight is only ever set to true or false later, an uninitialized value has triggered -EBUSY failures. Zero-initializing memory allocated with sock_kmalloc() ensures inflight and other fields start in a known state, removing random issues caused by uninitialized data.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 6.12.64, <=6.1.*, <=6.12.*, 6.1.160, <5a4b65523608974a81edbe386f8a667a3e10c726, 0, <2.6.38, 6.6.120, <6f6e309328d53a10c0fe1f77dec2db73373179b6, 5.15.198, <f81244fd6b14fecfa93b66b6bb1d59f96554e550, <=5.10.*, <=6.6.*, 6.18.3, 2.6.38, <=6.18.*, <e125c8e346e4eb7b3e854c862fcb4392bc13ddba, <51a5ab36084f3251ef87eda3e6a6236f6488925e, 5.10.248, <=*, <543bf004e4eafbb302b1e6c78570d425d2ca13a0, <=5.15.*, 6.19, <84238876e3b3b262cf62d5f4d1338e983fb27010, fe869cdb89c95d060c77eea20204d6c91f233b53) 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