Answer in brief
CVE-2023-54200 records a Unknown severity vulnerability in netfilter: nf_tables: always release netdev hooks from notifier. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=68a3765c659f809dcaac20030853a054646eb739 <8d56f00c61f67b450fbbdcb874855e60ad92c560 || >=68a3765c659f809dcaac20030853a054646eb739 <30e4b13b1bfbdf3bf3b27036d8209ea1b9f0d880 || >=68a3765c659f809dcaac20030853a054646eb739 <94032527efbac13be702c76afb9d872c0cca7a43 || >=68a3765c659f809dcaac20030853a054646eb739 <dc1c9fd4a8bbe1e06add9053010b652449bfe411 || 90c7c58aa2bd02c65a4c63b7dfe0b16eab12cf9f || >=5.14.15 <5.15 | 8d56f00c61f67b450fbbdcb874855e60ad92c560, 30e4b13b1bfbdf3bf3b27036d8209ea1b9f0d880, 94032527efbac13be702c76afb9d872c0cca7a43, dc1c9fd4a8bbe1e06add9053010b652449bfe411, 5.15 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Dec 30, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-54200 records a Unknown severity vulnerability in netfilter: nf_tables: always release netdev hooks from notifier. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=68a3765c659f809dcaac20030853a054646eb739 <8d56f00c61f67b450fbbdcb874855e60ad92c560 || >=68a3765c659f809dcaac20030853a054646eb739 <30e4b13b1bfbdf3bf3b27036d8209ea1b9f0d880 || >=68a3765c659f809dcaac20030853a054646eb739 <94032527efbac13be702c76afb9d872c0cca7a43 || >=68a3765c659f809dcaac20030853a054646eb739 <dc1c9fd4a8bbe1e06add9053010b652449bfe411 || 90c7c58aa2bd02c65a4c63b7dfe0b16eab12cf9f || >=5.14.15 <5.15 | 8d56f00c61f67b450fbbdcb874855e60ad92c560, 30e4b13b1bfbdf3bf3b27036d8209ea1b9f0d880, 94032527efbac13be702c76afb9d872c0cca7a43, dc1c9fd4a8bbe1e06add9053010b652449bfe411, 5.15 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Dec 30, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.