CVE-2026-74666packet: synchronize pressure clearing with ring reconfiguration
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a before bf3c8e86bc8ad111be3f3136125e255344bcb3da; from 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a before 8cfb2e71926a682f36c4240067d424074dd8f70f; from 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a before f015c9de92b731814059a343b765c60c0196225c; from 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a before cf8189b82bb93f219ab740e0346c919ad65ada62; from 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a before ad740b4990347521f0db260d381f9f74e7b340ba; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a builds before 2c7b5eb87b2b288cdbde825f21d2b83b2f5da747; from 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a before a08196c3cc105947746ec21309edfbb60275fcdb; 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a builds before 1a35da325cac4d5bcad76a2aa943408a6f1d9000 | CNA record |
References
- https://git.kernel.org/stable/c/bf3c8e86bc8ad111be3f3136125e255344bcb3da
- https://git.kernel.org/stable/c/8cfb2e71926a682f36c4240067d424074dd8f70f
- https://git.kernel.org/stable/c/f015c9de92b731814059a343b765c60c0196225c
- https://git.kernel.org/stable/c/cf8189b82bb93f219ab740e0346c919ad65ada62
- https://git.kernel.org/stable/c/ad740b4990347521f0db260d381f9f74e7b340ba
- https://git.kernel.org/stable/c/2c7b5eb87b2b288cdbde825f21d2b83b2f5da747
- https://git.kernel.org/stable/c/a08196c3cc105947746ec21309edfbb60275fcdb
- https://git.kernel.org/stable/c/1a35da325cac4d5bcad76a2aa943408a6f1d9000
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.