CVE-2026-74582

CVE CVE-2026-74582EUVD EUVD-2026-64004Published 2026-08-21T16:31:55.000ZLast changed 2026-08-27T12:39:47.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.2; 8809ae6747e760e6f1d2453ceb08c9bcc4939766; 6190cce26e40bf71c4d375b21eea74bb07b6a0f3; b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba <5bb10753d428aadfc356a2bfe9acea09c82a62ec; b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba <b06b6fce6d7deaf7238e09b48ce3b1125ff41acd; 4.9.103 <4.10; b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba <bcd4df60ac9481b1ceffdfe5ec38fe51dcaae812; 01a658c1b9d4b5393c38d5a92d9112ab1425382a; b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba <03390aa32e669cc4ecd7d34108e2e1afc13d689d; 4.14.44 <4.15; b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba <142e287b3a25cfe909215177c23243e7fc5ae2b1; 4.17; patch: 7.1.9; patch: 5.10.267; 4.4.133 <4.5; patch: 0; b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba <9052756290962ffb9a661bcf319e92dedaaedfed; d9fb8cc230b2a4757e9fe4f81468f81212d4deaa; patch: 5.15.218; patch: 6.12.104; b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba <78a47127e33c340bc6d38dcc4552a094b4f5cc77; patch: 6.18.45; patch: 6.6.152; b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba <91f041451f967cd87ed722a8f43c0b767a64f1a0; patch: 6.1.185; 4.16.12 <4.17

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.