CVE-2026-68338

net/packet: avoid fanout hook re-registration after unregister

HIGH
7.8
CVSS Score
Published: August 10, 2026 at 12:03 PM UTC
Updated: October 19, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net/packet: avoid fanout hook re-registration after unregister packet_set_ring() temporarily detaches a socket from packet delivery while reconfiguring its ring. It records the previous running state, clears po->num, unregisters the protocol hook when needed, drops po->bind_lock, and later restores po->num and re-registers the hook from the saved was_running value. That unlocked window can race with NETDEV_UNREGISTER. The notifier can observe the socket as not running, skip __unregister_prot_hook(), and invalidate the per-socket binding by setting po->ifindex to -1 and clearing po->prot_hook.dev. A one-member fanout group can still retain its shared fanout hook device pointer. When packet_set_ring() resumes, re-registering solely from the stale was_running state can re-add the fanout hook after the device has been unregistered. Treat po->ifindex == -1 as an invalidated binding after reacquiring po->bind_lock. This is distinct from ifindex 0, the normal unbound/wildcard state: ifindex -1 marks an existing device binding that was invalidated when the device was unregistered. Restore po->num as before, but do not re-register the hook if device unregister already detached the socket.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.1dc99f600698dcac69b8f56dda9a8a00d645c5ffc
Vendor states this is fixed in 0a052e0808e015e68144a9877e6ef42b952c49fa (fixed)
Vendor states this is fixed in 1bc55c29cd85818e9052f17deb287d5a11fb817f (fixed)
Vendor states this is fixed in 4628efbdc7affd094181f5263e65c1062e31f15f (fixed)
Vendor states this is fixed in 50aff80475abd3533eef4320477037e6fcc6b56e (fixed)
Vendor states this is fixed in 80ec024d53a05c60ad1d08968dcf745f10c1665c (fixed)
Vendor states this is fixed in a885387dae7986a55bae5c77a15bdd447f64e9b9 (fixed)
Vendor states this is fixed in acb40ebfa5c4d62f84339fcbf713f2a9fd033a71 (fixed)
Vendor states this is fixed in c820f4b7f2fa38f8769db0d0cefdd94e2721504d (fixed)
Vendor states this is fixed in 3.1 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card