Answer in brief
CVE-2026-74666 records a High severity (CVSS 7.8) vulnerability in packet: synchronize pressure clearing with ring reconfiguration. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <cf8189b82bb93f219ab740e0346c919ad65ada62 || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <ad740b4990347521f0db260d381f9f74e7b340ba || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <2c7b5eb87b2b288cdbde825f21d2b83b2f5da747 || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <a08196c3cc105947746ec21309edfbb60275fcdb || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <1a35da325cac4d5bcad76a2aa943408a6f1d9000 | cf8189b82bb93f219ab740e0346c919ad65ada62, ad740b4990347521f0db260d381f9f74e7b340ba, 2c7b5eb87b2b288cdbde825f21d2b83b2f5da747, a08196c3cc105947746ec21309edfbb60275fcdb, 1a35da325cac4d5bcad76a2aa943408a6f1d9000 |
| Linux/Linuxgeneric | 4.2 | Not reported |
| Linux/Linuxgeneric | >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <bf3c8e86bc8ad111be3f3136125e255344bcb3da || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <8cfb2e71926a682f36c4240067d424074dd8f70f || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <f015c9de92b731814059a343b765c60c0196225c || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <cf8189b82bb93f219ab740e0346c919ad65ada62 || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <ad740b4990347521f0db260d381f9f74e7b340ba || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <2c7b5eb87b2b288cdbde825f21d2b83b2f5da747 || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <a08196c3cc105947746ec21309edfbb60275fcdb || >=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <1a35da325cac4d5bcad76a2aa943408a6f1d9000 | bf3c8e86bc8ad111be3f3136125e255344bcb3da, 8cfb2e71926a682f36c4240067d424074dd8f70f, f015c9de92b731814059a343b765c60c0196225c, cf8189b82bb93f219ab740e0346c919ad65ada62, ad740b4990347521f0db260d381f9f74e7b340ba, 2c7b5eb87b2b288cdbde825f21d2b83b2f5da747, a08196c3cc105947746ec21309edfbb60275fcdb, 1a35da325cac4d5bcad76a2aa943408a6f1d9000 |
Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 22, 2026
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.
Quoted source text, attributed separately from HOL analysis.