Heimdall Security Logo

CVE-2026-31400

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <301670dcd098c1fe5c2fe90fb3c7a8f4814d2351, <=6.1.*, <=6.12.*, 2.6.12, 6.12.78, 0, 7.0, <1dfedb293943e491379c9302b428e6f920a73d12, <41f6ba6c98a618043d2cd71030bf9a752dfab8b2, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <7bcd5e318876ac638c8ceade7a648e76ac8c48e1, <=5.10.*, <=6.6.*, <=6.19.*, <373457de14281c1fc7cace6fc4c8a267fc176673, 5.15.203, <f18c1f2a88ca91357916997cdb0f7adaf14fc497, <=6.18.*, 6.1.167, <17ad31b3a43b72aec3a3d83605891e1397d0d065, <be5c35960e5ead70862736161836e2d1bc7352dc, <=*, 5.10.253, <=5.15.*, 6.19.10, 6.6.130, 6.18.20

Description

In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix cache_request leak in cache_release When a reader's file descriptor is closed while in the middle of reading a cache_request (rp->offset != 0), cache_release() decrements the request's readers count but never checks whether it should free the request. In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup. The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up. Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so, dequeue and free the cache_request.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <301670dcd098c1fe5c2fe90fb3c7a8f4814d2351, <=6.1.*, <=6.12.*, 2.6.12, 6.12.78, 0, 7.0, <1dfedb293943e491379c9302b428e6f920a73d12, <41f6ba6c98a618043d2cd71030bf9a752dfab8b2, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <7bcd5e318876ac638c8ceade7a648e76ac8c48e1, <=5.10.*, <=6.6.*, <=6.19.*, <373457de14281c1fc7cace6fc4c8a267fc176673, 5.15.203, <f18c1f2a88ca91357916997cdb0f7adaf14fc497, <=6.18.*, 6.1.167, <17ad31b3a43b72aec3a3d83605891e1397d0d065, <be5c35960e5ead70862736161836e2d1bc7352dc, <=*, 5.10.253, <=5.15.*, 6.19.10, 6.6.130, 6.18.20) 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