SECUFOCUSNOW
Home›CVE index›CVE-2026-74666
ReviewHigh

CVE-2026-74666

Linux

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 s...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.08.23
PRIORITY ASSESSMENT

Review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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 s...

Affected product and versions

Product
Linux
Affected versions
>= 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a < bf3c8e86bc8ad111be3f3136125e255344bcb3da, >= 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a < 8cfb2e71926a682f36c4240067d424074dd8f70f, >= 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a < f015c9de92b731814059a343b765c60c0196225c, >= 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a < cf8189b82bb93f219ab740e0346c919ad65ada62, >= 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a < ad740b4990347521f0db260d381f9f74e7b340ba, >= 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a < 2c7b5eb87b2b288cdbde825f21d2b83b2f5da747, >= 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a < a08196c3cc105947746ec21309edfbb60275fcdb, >= 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a < 1a35da325cac4d5bcad76a2aa943408a6f1d9000, >= 4.2
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available