Heimdall Security Logo

CVE-2026-53223

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

CVSS 7.1 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, <=6.12.*, 4.10.14, 6.12.94, 4.11, 0, <1ee90b77b727df903033db873c75caac5c27ec98, <ad9a0374ee6d11048e1f74cd5180bad58b9848b4, 6.1.176, <b903e9b5629ec8dd6db92174070045bf81ad7060, 5.15.210, <e0665b2a8e90bb08bd205062c75662b502d31797, <=5.10.*, <=6.6.*, 7.0.13, 6.18.36, <4.11, 8605330aac5a5785630aec8f64378a54891937cc, 7.1, <=6.18.*, <eb51a9ad3ceb01bc6c0fb608dbc856e03ee6f24a, <3dde4fb941fa5649ab809f6cd3e20e0c424a4e31, <24a0d548d3a765cd4558224e4f8e06e14cba26e3, cdaf15b43bd31003220cb080bcbbd57787a2fca9, <=*, <71ff5cdd5da61d0438e902aa0fd68c28bc901abe, <=5.15.*, 6.6.143, 5.10.259

Description

In the Linux kernel, the following vulnerability has been resolved: net: guard timestamp cmsgs to real error queue skbs skb_is_err_queue() treats PACKET_OUTGOING as the sole marker for an skb from sk_error_queue. That assumption is not true for AF_PACKET sockets: outgoing packet taps are also delivered to packet sockets with skb->pkt_type == PACKET_OUTGOING, but their skb->cb is owned by AF_PACKET instead of struct sock_exterr_skb. If such an skb is received with timestamping enabled, the generic timestamp cmsg path can read AF_PACKET control-buffer state as sock_exterr_skb::opt_stats. With SO_RXQ_OVFL enabled, the packet drop counter overlaps opt_stats. An odd drop count makes the path emit SCM_TIMESTAMPING_OPT_STATS with skb->len and skb->data. For non-linear skbs this copies past the linear head and can trigger hardened usercopy or disclose adjacent heap contents. Keep skb_is_err_queue() local to net/socket.c, but make it verify that the PACKET_OUTGOING marker is paired with the sock_rmem_free destructor installed by sock_queue_err_skb(). AF_PACKET receive skbs use normal receive ownership and no longer pass as error-queue skbs, while legitimate sk_error_queue entries keep the PACKET_OUTGOING marker and sock_rmem_free ownership.

Gravité et risque d'exploitation

CVE-2026-53223 obtient un score CVSS de 7.1/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.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, <=6.12.*, 4.10.14, 6.12.94, 4.11, 0, <1ee90b77b727df903033db873c75caac5c27ec98, <ad9a0374ee6d11048e1f74cd5180bad58b9848b4, 6.1.176, <b903e9b5629ec8dd6db92174070045bf81ad7060, 5.15.210, <e0665b2a8e90bb08bd205062c75662b502d31797, <=5.10.*, <=6.6.*, 7.0.13, 6.18.36, <4.11, 8605330aac5a5785630aec8f64378a54891937cc, 7.1, <=6.18.*, <eb51a9ad3ceb01bc6c0fb608dbc856e03ee6f24a, <3dde4fb941fa5649ab809f6cd3e20e0c424a4e31, <24a0d548d3a765cd4558224e4f8e06e14cba26e3, cdaf15b43bd31003220cb080bcbbd57787a2fca9, <=*, <71ff5cdd5da61d0438e902aa0fd68c28bc901abe, <=5.15.*, 6.6.143, 5.10.259) 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