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-97608netfilter: nf_log: unregister loggers before per-net teardown

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_log: unregister loggers before per-net teardown nf_log_syslog and nfnetlink_log unregister their per-network namespace operations before unregistering their global logger backends. This leaves a window where a sysctl or netlink writer can rebind the still- registered logger after the per-net pre-exit callback cleared the old selection. The race looks like this: CPU 0 CPU 1 ---- ---- unregister_pernet_subsys() nf_log_unset(net, logger) net->nf.nf_loggers[pf] = NULL lock nf_log_mutex find logger in loggers[][] net->nf.nf_loggers[pf] = logger unlock nf_log_mutex nf_log_unregister(logger) lock nf_log_mutex loggers[pf][type] = NULL unlock nf_log_mutex synchronize_rcu() module exit returns module core frees backend memory Later, a sysctl read or packet logging operation can dereference the stale per-net logger pointer. Fix this by unregistering the global logger backends before tearing down per-net state. Once the global registrations are gone, later writers can no longer rebind the logger. unregister_pernet_subsys() already waits for an RCU grace period after the pre-exit callback clears the per-net selection, while nf_log_unregister() continues to cover readers of the global logger table. Apply this ordering fix to both nf_log backends that combine per-net teardown with global logger registration.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 24 days 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-97608, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e – < 51417230716b73f6aa1dc402b3a56d3382a694dc
    • affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e – < b0514ca1ee6f2b708d6c602ea946acdfc6a90e24
    • affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e – < 90166834b7dc6131aa42b6b14b8b4ed47be97079
    • affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e – < eaec35fae8f2052c1878a5c7cc7699d8357d79f2
    • affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e – < 64803ba0a05791cf9ca874466480e4c4cadaf7ab
    • affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e – < dce24f3a146948595bb1b86347f31e20b4975daa
    • affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e – < 2c018cc4842c33f0c732962e2ab58635e8ae5823
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .