netfilter: nf_log: unregister loggers before per-net teardown
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2c018cc4842c33f0c732962e2ab58635e8ae5823, Kernel 51417230716b73f6aa1dc402b3a56d3382a694dc, Kernel 64803ba0a05791cf9ca874466480e4c4cadaf7ab and 4 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.10, >=5b023fc8d8e0997e0b7ea6506d243afd5478c96e <2c018cc4842c33f0c732962e2ab58635e8ae5823, >=5b023fc8d8e0997e0b7ea6506d243afd5478c96e <51417230716b73f6aa1dc402b3a56d3382a694dc, >=5b023fc8d8e0997e0b7ea6506d243afd5478c96e <64803ba0a05791cf9ca874466480e4c4cadaf7ab, >=5b023fc8d8e0997e0b7ea6506d243afd5478c96e <90166834b7dc6131aa42b6b14b8b4ed47be97079, >=5b023fc8d8e0997e0b7ea6506d243afd5478c96e <b0514ca1ee6f2b708d6c602ea946acdfc6a90e24, >=5b023fc8d8e0997e0b7ea6506d243afd5478c96e <dce24f3a146948595bb1b86347f31e20b4975daa, >=5b023fc8d8e0997e0b7ea6506d243afd5478c96e <eaec35fae8f2052c1878a5c7cc7699d8357d79f2 | 2c018cc4842c33f0c732962e2ab58635e8ae5823, 51417230716b73f6aa1dc402b3a56d3382a694dc, 64803ba0a05791cf9ca874466480e4c4cadaf7ab, 90166834b7dc6131aa42b6b14b8b4ed47be97079, b0514ca1ee6f2b708d6c602ea946acdfc6a90e24, dce24f3a146948595bb1b86347f31e20b4975daa, eaec35fae8f2052c1878a5c7cc7699d8357d79f2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket