Heimdall Security Logo

CVE-2025-40248

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : 6.6.118, <=6.1.*, d021c344051af91f42c5ba9fdedc176740cbd238, <da664101fb4a0de5cb70d2bae6a650df954df2af, <=6.12.*, 6.17.10, <5998da5a8208ae9ad7838ba322bccb2bdcd95e81, 0, <3.9, 6.18, <ab6b19f690d89ae4709fba73a3c4a7911f495b7a, 5.10.247, <=5.10.*, <=6.6.*, 6.12.60, <67432915145848658149683101104e32f9fd6559, <3f71753935d648082a8279a97d30efe6b85be680, 5.4.302, <=5.4.*, <002541ef650b742a198e4be363881439bb9d86b4, 5.15.197, 6.1.159, <eeca93f06df89be5a36305b7b9dae1ed65550dfc, <=*, <=5.15.*, <=6.17.*, <f1c170cae285e4b8f61be043bb17addc3d0a14b5, 3.9

Description

In the Linux kernel, the following vulnerability has been resolved: vsock: Ignore signal/timeout on connect() if already established During connect(), acting on a signal/timeout by disconnecting an already established socket leads to several issues: 1. connect() invoking vsock_transport_cancel_pkt() -> virtio_transport_purge_skbs() may race with sendmsg() invoking virtio_transport_get_credit(). This results in a permanently elevated `vvs->bytes_unsent`. Which, in turn, confuses the SOCK_LINGER handling. 2. connect() resetting a connected socket's state may race with socket being placed in a sockmap. A disconnected socket remaining in a sockmap breaks sockmap's assumptions. And gives rise to WARNs. 3. connect() transitioning SS_CONNECTED -> SS_UNCONNECTED allows for a transport change/drop after TCP_ESTABLISHED. Which poses a problem for any simultaneous sendmsg() or connect() and may result in a use-after-free/null-ptr-deref. Do not disconnect socket on signal/timeout. Keep the logic for unconnected sockets: they don't linger, can't be placed in a sockmap, are rejected by sendmsg(). [1]: https://lore.kernel.org/netdev/e07fd95c-9a38-4eea-9638-133e38c2ec9b@rbox.co/ [2]: https://lore.kernel.org/netdev/20250317-vsock-trans-signal-race-v4-0-fc8837f3f1d4@rbox.co/ [3]: https://lore.kernel.org/netdev/60f1b7db-3099-4f6a-875e-af9f6ef194f6@rbox.co/

Gravité et risque d'exploitation

CVE-2025-40248 obtient un score CVSS de 7.8/10, soit une gravité élevé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 4.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.6.118, <=6.1.*, d021c344051af91f42c5ba9fdedc176740cbd238, <da664101fb4a0de5cb70d2bae6a650df954df2af, <=6.12.*, 6.17.10, <5998da5a8208ae9ad7838ba322bccb2bdcd95e81, 0, <3.9, 6.18, <ab6b19f690d89ae4709fba73a3c4a7911f495b7a, 5.10.247, <=5.10.*, <=6.6.*, 6.12.60, <67432915145848658149683101104e32f9fd6559, <3f71753935d648082a8279a97d30efe6b85be680, 5.4.302, <=5.4.*, <002541ef650b742a198e4be363881439bb9d86b4, 5.15.197, 6.1.159, <eeca93f06df89be5a36305b7b9dae1ed65550dfc, <=*, <=5.15.*, <=6.17.*, <f1c170cae285e4b8f61be043bb17addc3d0a14b5, 3.9) 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