Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-68338, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected dc99f600698dcac69b8f56dda9a8a00d645c5ffc – < acb40ebfa5c4d62f84339fcbf713f2a9fd033a71
    • affected dc99f600698dcac69b8f56dda9a8a00d645c5ffc – < c820f4b7f2fa38f8769db0d0cefdd94e2721504d
    • affected dc99f600698dcac69b8f56dda9a8a00d645c5ffc – < 4628efbdc7affd094181f5263e65c1062e31f15f
    • affected dc99f600698dcac69b8f56dda9a8a00d645c5ffc – < 80ec024d53a05c60ad1d08968dcf745f10c1665c
    • affected dc99f600698dcac69b8f56dda9a8a00d645c5ffc – < 0a052e0808e015e68144a9877e6ef42b952c49fa
    • affected dc99f600698dcac69b8f56dda9a8a00d645c5ffc – < 1bc55c29cd85818e9052f17deb287d5a11fb817f
    • affected dc99f600698dcac69b8f56dda9a8a00d645c5ffc – < a885387dae7986a55bae5c77a15bdd447f64e9b9
    • affected dc99f600698dcac69b8f56dda9a8a00d645c5ffc – < 50aff80475abd3533eef4320477037e6fcc6b56e
  • Linux · Linux

    • affected 3.1
    • unaffected < 3.1
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68338 badge
[![CVE-2026-68338](https://cveledger.app/badge/CVE-2026-68338.svg)](https://cveledger.app/cve/CVE-2026-68338)

Record last updated .