CVE-2024-42109: netfilter: nf_tables: unconditionally flush pending work before notifier
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: unconditionally flush pending work before notifier
syzbot reports:
KASAN: slab-uaf in nft_ctx_update include/net/netfilter/nf_tables.h:1831
KASAN: slab-uaf in nft_commit_release net/netfilter/nf_tables_api.c:9530
KASAN: slab-uaf int nf_tables_trans_destroy_work+0x152b/0x1750 net/netfilter/nf_tables_api.c:9597
Read of size 2 at addr ffff88802b0051c4 by task kworker/1:1/45
[..]
Workqueue: events nf_tables_trans_destroy_work
Call Trace:
nft_ctx_update include/net/netfilter/nf_tables.h:1831 [inline]
nft_commit_release net/netfilter/nf_tables_api.c:9530 [inline]
nf_tables_trans_destroy_work+0x152b/0x1750 net/netfilter/nf_tables_api.c:9597
Problem is that the notifier does a conditional flush, but its possible
that the table-to-be-removed is still referenced by transactions being
processed by the worker, so we need to flush unconditionally.
We could make the flush_work depend on whether we found a table to delete
in nf-next to avoid the flush for most cases.
AFAICS this problem is only exposed in nf-next, with
commit e169285f8c56 ("netfilter: nf_tables: do not store nft_ctx in transaction objects"),
with this commit applied there is an unconditional fetch of
table->family which is whats triggering the above splat.
Security readout for executives and security teams
Plain-English summary
CVE-2024-42109 is a Linux kernel netfilter nf_tables memory-safety bug. The source describes a use-after-free found by syzbot/KASAN when pending transaction work can still reference a table being removed. Public sources provided do not state business impact, CVSS severity, or confirmed exploitation.
Executive priority
Track and remediate through kernel patch management. The issue is kernel-level and memory-safety related, but the provided evidence lacks severity scoring or exploitation claims, so it does not support emergency prioritization by itself.
Technical view
The issue is a slab use-after-free in nf_tables transaction cleanup. The notifier conditionally flushed pending work, but a table scheduled for removal could still be referenced by worker-processed transactions. The kernel fix changes this behavior to flush pending work unconditionally before the notifier path proceeds.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds with nf_tables code present. The bundle lists Linux kernel affected-version metadata and stable kernel fixes, plus a Debian LTS advisory. Validate using distribution kernel package advisories rather than upstream version numbers alone.
Exploitation context
The provided sources show syzbot/KASAN detection and kernel stable fixes. KEV is false, and no cited source claims active exploitation, public exploit availability, or practical attack requirements. The source text says the observed problem was only exposed in nf-next with a specific related commit.
Researcher notes
Key evidence is the syzbot KASAN slab use-after-free trace and the upstream explanation that pending nf_tables transaction work must be flushed unconditionally. The record has no CVSS, CWE, or exploit confirmation, and the nf-next exposure note narrows interpretation.
Mitigation direction
Apply the relevant Linux kernel update from your distribution or upstream stable branch.
Review the Debian LTS advisory if running Debian LTS kernels.
Prioritize hosts where nf_tables is enabled or firewall rules rely on nftables.
If no package is available, monitor vendor guidance for backported fixes.
Validation and detection
Inventory running kernel versions across Linux hosts.
Check distribution advisories for CVE-2024-42109 fix status.
Confirm updated kernels include the relevant stable fix commits or vendor backports.
Verify hosts rebooted into the patched kernel after package installation.
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-2024-42109 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.