netfilter: nf_log: unregister loggers before per-net teardown
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5b023fc8d8e0997e0b7ea6506d243afd5478c96e · < dce24f3a146948595bb1b86347f31e20b4975daa| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s nf_log_syslog and nfnetlink_log backends can leave a stale per-network logger pointer during module teardown. A sysctl or netlink writer racing with teardown can rebind the logger, allowing a later sysctl read or packet-logging operation to dereference freed backend memory. The input does not specify authentication or user-interaction requirements.
Engineers running the Linux kernel should check affected versions; none are specified in the input.