CVE-2026-74666

CVE CVE-2026-74666EUVD EUVD-2026-64353Published 2026-08-22T15:32:38.000ZLast changed 2026-08-27T12:40:00.000ZCVSS 7.8

What the advisory describes

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.

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: 6.6.152; patch: 5.15.218; patch: 5.10.267; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <a08196c3cc105947746ec21309edfbb60275fcdb; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <cf8189b82bb93f219ab740e0346c919ad65ada62; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <1a35da325cac4d5bcad76a2aa943408a6f1d9000; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <ad740b4990347521f0db260d381f9f74e7b340ba; patch: 6.1.185; patch: 6.18.45; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <f015c9de92b731814059a343b765c60c0196225c; patch: 7.1.9; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <bf3c8e86bc8ad111be3f3136125e255344bcb3da; 4.2; patch: 0; patch: 6.12.104; patch: 7.2; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <8cfb2e71926a682f36c4240067d424074dd8f70f; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <2c7b5eb87b2b288cdbde825f21d2b83b2f5da747

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.