netfilter: nf_log: unregister loggers before per-net teardown
Summary
| CVE | CVE-2026-97608 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-25 11:17:14 UTC |
| Updated | 2026-09-25 11:17:14 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e eaec35fae8f2052c1878a5c7cc7699d8357d79f2 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e 64803ba0a05791cf9ca874466480e4c4cadaf7ab git |
Not specified |
| CNA |
Linux |
Linux |
affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e dce24f3a146948595bb1b86347f31e20b4975daa git |
Not specified |
| CNA |
Linux |
Linux |
affected 5b023fc8d8e0997e0b7ea6506d243afd5478c96e 2c018cc4842c33f0c732962e2ab58635e8ae5823 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3.10 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 3.10 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.111 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.53 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.7 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/dce24f3a146948595bb1b86347f31e20b4975daa |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2c018cc4842c33f0c732962e2ab58635e8ae5823 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/eaec35fae8f2052c1878a5c7cc7699d8357d79f2 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/64803ba0a05791cf9ca874466480e4c4cadaf7ab |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.