Heimdall Security Logo

CVE-2026-74666

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

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : 6.1.185, <=6.1.*, <=6.12.*, <4.2, 6.6.152, <f015c9de92b731814059a343b765c60c0196225c, <2c7b5eb87b2b288cdbde825f21d2b83b2f5da747, 0, 5.10.267, <=7.1.*, <1a35da325cac4d5bcad76a2aa943408a6f1d9000, <=5.10.*, 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a, <cf8189b82bb93f219ab740e0346c919ad65ada62, <=6.6.*, 7.1.9, <=6.18.*, 6.12.104, 4.2, <ad740b4990347521f0db260d381f9f74e7b340ba, <a08196c3cc105947746ec21309edfbb60275fcdb, 6.18.45, <=*, <=5.15.*, <bf3c8e86bc8ad111be3f3136125e255344bcb3da, <8cfb2e71926a682f36c4240067d424074dd8f70f, 7.2, 5.15.218

Description

In the Linux kernel, the following vulnerability has been resolved: packet: synchronize pressure clearing with ring reconfiguration packet_set_ring() updates the RX ring state under sk_receive_queue.lock, but used to publish the tpacket receive mode through po->prot_hook.func after releasing that lock. packet_poll() and packet_recvmsg() can then run the pressure clearing path after the ring has been cleared while still seeing tpacket_rcv, causing __packet_rcv_has_room() to dereference stale or NULL ring storage. Move the existing receive hook assignment into the same sk_receive_queue.lock section as the ring state update. Keep the assignment otherwise unchanged, including on TX ring reconfiguration, to avoid adding behavior changes that are not required for the fix. Serialize packet_recvmsg() pressure clearing with the same queue lock only after PACKET_SOCK_PRESSURE has been observed. If the flag is clear and the socket has moved away from tpacket_rcv, packet_set_ring() has already detached the socket and waited for synchronize_net(), so no new packet input can set the flag again. packet_poll() already holds sk_receive_queue.lock, so it uses the new unlocked helper directly.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 6.1.185, <=6.1.*, <=6.12.*, <4.2, 6.6.152, <f015c9de92b731814059a343b765c60c0196225c, <2c7b5eb87b2b288cdbde825f21d2b83b2f5da747, 0, 5.10.267, <=7.1.*, <1a35da325cac4d5bcad76a2aa943408a6f1d9000, <=5.10.*, 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a, <cf8189b82bb93f219ab740e0346c919ad65ada62, <=6.6.*, 7.1.9, <=6.18.*, 6.12.104, 4.2, <ad740b4990347521f0db260d381f9f74e7b340ba, <a08196c3cc105947746ec21309edfbb60275fcdb, 6.18.45, <=*, <=5.15.*, <bf3c8e86bc8ad111be3f3136125e255344bcb3da, <8cfb2e71926a682f36c4240067d424074dd8f70f, 7.2, 5.15.218) 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