Heimdall Security Logo

CVE-2026-64575

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

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : 1d7a82c1df5fc397eaca9c6b8c8f61aae9866ad4, <c842882e4c5d2818b858d6baf3fd10958c93f729, 6.17, cdec67a489d4fdae3e83e04fca0419136a83c4c2, 0, <=7.1.*, <980a813452754f8001704744e92f7aa697c53dd3, 36f955807ee4ede07e9410772f792e4cb4ec807b, 6.18.42, 9794ac757a650dd594391192183c9caf939f8223, 7.1.6, <7a6a6d2a127866935f87b55b557bc89693065462, <=6.18.*, <6.17, <8a726e9585ffe7bfbfad2b5279277a00973970f3, <9f27c4f0ae35b5390ce4f7a54d3501144e41a54d, <=*, <f0c1810320b0dac228103fad7311e89532134d83, 7.2

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: tcp: fix double sock release on batch realloc bpf_iter_tcp_batch() releases the current batch via bpf_iter_tcp_put_batch(), which drops the socket refs and rewrites each slot with the socket cookie, then grows the batch. cur_sk/end_sk are kept for bpf_iter_tcp_resume(), but on realloc failure the function returns ERR_PTR() before resume runs, leaving cur_sk < end_sk over slots that now hold cookies rather than sock pointers. bpf_iter_tcp_seq_stop() then calls bpf_iter_tcp_put_batch() again and dereferences a cookie as a struct sock. Empty the batch on the failure path so stop() does not release it again. The sockets were already freed by the first bpf_iter_tcp_put_batch(), so nothing leaks, and a later read() rescans the bucket from the start instead of skipping it. The sibling GFP_NOWAIT failure path still holds real socket references and is left for stop() to release. BUG: KASAN: null-ptr-deref in __sock_gen_cookie Read of size 8 at addr 0000000000000059 by task exploit ... __sock_gen_cookie (net/core/sock_diag.c:28) bpf_iter_tcp_put_batch (net/ipv4/tcp_ipv4.c:2918) bpf_iter_tcp_seq_stop (net/ipv4/tcp_ipv4.c:3270) bpf_seq_read (kernel/bpf/bpf_iter.c:205) vfs_read (fs/read_write.c:572) ksys_read (fs/read_write.c:716) do_syscall_64 entry_SYSCALL_64_after_hwframe Kernel panic - not syncing: Fatal exception

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 1d7a82c1df5fc397eaca9c6b8c8f61aae9866ad4, <c842882e4c5d2818b858d6baf3fd10958c93f729, 6.17, cdec67a489d4fdae3e83e04fca0419136a83c4c2, 0, <=7.1.*, <980a813452754f8001704744e92f7aa697c53dd3, 36f955807ee4ede07e9410772f792e4cb4ec807b, 6.18.42, 9794ac757a650dd594391192183c9caf939f8223, 7.1.6, <7a6a6d2a127866935f87b55b557bc89693065462, <=6.18.*, <6.17, <8a726e9585ffe7bfbfad2b5279277a00973970f3, <9f27c4f0ae35b5390ce4f7a54d3501144e41a54d, <=*, <f0c1810320b0dac228103fad7311e89532134d83, 7.2) 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