CVE-2025-39880

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.3%
Linux•Linux•Versions : 6.16.8, <5.11, <=6.1.*, <=6.12.*, <=6.16.*, cd1a677cad994021b19665ed476aea63f5d54f31, 6.17, 0, <23538cfbeed87159a5ac6c61e7a6de3d8d4486a8, 5.11, <35dbbc3dbf8bccb2d77c68444f42c1e6d2d27983, 5.15.194, <=6.6.*, <6bd8b56899be0b514945f639a89ccafb8f8dfaef, 6.6.107, <ea12ab684f8ae8a6da11a22c78d94a79e2163096, 6.1.153, <cdbc9836c7afadad68f374791738f118263c5371, <591ea9c30737663a471b2bb07b27ddde86b020d5, 6.12.48, <=*, <=5.15.*

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: fix invalid accesses to ceph_connection_v1_info There is a place where generic code in messenger.c is reading and another place where it is writing to con->v1 union member without checking that the union member is active (i.e. msgr1 is in use). On 64-bit systems, con->v1.auth_retry overlaps with con->v2.out_iter, so such a read is almost guaranteed to return a bogus value instead of 0 when msgr2 is in use. This ends up being fairly benign because the side effect is just the invalidation of the authorizer and successive fetching of new tickets. con->v1.connect_seq overlaps with con->v2.conn_bufs and the fact that it's being written to can cause more serious consequences, but luckily it's not something that happens often.

Gravité et risque d'exploitation

CVE-2025-39880 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.33 %, ce qui la place devant 24.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.16.8, <5.11, <=6.1.*, <=6.12.*, <=6.16.*, cd1a677cad994021b19665ed476aea63f5d54f31, 6.17, 0, <23538cfbeed87159a5ac6c61e7a6de3d8d4486a8, 5.11, <35dbbc3dbf8bccb2d77c68444f42c1e6d2d27983, 5.15.194, <=6.6.*, <6bd8b56899be0b514945f639a89ccafb8f8dfaef, 6.6.107, <ea12ab684f8ae8a6da11a22c78d94a79e2163096, 6.1.153, <cdbc9836c7afadad68f374791738f118263c5371, <591ea9c30737663a471b2bb07b27ddde86b020d5, 6.12.48, <=*, <=5.15.*) 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