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
A Linux kernel netfilter flaw can access memory after it has been freed when nftables transactions and table removal overlap. A local, low-privileged attacker may be able to crash the system or compromise kernel-enforced confidentiality and integrity. The supplied record rates it 7.8 High, but provides no evidence of active exploitation.
Executive priority
Treat as a high-priority local privilege-boundary issue, especially on shared or untrusted-user Linux systems. Patch through normal emergency kernel-maintenance procedures after vendor confirmation. Internet exposure alone does not establish reachability, and the supplied evidence does not show active exploitation.
Technical view
The nf_tables notifier conditionally flushed pending work, allowing a transaction-destruction worker to retain a reference to a table being removed. This produced a kernel slab use-after-free during nft_ctx_update and nft_commit_release. The kernel fix unconditionally flushes pending work before the notifier proceeds.
Likely exposure
Exposure requires a Linux kernel containing the vulnerable nf_tables code and local low-privileged access, according to the CVSS vector. The supplied affected-version data includes 6.5, 5.15.163, 6.1.98, 6.6.39, 6.9.9, and 6.10. Confirm distribution-specific backports because kernel version alone may be misleading.
Exploitation context
The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction, with potentially high confidentiality, integrity, and availability impact. The bundle marks this CVE absent from KEV and cites no observed exploitation or public exploit. Do not treat the theoretical impact as proof of reliable compromise.
Researcher notes
The report attributes the fault to a race between notifier activity and asynchronous transaction cleanup. It also says the problem appeared exposed only in nf-next after commit e169285f8c56, while the supplied affected table lists released kernels. This tension makes distribution and backport verification important. No CWE classification or exploit reliability evidence is supplied.
Mitigation direction
Install the Linux kernel security update supplied by your operating-system vendor.
Confirm the installed package incorporates the applicable linked stable-kernel fix.
Prioritize multi-user systems where untrusted local users can interact with nftables.
Check vendor advisories for backports rather than relying only on the reported kernel version.
Validation and detection
Inventory running kernel versions and operating-system package revisions.
Compare each revision with vendor advisories and the linked stable-kernel commits.
Confirm patched systems booted into the updated kernel after 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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.