packet: synchronize pressure clearing with ring reconfiguration
Summary
| CVE | CVE-2026-74666 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-22 16:16:40 UTC |
| Updated | 2026-08-22 16:16:40 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a cf8189b82bb93f219ab740e0346c919ad65ada62 git |
Not specified |
| CNA |
Linux |
Linux |
affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a ad740b4990347521f0db260d381f9f74e7b340ba git |
Not specified |
| CNA |
Linux |
Linux |
affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a 2c7b5eb87b2b288cdbde825f21d2b83b2f5da747 git |
Not specified |
| CNA |
Linux |
Linux |
affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a a08196c3cc105947746ec21309edfbb60275fcdb git |
Not specified |
| CNA |
Linux |
Linux |
affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a 1a35da325cac4d5bcad76a2aa943408a6f1d9000 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.2 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.2 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.152 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.104 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.45 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.9 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/1a35da325cac4d5bcad76a2aa943408a6f1d9000 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/cf8189b82bb93f219ab740e0346c919ad65ada62 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ad740b4990347521f0db260d381f9f74e7b340ba |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2c7b5eb87b2b288cdbde825f21d2b83b2f5da747 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a08196c3cc105947746ec21309edfbb60275fcdb |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.