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

Published Aug 10, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

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

packetsetring() 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->bindlock, and later restores po->num and re-registers the hook from the saved wasrunning value.

That unlocked window can race with NETDEVUNREGISTER. The notifier can observe the socket as not running, skip unregisterprothook(), and invalidate the per-socket binding by setting po->ifindex to -1 and clearing po->prothook.dev. A one-member fanout group can still retain its shared fanout hook device pointer. When packetsetring() resumes, re-registering solely from the stale wasrunning state can re-add the fanout hook after the device has been unregistered.

Treat po->ifindex == -1 as an invalidated binding after reacquiring po->bindlock. 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 Software

1 affected component
Linux Kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    When invalidating a per-socket binding after a device unregistration, set po->ifindex to -1 (the stale was_running state alone must not cause re-registration), and ensure the fanout hook re-registration is skipped if the device has already been unregistered.

    Linux kernel packet fanout hook po->ifindex = -1

Event History

Aug 10, 2026
CVE Published
via MITRE·12:03 PM
Data Sourced
via MITRE·12:03 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68338?

CVE-2026-68338 has a risk score of 27, indicating a significant level of concern.

2

How do I fix CVE-2026-68338?

To fix CVE-2026-68338, update the Linux kernel to the latest version that addresses this vulnerability.

3

What impact does CVE-2026-68338 have on system security?

CVE-2026-68338 can lead to improper socket behavior, potentially allowing unauthorized packet handling.

4

Which version of the Linux kernel is affected by CVE-2026-68338?

CVE-2026-68338 affects specific versions of the Linux kernel prior to the security patch being applied.

5

Has CVE-2026-68338 been publicly disclosed?

Yes, CVE-2026-68338 was published on August 10, 2026, providing details about the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203