Local system crash via packet-ring race
Published Aug 22, 2026 · Updated Aug 27, 2026
Race condition in the Linux kernel packet subsystem allows local users to crash the system through packet-socket ring reconfiguration. packet_set_ring() cleared the RX ring under sk_receive_queue.lock but published the receive hook after unlocking, letting packet_poll() or packet_recvmsg() call __packet_rcv_has_room() on stale or NULL storage. Reaching the flaw requires local low-privileged access and a race between ring reconfiguration and pressure clearing; the supported consequence is a kernel crash.
Summary
What happened
Race condition in the Linux kernel packet subsystem allows local users to crash the system through packet-socket ring reconfiguration. packet_set_ring() cleared the RX ring under sk_receive_queue.lock but published the receive hook after unlocking, letting packet_poll() or packet_recvmsg() call __packet_rcv_has_room() on stale or NULL storage. Reaching the flaw requires local low-privileged access and a race between ring reconfiguration and pressure clearing; the supported consequence is a kernel crash.
The record
- CVE
- CVE-2026-74666
- Published
- Aug 22, 2026
- Updated
- Aug 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 22, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <1a35da325cac4d5bcad76a2aa943408a6f1d9000
- Affected versionversion=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <2c7b5eb87b2b288cdbde825f21d2b83b2f5da747
- Affected versionversion=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <8cfb2e71926a682f36c4240067d424074dd8f70f
- Affected versionversion=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <a08196c3cc105947746ec21309edfbb60275fcdb
- Affected versionversion=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <ad740b4990347521f0db260d381f9f74e7b340ba
- Affected versionversion=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <bf3c8e86bc8ad111be3f3136125e255344bcb3da
- Affected versionversion=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <cf8189b82bb93f219ab740e0346c919ad65ada62
- Affected versionversion=2ccdbaa6d55b0656244ba57c4b56765a0af76c0a <f015c9de92b731814059a343b765c60c0196225c
- Affected versionversion=4.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo