Heimdall Security Logo

CVE-2026-74582

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

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : 6.1.185, <=6.1.*, 01a658c1b9d4b5393c38d5a92d9112ab1425382a, <=6.12.*, 6.6.152, <bcd4df60ac9481b1ceffdfe5ec38fe51dcaae812, 0, 5.10.267, <=7.1.*, <4.10, 4.4.133, 5.15.218, <4.17, <=5.10.*, <=6.6.*, 6190cce26e40bf71c4d375b21eea74bb07b6a0f3, 7.1.9, <4.5, b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba, 4.17, d9fb8cc230b2a4757e9fe4f81468f81212d4deaa, 4.9.103, 4.16.12, 8809ae6747e760e6f1d2453ceb08c9bcc4939766, <=6.18.*, <03390aa32e669cc4ecd7d34108e2e1afc13d689d, 6.12.104, <5bb10753d428aadfc356a2bfe9acea09c82a62ec, 4.14.44, <91f041451f967cd87ed722a8f43c0b767a64f1a0, <b06b6fce6d7deaf7238e09b48ce3b1125ff41acd, 6.18.45, <=*, <=5.15.*, <4.15, <78a47127e33c340bc6d38dcc4552a094b4f5cc77, 7.2, <9052756290962ffb9a661bcf319e92dedaaedfed, <142e287b3a25cfe909215177c23243e7fc5ae2b1

Description

In the Linux kernel, the following vulnerability has been resolved: packet: use consistent hard_header_len in non-ring send paths packet_snd() reads dev->hard_header_len multiple times while allocating and constructing an skb. Device reconfiguration can change this value concurrently, for example through bonding device type changes. For SOCK_RAW, packet_snd() can save a larger value in reserve and later allocate headroom using a smaller value. Moving skb->data back by reserve then places it before skb->head, and the following copy from userspace can attempt an out-of-bounds write. packet_sendmsg_spkt() has the same issue because it calculates its reservation and header offset from separate reads before dropping the RCU read lock to allocate the skb. Add LL_RESERVED_SPACE_EX() for callers that already saved a header length. Read hard_header_len once in packet_snd() and use it for allocation and construction. In packet_sendmsg_spkt(), preserve the allocation-time value through the device lookup retry. The separate SOCK_DGRAM consistency problem between hard_header_len and header_ops->create is not addressed here.

Gravité et risque d'exploitation

CVE-2026-74582 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 6.1.185, <=6.1.*, 01a658c1b9d4b5393c38d5a92d9112ab1425382a, <=6.12.*, 6.6.152, <bcd4df60ac9481b1ceffdfe5ec38fe51dcaae812, 0, 5.10.267, <=7.1.*, <4.10, 4.4.133, 5.15.218, <4.17, <=5.10.*, <=6.6.*, 6190cce26e40bf71c4d375b21eea74bb07b6a0f3, 7.1.9, <4.5, b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba, 4.17, d9fb8cc230b2a4757e9fe4f81468f81212d4deaa, 4.9.103, 4.16.12, 8809ae6747e760e6f1d2453ceb08c9bcc4939766, <=6.18.*, <03390aa32e669cc4ecd7d34108e2e1afc13d689d, 6.12.104, <5bb10753d428aadfc356a2bfe9acea09c82a62ec, 4.14.44, <91f041451f967cd87ed722a8f43c0b767a64f1a0, <b06b6fce6d7deaf7238e09b48ce3b1125ff41acd, 6.18.45, <=*, <=5.15.*, <4.15, <78a47127e33c340bc6d38dcc4552a094b4f5cc77, 7.2, <9052756290962ffb9a661bcf319e92dedaaedfed, <142e287b3a25cfe909215177c23243e7fc5ae2b1) 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