CVE-2023-54200: netfilter: nf_tables: always release netdev hooks from notifier
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: always release netdev hooks from notifier
This reverts "netfilter: nf_tables: skip netdev events generated on netns removal".
The problem is that when a veth device is released, the veth release
callback will also queue the peer netns device for removal.
Its possible that the peer netns is also slated for removal. In this
case, the device memory is already released before the pre_exit hook of
the peer netns runs:
BUG: KASAN: slab-use-after-free in nf_hook_entry_head+0x1b8/0x1d0
Read of size 8 at addr ffff88812c0124f0 by task kworker/u8:1/45
Workqueue: netns cleanup_net
Call Trace:
nf_hook_entry_head+0x1b8/0x1d0
__nf_unregister_net_hook+0x76/0x510
nft_netdev_unregister_hooks+0xa0/0x220
__nft_release_hook+0x184/0x490
nf_tables_pre_exit_net+0x12f/0x1b0
..
Order is:
1. First netns is released, veth_dellink() queues peer netns device
for removal
2. peer netns is queued for removal
3. peer netns device is released, unreg event is triggered
4. unreg event is ignored because netns is going down
5. pre_exit hook calls nft_netdev_unregister_hooks but device memory
might be free'd already.
Security readout for executives and security teams
Plain-English summary
CVE-2023-54200 is a Linux kernel netfilter nf_tables cleanup bug. Under a specific network namespace and veth device removal sequence, the kernel can access already freed device memory. The public record does not provide CVSS, confirmed impact, or exploitation evidence, so urgency depends on whether affected kernels and this networking path exist in your fleet.
Executive priority
Track this as a kernel patch-management item with uncertain severity. Prioritize validation on container or namespace-heavy Linux infrastructure, but avoid emergency assumptions unless vendor advisories add impact detail or exploitation evidence.
Technical view
The issue is a slab use-after-free in nf_tables netdev hook cleanup. A prior change skipped netdev unregister events during namespace teardown; when veth peer namespaces are also being removed, device memory may be freed before nf_tables pre_exit unregisters hooks. Stable fixes revert that behavior so netdev hooks are always released from the notifier path.
Likely exposure
Exposure is most relevant on Linux systems running affected kernel versions with nf_tables netdev hooks and network namespaces using veth devices. The CVE record lists affected Linux kernel ranges, but distribution backports may change practical exposure. Confirm against your exact kernel package and vendor advisories.
Exploitation context
The source bundle shows no KEV listing and provides no evidence of active exploitation. It documents a kernel use-after-free observed with KASAN during netns cleanup. The sources do not state whether this is remotely exploitable, locally triggerable, or only a denial-of-service risk.
Researcher notes
Useful research focus is version mapping and backport confirmation. The public description gives a concrete teardown ordering issue and KASAN trace, but not a full exploitability analysis, attacker prerequisites, or confirmed security impact beyond use-after-free behavior.
Mitigation direction
Update to a kernel containing the referenced stable nf_tables fixes.
Check distribution kernel advisories for backported fixes or unaffected builds.
Prioritize hosts using network namespaces, veth devices, or nf_tables netdev hooks.
If patch timing is unclear, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, and appliances.
Compare running kernels to the CVE affected ranges and vendor package status.
Review whether nf_tables netdev hooks and veth-based namespaces are in use.
Confirm the kernel includes one of the referenced stable commits or vendor equivalent.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-54200 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 30, 2025, 12:09 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.